fix: continue interrupted agents with follow-up - #87
Merged
Merged
Conversation
Route interrupt control markers through Pi's follow-up queue so the replacement instruction survives cancellation of the current run and executes in a fresh continuation. Keep task, steer, and reply requests on the existing steering path. Extend the managed request pump regression to assert follow-up delivery and native abort behavior. Validation: - npm run check - git diff --check - Live interrupt smoke passed with replacement completion, preserved assignment/session identity, and no stale steer execution.
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
1 participant
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
Validation
npm test -- extension/agent-runtime.test.ts— 51 passednpm run check— passedgit diff --checkandgit diff HEAD --check— passedOwner interrupt:replacement executed and completed in the same session and assignment, the queued stale steer did not execute, and exactly one final result was produced.