feat: add noWait parameter to start_debugging and continue_execution - #116
Open
ankitajha6475-jpg wants to merge 3 commits into
Open
feat: add noWait parameter to start_debugging and continue_execution#116ankitajha6475-jpg wants to merge 3 commits into
ankitajha6475-jpg wants to merge 3 commits into
Conversation
Author
|
@microsoft-github-policy-service agree |
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.
Description
Historically, DebugMCP's \start_debugging\ and \continue_execution\ calls blocked synchronously until a breakpoint was hit. If an AI agent invoked \start_debugging\ before informing the user in text, the turn blocked in a tool-call wait state, preventing the user from receiving the prompt instructions.
This PR natively updates \microsoft/DebugMCP\ to support
oWait: true.
The agent can now call \start_debugging(noWait: true)\ to arm the debugger in the background and immediately get control back to output instructions to the user.
The human user can then safely interact with the UI at their own pace. Once the breakpoint is reached, the IDE natively pauses execution and the agent can evaluate expressions.