Fix recovery false positive after terminal review - #393
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Aug 29, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fix the Codex watchdog recovery false positive seen after a completed read-only acceptance review.
The reproduced failure is a terminal
REJECTEDreport where no further repository action is authorised, but theStophook still injectsrecovery 1/3. After the assistant explicitly reports that no further action is authorised, the persisted recovery state can injectrecovery 2/3as well.Root cause
Stopfeeds the final assistant message through the no-progress watchdog and then treats any interrupt, including the generated-character budget, as evidence that a selected tool/action boundary is still missing. Once recovery starts, it stays active until a real tool boundary even when the corrective continuation is an explicit terminal disposition.Fix
No further action is authorized.Regression coverage
recovery 1/3.recovery 2/3.TDD evidence
The first commit,
67fc71b105e353122ca14d7fed32d36999a472c4, contains the two original regressions only. CI fails both assertions on the unchanged hook and returns the exactrecovery 1/3andrecovery 2/3outputs from the reported bug.A later adversarial regression also covers the mixed terminal-plus-tool-intent bypass before the final guard was tightened.