Repository navigation
codex-claude-loop v0.3.0 — carrying intent between rounds
A reader of the launch thread named the failure this loop did not catch:
codex sometimes technically matches the revise feedback but misses the intent, and i don't notice till the next review round. does your hash binding only lock the plan text, or does it somehow prevent that intent drift too?
It did not. Worth stating plainly, because it is the more interesting half of the answer: hashing binds an approval to the state it judged. It says nothing about whether a fix meant what the reviewer meant. Those are different problems, and v0.2.0 only solved the first.
The gap was structural, not a bug. cl_revise handed the blocking items to the Codex thread and kept no copy, so the next review started from the diff alone. It had the evidence and not the question.
v0.3.0
cl_reviseappends each round's items to<slug>.carryover.md- both review paths carry every earlier round into the prompt, and are told to judge each item on intent: name the item, quote the line that satisfies the letter, state the intent it misses
- settled items get marked, so later rounds stop re-litigating them
cl_planclears the carryover, since those items were raised against a plan that no longer exists
53 → 58 assertions. The new ones check the items survive the round, that the next review's prompt contains them, that rounds accumulate rather than overwrite, and that re-planning drops them.
/plugin marketplace add ozzaii/codex-claude-loop
/plugin install codex-claude-loop@codex-claude-loop