Codex Delegate

Delegate a complete, bounded task from the main session to the Codex CLI with codex exec --json. No plugin, broker, or daemon: the host packages intent, launches one detached codex run that outlives the command that started it, checks it through a read-only renderer, and verifies the outcome.

Execution boundary: the host is Claude Code, Cursor, or another non-Codex harness. If this skill is invoked from inside Codex, stop instead of launching Codex recursively. The boundary is instruction-driven; do not add harness detection or a plugin-like management layer to enforce it.

Requirements: codex CLI ≥ 0.145, logged in; openssl for run IDs; util-linux setsid when available, otherwise perl with POSIX support for the detached launch (macOS has system Perl but no setsid command); bun (preferred) or Node ≥ 18 for the renderer.

1. Package the mission

Codex sees the packet plus whatever it discovers in the workspace. Write the smallest complete set of:

• objective and an observable definition of done;
• intent, context, and decisions that exist only in the host conversation, plus the paths, plans, or artifacts Codex cannot discover;
• scope in and out, plus how much investigation, judgment, and decision-making Codex owns;
• authority boundaries and pause conditions, including intended external effects (network, MCP tools, credentials);
• whether internal subagents are useful: allow Codex to choose their number and topology when the mission has genuinely independent branches;
• verification commands and the final response contract.