fix: use VS Code commands for continue/step to fix exception UI#21
Merged
TPreece101 merged 1 commit intomainfrom Feb 13, 2026
Merged
fix: use VS Code commands for continue/step to fix exception UI#21TPreece101 merged 1 commit intomainfrom
TPreece101 merged 1 commit intomainfrom
Conversation
…ass stop reason to LLM
session.customRequest('continue') bypassed VS Code's internal debug model
state updates, so the model never transitioned to "running". When an
exception's stopped event arrived, VS Code didn't properly process it —
the exception dialog never showed and the debugger appeared stuck.
Switch to vscode.commands.executeCommand for continue/step actions by
default, falling back to customRequest only when explicit threadId or
granularity is needed.
Also pass through DAP stop metadata (reason, description, exceptionText)
in tool responses so LLMs can distinguish breakpoints from exceptions and
see the error message.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #21 +/- ##
==========================================
+ Coverage 74.87% 75.70% +0.83%
==========================================
Files 7 8 +1
Lines 1210 1268 +58
Branches 152 160 +8
==========================================
+ Hits 906 960 +54
- Misses 302 306 +4
Partials 2 2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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
session.customRequest('continue')bypassed VS Code's internal debug model state updates, so when an exception occurred after continuing from a breakpoint, the UI never showed the exception and the debugger appeared stuck. Now usesvscode.commands.executeCommand('workbench.action.debug.continue')(and equivalent step commands) by default, which properly updates the model state. Falls back tocustomRequestonly when explicitthreadIdorgranularityis needed.reason(e.g."breakpoint","exception","step"),description, andexceptionTextfields so LLMs can distinguish why the debugger stopped and see exception messages without needing a separate evaluate call.exception-continue.test.tssuite covers the breakpoint → continue → exception scenario, verifying proper stop detection and that exception metadata is present in the response.Test plan
npm test), including new exception-after-continue suitereason: "exception"anddescriptionfields🤖 Generated with Claude Code