Merge pull request #98 from microsoft/ozzafar/conditional_breakpoint

Ozzafar/conditional breakpoint

Author: ozzafar

CHANGELOG.md

@@ -4,6 +4,17 @@ All notable changes to DebugMCP will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/), and this project adheres to [Semantic Versioning](https://semver.org/).
 
+## [2.1.0] - 2026-06-23
+
+### Added
+- **Conditional breakpoints** — `add_breakpoint` now accepts an optional `condition` expression so execution only pauses when the condition evaluates to true (e.g. `i == 5`, `user.id === null`). Conditions are surfaced in `list_breakpoints` and the debug state.
+
+### Changed
+- **Renamed the companion Agent Skill from `really-debug` to `debug-live`.** It now installs at `skills/debug-live/` (e.g. `~/.copilot/skills/debug-live/`) and is invoked with `/debug-live`. Previous `really-debug` (and `debug`) installs are cleaned up automatically on registration.
+
+### Fixed
+- **`continue`/step no longer hangs when the program runs to completion.** Detection now settles on termination of the specific session being debugged (by identity) instead of waiting for the global active session to clear, which previously hung until the timeout when a parent session (e.g. the JS debug terminal) outlived the program.
+
 ## [1.2.0] - 2026-06-04
 
 ### Added

README.md

@@ -19,7 +19,7 @@ Let AI agents debug your code inside VS Code - set breakpoints, step through exe
 
 ## ✨ What's New in 2.0.0
 
-- **`/really-debug` Agent Skill** — DebugMCP now ships a companion [Agent Skill](./skills/really-debug/SKILL.md) that is auto-installed into each configured harness's personal skills directory (e.g. `~/.copilot/skills/really-debug/`). Invoke it with `/really-debug` in supporting agents to load the systematic debugging workflow and trigger DebugMCP tools with the right context.
+- **`/debug-live` Agent Skill** — DebugMCP now ships a companion [Agent Skill](./skills/debug-live/SKILL.md) that is auto-installed into each configured harness's personal skills directory (e.g. `~/.copilot/skills/debug-live/`). Invoke it with `/debug-live` in supporting agents to load the systematic debugging workflow and trigger DebugMCP tools with the right context.
 - **Robust debugging via the VS Code Testing API** — `start_debugging` with a `testName` now uses the VS Code Testing API to discover and launch the test, replacing the previous best-effort path. This works reliably across language test runners that integrate with the Testing API (pytest, Jest/Vitest, Java, .NET, Go, etc.) and produces consistent breakpoint hits inside individual test cases.
 
 ## 🚀 Quick Install
@@ -57,7 +57,7 @@ DebugMCP is an MCP server that gives AI coding agents full control over the VS C
 | **step_out** | Step out of the current function | None |
 | **continue_execution** | Continue until next breakpoint | None |
 | **restart_debugging** | Restart the current debug session | None |
-| **add_breakpoint** | Add a breakpoint at a specific line | `fileFullPath` (required)<br>`lineContent` (required) |
+| **add_breakpoint** | Add a breakpoint at a specific line (optionally conditional) | `fileFullPath` (required)<br>`lineContent` (required)<br>`condition` (optional) |
 | **remove_breakpoint** | Remove a breakpoint from a specific line | `fileFullPath` (required)<br>`line` (required) |
 | **clear_all_breakpoints** | Remove all breakpoints at once | None |
 | **list_breakpoints** | List all active breakpoints | None |
@@ -67,7 +67,7 @@ DebugMCP is an MCP server that gives AI coding agents full control over the VS C
 > **Note:** The MCP server intentionally exposes **tools only** — no procedural
 > instructions, no documentation resources. Workflow guidance (when to debug, how to
 > structure a root-cause investigation, language-specific quirks) lives in the companion
-> [DebugMCP Agent Skill](./skills/really-debug/SKILL.md) so it can be loaded into an
+> [DebugMCP Agent Skill](./skills/debug-live/SKILL.md) so it can be loaded into an
 > agent's prompt context independently of the MCP capability surface.
 
 ### 🎯 Debugging Best Practices

docs/architecture/debugMCPServer.md

@@ -39,7 +39,7 @@ AI Agent (MCP Client)
 
 `DebugMCPServer` exposes **tools only**. Procedural workflow guidance (when to debug,
 how to structure a root-cause investigation, language-specific quirks) lives in the
-companion Agent Skill at `skills/really-debug/SKILL.md`, not in tool descriptions or MCP
+companion Agent Skill at `skills/debug-live/SKILL.md`, not in tool descriptions or MCP
 resources. This separation matches modern agent ecosystems where MCP servers provide
 *capabilities* and skills provide *procedural knowledge* an agent loads as context.
 
@@ -58,7 +58,7 @@ Each request creates a new stateless `StreamableHTTPServerTransport` instance th
 - Class definition: `src/debugMCPServer.ts`
 - Tool registration: `setupTools()` method (uses `McpServer.registerTool()`)
 - Server startup: `start()` method (creates express app with `/mcp` route)
-- Agent Skill (companion, not part of the MCP surface): `skills/really-debug/SKILL.md`
+- Agent Skill (companion, not part of the MCP surface): `skills/debug-live/SKILL.md`
 
 ## Exposed Tools
 

package-lock.json

@@ -2,7 +2,7 @@
   "name": "debugmcpextension",
   "displayName": "DebugMCP",
   "description": "Let AI agents debug your code inside VS Code — breakpoints, step-through execution, variable inspection, and expression evaluation. Automatically exposes itself as an MCP (Model Context Protocol) server for seamless integration with AI assistants.",
-  "version": "2.0.1",
+  "version": "2.1.0",
   "publisher": "ozzafar",
   "author": {
     "name": "Oz Zafar",
@@ -79,9 +79,17 @@
           "description": "Port number for the DebugMCP server"
         },
         "debugmcp.bindHost": {
-          "type": ["string", "array"],
-          "items": { "type": "string" },
-          "default": ["127.0.0.1", "::1"],
+          "type": [
+            "string",
+            "array"
+          ],
+          "items": {
+            "type": "string"
+          },
+          "default": [
+            "127.0.0.1",
+            "::1"
+          ],
           "markdownDescription": "Network interface(s) the DebugMCP HTTP server binds to. **Defaults to `[\"127.0.0.1\", \"::1\"]` (IPv4 + IPv6 loopback only).** Accepts a single string or an array of strings. ⚠️ **Security warning:** changing this to `0.0.0.0` or a LAN address exposes the unauthenticated MCP debugger — including arbitrary code execution via `evaluate_expression` and `start_debugging` — to every host on the network. Only change this if you fully understand the risk."
         }
       }

package.json

@@ -1,5 +1,5 @@
 ---
-name: really-debug
+name: debug-live
 description: Drive an interactive VS Code debugger to investigate bugs, failing tests, wrong/null variable values, unexpected runtime behavior, and other "it doesn't work" reports. Use this skill whenever speculation about runtime behavior would be cheaper to *verify* by stepping through the code than to reason about. Pairs with the DebugMCP MCP server, which exposes the underlying breakpoint / step / inspect tools.
 license: MIT
 allowed-tools: