codexlisted

# Codex as a Thinking Partner `codex exec` provides independent perspective from a separate AI agent. Runs locally, reads codebase, returns analysis to stdout. > **Shell prerequisite:** the recipes below use bash features (`/tmp/` paths, `source`, heredocs, `cygpath`). Claude Code ships with bash on every platform (native on Linux/macOS, Git Bash on Windows) so this is usually a non-issue — but if you're running Codex commands from native Windows `cmd` or PowerShell outside Claude Code, adapt the syntax. ## When to Use Codex - **Exploring design space** — want alternatives before committing → **Brainstorm** - **Have a plan or design** — want weaknesses flagged (failure modes + over-engineering + missed simplifications) before investing implementation time → **Red-team** - **Bug where local reasoning is stuck** — obvious hypotheses ruled out, OR unfamiliar stack where causes/instrumentation/repro are non-obvious → **Debug** - **Plan spans multiple subsystems or has non-trivial step ordering** — want sequencing, gap, rollback review → **Plan Review** - **Have a diff or report** — want factual claims verified, regressions found, or mismatch with the ticket/spec caught (prose optional) → **Diff Review** - **Ticket is prose with implicit requirements, or legacy code lacks clear contracts** — need concrete acceptance checklist before coding → **Spec Extraction** - **Shipping risky change** — schema update, API change, migration with operational impact → **Rollout/Rollback** - *