What the source did
- Claude Code explores, plans, builds and handles refactors.
- Codex reviews the changes, looks for edge cases and challenges decisions.
“claude code builds > codex reviews”— sannn ~ (@santiagoo24_), X
Summary written by Agent Cookbook. See the original for the full context.
Copy the prompt
Ours Our version, based on what sannn ~ described. Not their wording. Fill in the [BRACKETS].
(Codex, after Claude Code finishes) Review the diff on this branch against main.
1. Bugs and edge cases, with file:line.
2. Architectural decisions you'd challenge, and the alternative.
3. Anything that looks finished but isn't (TODOs, unhandled errors, missing tests).
Don't edit files. Rank findings by risk.
Approval rule
🛡
The reviewer is read-only; the builder applies fixes you accept.
Set it up
- Finish the feature in Claude Code and commit.
- Run the review prompt in Codex on the same branch.
- Paste high-risk findings back to Claude Code to fix.
Common failures
⚠
- Reviewer nitpicks bury real issues. Ask it to rank.
- Both agents share the same blind spot when given the same vague spec.
Variations
- Swap roles for bug fixes.
- Add a third agent from a different vendor as tie-breaker.
Get the 10 best agent setups. Free.
Plus new recipes every week. One email, no spam.
Unsubscribe anytime. Privacy