Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Monitor, control, and orchestrate background Codex sessions. Use this skill to track progress, handle interruptions, and ensure task completion for long-running coding tasks.
Monitor, control, and orchestrate background Codex sessions. Use this skill to track progress, handle interruptions, and ensure task completion for long-running coding tasks.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
This skill provides a workflow for supervising the Codex coding agent running in background processes.
Always launch Codex in a background PTY session to maintain interactivity without blocking the main agent. bash pty:true workdir:<target_dir> background:true command:"codex exec --full-auto '<PROMPT>'" Store the returned sessionId. If sessionId is lost, find it via process action:list.
Check progress regularly (e.g., via cron or manual check). # Get last 2KB of logs to see current status process action:log sessionId:<id> limit:2000 Signs of life: Spinner animations or progress bars updating. "Working...", "Thinking...", "Running...". File edits (Edit ...). Signs of blockage: Interactive prompts (e.g., "Select directory", "Approve change [y/n]"). No log output for >5 minutes (process might be hung or waiting for hidden input).
If Codex is stuck at a prompt: # Send 'y' and Enter process action:submit sessionId:<id> data:"y" # Send just Enter (default choice) process action:submit sessionId:<id> data:"" If Codex is looping or hallucinating: # Kill the session process action:kill sessionId:<id>
When a significant milestone is reached or the task is done: Summarize the work done (files changed, tests passed). Notify the user.
Diagnose: Run process action:log sessionId:<id> limit:500. Analyze: Is it asking a question? Is it downloading? Action: If asking: Provide answer via submit. If downloading (slow): Wait. If silent >10m: Send a "poke" (e.g. submit data:"\n" to refresh prompt) or kill/resume.
If a session died or was killed: Run codex resume --last or codex resume <session_id> in a new background process. Verify it picked up the context.
Codex logs are ephemeral in the PTY buffer. For persistent logs, instruct Codex to write to a file: codex exec "task..." > codex.log 2>&1 (Note: buffering may delay output). Better: Use process action:log to snapshot the buffer periodically.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.