Repository navigation
Conversation
This branch has not been deployed
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
A standard subagent can advertise cancellation before Codex has registered its turn as interruptible. Both a direct child cancel and a parent cancel currently send one
turn/interrupt, so a transient registration error can leave the child running.This reuses the existing interrupt backoff for those child turns. Each retry targets the original child turn while the router still observes it as current. A mismatched active ID from Codex never retargets the retry. The existing foreground/background selection and completion reporting are preserved.
Related to #641. This extends the cancellation retry fencing from #723 to standard subagents.
Validation