Feature Request: Add `get_unbound_breakpoints` tool
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- typescript, vscode
- Domain
- devtools
Research direction
Start by locating the existing add_breakpoint and list_breakpoints MCP tools, then inspect how they access vscode.debug.breakpoints. Add the no-parameter get_unbound_breakpoints tool and verify that it returns file and line information for breakpoints with verified === false, an empty array when none are unverified, and works without an active debug session.
Written by the indexing model from the issue text.
Description
Summary
Add a new MCP tool called get_unbound_breakpoints that returns all breakpoints currently set but not verified (i.e., not successfully bound to an executable line) by the debug adapter.
Problem
DebugMCP's existing add_breakpoint tool gives no feedback on whether a breakpoint actually bound successfully. If the lineContent parameter doesn't match the file exactly (see #18), or the file isn't loaded yet, the breakpoint is silently registered but never verified. The existing list_breakpoints tool lists all breakpoints without distinguishing between verified and unverified ones, leaving the agent with no way to detect or diagnose the failure.
This means an agent can confidently believe it has set a breakpoint, proceed to run the program, and never understand why execution never paused.
Proposed Solution
Add a get_unbound_breakpoints tool that queries VS Code's vscode.debug.breakpoints collection and filters for breakpoints where verified === false.
Requirements:
- No parameters required
- Should work at any point during a debug session
- Returns an array of unverified breakpoints with file and line information
- Returns an empty array (not an error) if all breakpoints are verified
- Dominant language
- TypeScript
- Stars
- 511
- Forks
- 60
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 18
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/DebugMCP
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in microsoft/DebugMCP
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ontola/atomic-server#1625 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
melgarafael/DeskcommCRM#1451 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bot:ai-assisted component:compact-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
midnightntwrk/midnight-sdk#403 ·