Codex Delegate

Route work Claude could do but Codex does as well and more cheaply over to the codex CLI, then verify and integrate the result. Codex (GPT-5) runs at roughly half the cost of a frontier Claude model, is highly token-efficient, and sustains long unattended runs — so offloading rote, well-specified work conserves the expensive Claude budget for what Claude is uniquely good at: judgment, interactive iteration, and final quality.

Claude stays the orchestrator. You decide what to delegate, write the spec, and own the quality gate on what comes back. Codex is a fast, cheap worker — not the decision-maker.

The core decision: DELEGATE or KEEP

Ask two questions:

1. Can I specify "done" crisply enough that a fresh agent with no chat context could finish it?
2. Is the work bulk, mechanical, long-running, parallelizable, or would it benefit from an independent second model?