codex

# Codex Bridge ## Standalone Codex If the active host is already standalone Codex, stop before any bridge command. Never recursively invoke `codex-run.ts` or launch the Codex CLI from inside Codex. Do the requested task locally with native tools. When the user asks for an independent review, spawn a fresh native `reviewer` and wait until it finishes; do not spawn `codex-verifier`. Everything below is the Claude-only bridge workflow. ## Claude-only bridge Invoke the OpenAI Codex CLI from inside a Claude session. Three subcommands map to three distinct use cases. All subcommands are called via: ```bash bun "$HOME/.claude/src/scripts/codex-run.ts" <subcommand> [args] ``` --- ## Subcommands ### exec -- delegate mechanical or bulk work ```bash bun "$HOME/.claude/src/scripts/codex-run.ts" exec "the full task description" ``` Runs Codex in a `workspace-write` sandbox. Use this when a task is: - Mechanical (repetitive edits, file scaffolding, boilerplate generation) - Bulk (touching many files at once where Claude's serial context would be slow) - Parallelizable with Claude's own work (start Codex on one half while Claude handles the other) **Quota routing**: Codex is metered by messages per ~5-hour window, not by tokens. Hand it one big complete task, not a sequence of small steps. A single `exec` call for a whole feature costs the same quota as one `exec` call for a single file. After `exec` returns, ALWAYS review Codex's diff before trusting it: ```bash git diff ``...