I Used Claude Code And Codex Together, Here’s What Surprised Me
by Wyndo and Dheeraj Sharma · 2026-06-14
✓ Opened with WebFetch on 2026-10-15
Read the original ↗Two agents pass one project back and forth through a single log file each must read before starting and append to after finishing, so the second agent can review the first.
- Created changes.log that both tools read first and update last.
- Kept Claude's rules in CLAUDE.md; Codex imported them into AGENTS.md.
- Ran a live round trip on a small calculator: Claude added a breakdown, Codex turned it into a chart and checked it in the browser, Claude then rebranded it.
“It gives the next agent something to judge.”— Wyndo and Dheeraj Sharma, Substack
Summary written by Agent Cookbook. See the original for the full context.
Adapted by us from what the source described. Fill in the [BRACKETS].
The prompt
Set it up
- Pick a low-risk repo both tools can open.
- Add changes.log and paste the block above into both CLAUDE.md and AGENTS.md (or import one from the other).
- Run one small round trip: agent A builds, agent B reviews and improves, agent A picks back up.
- Read each entry before approving the next run.
Common failures
- Both agents run at once and overwrite each other's entries. Hand off sequentially or use separate branches.
- Vague entries ('fixed stuff') give the next agent nothing to judge.
- Rules drift when CLAUDE.md and AGENTS.md diverge; keep one source and import it.
Variations
- Swap direction: Codex drafts, Claude Code wires it in.
- Add a 'reviewer findings' section to every entry.