fix(vscode): hide manual interruption warning - #13376
Merged
Merged
Conversation
marius-kilocode
enabled auto-merge
August 24, 2026 15:20
marius-kilocode
disabled auto-merge
August 24, 2026 15:21
kirillk
approved these changes
Aug 25, 2026
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
2 participants
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.
Explicitly stopping a turn in the VS Code sidebar or Agent Manager currently produces a transient yellow
Turn interrupted.card. The close event uses the sameinterruptedreason for both intentional user stops and unexpected runtime interruptions, and the UI can observe the close before the abort request completes.This change keeps the existing backend and SDK close-reason contracts unchanged. The shared VS Code connection now buffers an
interruptedclose only for filtered webview subscribers while a confirmed explicit abort is pending. A successful abort suppresses the close for all webview clients, while a failed abort replays it. Raw SSE subscribers continue to receive every event, and state is scoped by session and directory with handling for concurrent aborts, multi-directory sessions, reload/reset cleanup, and later turns.The existing warning behavior for genuine interruptions, errors, output limits, and other abnormal completions remains unchanged.