codex-orchestrator

What This Skill Does

The codex-orchestrator skill acts as a supervisor for the Codex AI coding assistant. When running long-form coding tasks, AI agents can sometimes hit roadblocks, enter wait-states, or require human-like feedback to proceed. This skill provides the infrastructure to spawn Codex in detached, persistent PTY sessions, monitor its terminal output for signs of life or stalled processes, and inject necessary input to keep the workflow moving. It transforms your coding agent from a 'fire and forget' tool into a managed, resilient background service.

Installation

To install this skill, use the ClawHub CLI: clawhub install openclaw/skills/skills/microcarft/codex-orchestrator

Use Cases

• Mass Refactoring: Managing Codex while it refactors large codebases across multiple files where confirmation prompts may appear.
• Long-Running Builds: Orchestrating background compilation or dependency resolution that requires the agent to remain alive and responsive.
• Unattended Task Completion: Ensuring the coding agent recovers gracefully from minor environmental interruptions without requiring constant manual intervention.

Example Prompts

1. "Orchestrator, please launch a codex session for the user authentication refactor in the /src/auth directory and monitor its progress."
2. "Check the status of my existing codex session. If it's waiting for a directory confirmation, provide the 'y' input."
3. "The codex session seems stuck. Please read the last 2000 lines of its output, diagnose if it's hung, and restart it using the resume protocol if necessary."

Tips & Limitations

• PTY Management: Always use the provided PTY launching pattern; running without it may cause input signals to drop or process buffers to fill up without notification.
• Log Snapshots: Since PTY logs are ephemeral, configure critical tasks to write to a log file if you need a persistent audit trail. Do not rely solely on the live buffer for long-term historical records.
• Prompt Injection: Use the 'submit' command carefully. Ensure you are providing the correct input; sending an erroneous character to a command-line prompt can trigger unintended file deletions or process cancellations.
• Idle Time: If the agent is silent for over 10 minutes, treat it as a potential freeze and perform a 'poke' via the submit command before resorting to a kill command.