Disclosure first, since the rule asks for it: I wrote this, it is free under MIT, and there is nothing to buy, sign up for, or host. What it does. It turns the Claude and Codex handoff into one gated loop instead of a copy-paste chore. Codex opens a persistent thread and writes the plan as the implementer. Claude approves that plan or sends it back. Codex resumes the same thread and implements its own approved plan. Claude reviews the diff against that plan file. Blocking findings go back into the same thread and get re-reviewed. Who benefits. People already running Claude Code alongside a Codex subscription who currently paste plans between two windows. If you use only one of the two, this does nothing for you. The gates are the whole point. Implementation refuses to run unless the plan verdict is approve , and the approval is bound to a hash of the plan text, so editing the plan afterwards voids it. Release refuses unless the review approved the tree as it stands. An approve that carries blocking items is rewritten to revise on disk. One writer holds a lock on the tree, and review refuses to run while that lock is held. /plugin marketplace add ozzaii/codex-claude-loop /plugin install codex-claude-loop@codex-claude-loop /codex-claude-loop:doctor It ran 45 gated waves across 20 lanes of a production codebase before I extracted it into its own repo. The test suite drives the entire loop against a stub codex binary, 53 assertions, so you can watch the gates refuse things without spending quota. Happy to answer questions here, and I want to hear where it breaks for you. https://github.com/ozzaii/codex-claude-loop submitted by /u/smealdor
Originally posted by u/smealdor on r/ClaudeCode