codex-delegatelisted

# Delegate to Codex when it saves the user tokens The Codex CLI on this machine runs on the user's **ChatGPT plan quota** — a separate budget from this Claude session. Work pushed to Codex costs no Claude output tokens and, more importantly, keeps large intermediate output (file dumps, generated boilerplate, long search results) out of this context window. Your job is to notice when that trade is worth making, **offer it**, and then orchestrate. ## The decision rubric Delegate to Codex when the task is **high-volume and low-judgment**: | Signal | Example | | :-- | :-- | | Mechanical edits across many files | rename a symbol in 40 files, migrate an import style, add a header to every module | | Bulk generation | scaffold 20 CRUD endpoints, write fixtures, generate a large seed dataset | | Exhaustive sweeps | "find every place we call the old API", audit all routes for auth | | Assets | any image, icon set, mockup, or diagram — always Codex, it has gpt-image-2 | | Long, self-contained subtasks | port a module to TypeScript, write the test suite for one file | | A genuinely independent opinion | you already have an answer and want it challenged | Keep it yourself when the task is **low-volume and high-judgment**: architecture calls, ambiguous requirements, anything needing the conversation history, small edits (under ~3 files), or anything the user is iterating on interactively. Round-tripping a two-line fix through Codex is slower and costs *more* overall. ## How to offe