codex-agent

Automates Codex CLI provisioning and management for controlled OpenClaw-powered runtime sessions and CI tasks.

158|25|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/dztabel-happy/codex-agent --skill codex-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-agent
Source: https://github.com/dztabel-happy/codex-agent/tree/main
Command: npx skills add https://github.com/dztabel-happy/codex-agent --skill codex-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenClaw-managed runtime to reliably operate Codex CLI, stabilizing startup, tracking sessions, and providing explicit routing and notifications.

Core Features & Use Cases

  • Provides a managed interactive Codex experience via start_codex.sh and run_codex.sh, enabling deterministic sessions and robust monitoring.
  • Maintains a private runtime registry under ~/.openclaw/runtime/codex-agent with per-session logs, PIDs, and outputs for auditability.
  • Enforces explicit --session-id routing for OpenClaw wakeups and cross-context coordination, and supports status queries through runtime tooling.
  • Detects common startup blockers (update prompts, trust prompts) and ensures recoverable operation with proper notifications.

Quick Start

Start a managed Codex session by running bash hooks/start_codex.sh codex-agent-demo /absolute/workdir --full-auto.

Frequently Asked Questions about codex-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Codex CLI session management and prevent startup blockers?

Automating Codex CLI session management requires a managed runtime like OpenClaw to provision tasks, detect startup blockers such as update or trust prompts, and maintain a private registry with per-session logs and PIDs for recoverable operation.

What is explicit session-id routing for OpenClaw wakeups?

Explicit session-id routing for OpenClaw wakeups is a mechanism ensuring deterministic cross-context coordination by directing execution commands to specific Codex CLI instances using stable session keys within a controlled runtime.

How do I start a managed interactive Codex session with full auto mode?

To start a managed interactive Codex session, run the bash hooks/start_codex.sh script with a session name and absolute working directory, passing the --full-auto flag to enable deterministic execution and robust monitoring.

Does the Codex CLI runtime support one-shot executions and status queries for CI tasks?

Yes, the Codex CLI runtime supports one-shot executions and status queries across local workflows and CI tasks, providing completion notifications and auditability through a private registry storing outputs and logs.

Why does my Codex CLI task fail to start during interactive tmux sessions?

Codex CLI tasks may fail to start during interactive tmux sessions due to undetected startup blockers like update or trust prompts, requiring a managed runtime to detect these blockers and ensure proper notifications for recoverable operation.