菜单
Delegate a coding task to a Codex CLI session managed via tmux. Invoked as /codex. User drives all progress checks and interventions — no auto-polling.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Delegate a coding task to an agy (Antigravity CLI) session managed via tmux. Invoke explicitly as $agy. User drives all progress checks and interventions — no auto-polling.
Delegate a coding task to a Cursor Agent CLI session managed via tmux. Invoke explicitly as $cursor. User drives all progress checks and interventions — no auto-polling.
Delegate a coding task to a Droid (Factory AI) CLI session managed via tmux. Invoke explicitly as $droid. User drives all progress checks and interventions — no auto-polling.
Delegate a coding task to a Claude Code CLI session managed via tmux. Invoke explicitly as $claude. User drives all progress checks and interventions — no auto-polling.
Delegate a coding task to a GitHub Copilot CLI session managed via tmux. Invoke explicitly as $copilot. User drives all progress checks and interventions — no auto-polling.
Delegate a coding task to an Opencode CLI session managed via tmux. Invoke explicitly as $opencode. User drives all progress checks and interventions — no auto-polling.
基于 SOC 职业分类
| name | codex |
| description | Delegate a coding task to a Codex CLI session managed via tmux. Invoked as /codex. User drives all progress checks and interventions — no auto-polling. |
Spawns Codex in a detached tmux session so Claude can offload work to it. The user stays in the loop: they ask Claude when to check progress, what guidance to send, and when to stop.
All operations go through a single dispatcher:
~/.claude/skills/codex/bin/codex-agent [--session <name>] <verb> [args]
Verbs:
start [task...] — create session (default cc-codex), launch codex --dangerously-bypass-approvals-and-sandbox, type the task and press Enter. Returns immediately (non-blocking).send <message> — type message + Enter. For follow-up guidance. Does not interrupt current generation; Codex queues the input.keys <name> — send a raw tmux key (Escape, C-c, Enter, etc.). Used for interrupts.capture [lines] — print last N ANSI-stripped rendered lines (default 500). Read-only, non-destructive.wait [stable] [timeout] — block until codex goes idle, then exit. Run via a backgrounded Bash so the harness notifies Claude on completion (see "Auto-notify" below). stable = secs the working indicator must stay gone before declaring idle (default 6); timeout = overall cap in secs (default 1800).stop — kill-session. Destroys the tmux session.list — list active cc-codex* sessions.| User says | Do |
|---|---|
/codex <task> | start <task>, then arm Auto-notify (below); reply "Started. I'll ping you when codex finishes." |
| "check codex" / "progress" / "what's codex doing" / "ask codex for progress" | capture. Show the relevant tail, add a one-line diagnosis (running / idle / error / prompt). Do not send ESC. |
| "interrupt codex" / "esc codex" | keys Escape → capture. |
| "tell codex: X" / "send codex: X" | send X. |
| "kill codex" / "stop codex" | stop. |
Rules:
ScheduleWakeup/timer. For new tasks, arm the wait watcher by default (see Auto-notify), which polls inside a cheap background shell instead. Only capture when the user asks.Escape unless the user explicitly asks to interrupt.capture is the default observation verb. Prefer it over intervention.cc-codex. For concurrent tasks, pass --session <name> before the verb.--dangerously-bypass-approvals-and-sandbox lets Codex run arbitrary shell commands without approval or sandbox. For untrusted tasks, launch inside a git worktree or change the script to use --full-auto (sandboxed workspace-write).
After start — and after any send that should produce another completion ping — arm a backgrounded watcher. This is the default for /codex <task>; the user does not need to say "tell me when it's done". The trick is entirely Claude-side: codex sends no signal. A background shell scrapes the pane and exits when codex goes idle, and the harness re-invokes Claude on that exit. The polling moves into a cheap shell loop; Claude is woken exactly once.
To arm it, call the wait verb through a backgrounded Bash:
Bash(
command: "~/.claude/skills/codex/bin/codex-agent wait",
run_in_background: true,
description: "wait for codex to go idle"
)
On exit the harness notifies Claude. Read the final stdout line for the state, then capture and report to the user:
| Watcher's last line | Means | Claude does on wake |
|---|---|---|
idle … task-appears-complete | spinner gone and stable | capture, summarize the result |
prompt … permission-prompt | idle but a y/n prompt is up | capture, tell the user / send y if they authorized it |
timeout … still-busy | hit the cap while still working | capture, report it's still going; re-arm wait if desired |
gone / idle … no-activity | session killed, or codex never started working | capture to confirm |
Notes:
wait immediately after start/send — don't capture first. A fast model can finish during the gap, and the watcher will then report no-activity (it never saw the spinner) instead of catching the idle transition. Capture only after the watcher wakes you.ScheduleWakeup timer (that's autopilot's job, with its own skill).wait requires it gone for stable secs (default 6) before declaring idle. Bump it for tasks with long gaps between steps.send if you want a ping for that follow-up too — one wait covers one idle transition.