This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
codex-claude-loop
Your AI approves its own work. This one can't.
A gated build loop between Claude Code and Codex CLI. Codex writes a plan, Claude approves it, Codex implements that same plan from the same thread, Claude reviews the diff against it. Release refuses an unreviewed tree. MIT, no extra deps.
The title is the whole problem. One agent writes the code and the same agent tells you it
looks good, which is not review, it is a receipt.
I have tried a lot of Claude + Codex setups. The handoff was always the weak point: Claude
writes a plan, you paste it into Codex, and Codex builds a summary of reasoning it never
did. Then you paste the diff back for review. Half a day of tab-switching per feature.
This closes it into one loop. Codex opens a persistent thread and writes the plan as the
implementer. Claude approves it or sends it back. Codex resumes that same thread and
implements its own approved plan. Claude reviews the diff against that plan file.
The part I did not expect to matter as much as it did: keeping the thread. When Codex
implements a plan it authored, the reasoning is still in context, so it stops re-deciding
what the plan already settled.
The gates refuse things on purpose. Implementation will not start unless the plan is
approved, and the approval is bound to the plan text that was read, so editing the plan
afterwards voids it. Release refuses unless the review approved the tree as it is right
now. An "approve" that carries blocking items is rewritten to "revise" on disk.
I found several of those the honest way: I handed the whole thing to Codex as an
adversarial reviewer, and it opened with "not release-ready, both hard gates can report
approval for state they did not validate." It was right. v0.2.0 is what came out of that.
It ran 45 gated waves across 20 lanes of a production codebase before I extracted it. MIT,
free, no signup, nothing to buy. Tests are 53 assertions that run against a stub codex, so
you can verify the gates without spending quota.
Happy to answer anything, and I would genuinely like to hear where it breaks for you.
About codex-claude-loop on Product Hunt
“Your AI approves its own work. This one can't.”
codex-claude-loop was submitted on Product Hunt and earned 3 upvotes and 1 comments, placing #111 on the daily leaderboard. A gated build loop between Claude Code and Codex CLI. Codex writes a plan, Claude approves it, Codex implements that same plan from the same thread, Claude reviews the diff against it. Release refuses an unreviewed tree. MIT, no extra deps.
On the analytics side, codex-claude-loop competes within Open Source, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how codex-claude-loop performed against the three products that launched closest to it on the same day.
Who hunted codex-claude-loop?
codex-claude-loop was hunted by Kaan Özkan. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of codex-claude-loop including community comment highlights and product details, visit the product overview.
Kaan Özkan