fix: mark tool outputs after interrupted replies - #6859
Draft
chenghao-mou wants to merge 1 commit into
Draft
Conversation
chenghao-mou
force-pushed
the
chenghao/fix/AGT-3295-interrupted-tool-output
branch
from
August 14, 2026 16:43
a202b70 to
f644561
Compare
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.
Why
Tool outputs remain in chat history after execution. If the user interrupts their spoken reply, the next LLM turn can treat that explanation as delivered and return no reply.
Behavior
Mark interrupted tool results in model-facing payloads while preserving existing payloads for completed replies. Keep immediate commits so tools with side effects are not replayed.
Addresses AGT-3295
Initial prompt and agent context
Model: GPT-5.6