v0.4.0

v0.4.0

Released 2026-06-30

Highlights

• Connect more than Claude Code — a new harness manager registers the debug server with Claude Code, opencode, and Codex, plus a portable project .mcp.json, each installable at user or project scope.
• The server now appears automatically in VS Code's built-in MCP server list, so the native agent discovers it with no hand-written config.
• Requires VS Code 1.101 or newer — the minimum engine was raised from 1.90 to enable the native MCP registration API.

Added

• Harness manager (Debug MCP: Manage AI Harnesses…, also on the status-bar menu): a webview with one card per AI tool showing detected/configured state and Install/Uninstall buttons for both user and project scope.
• Native VS Code MCP discovery via vscode.lm.registerMcpServerDefinitionProvider, so the vscode-debug server shows up in VS Code's own MCP UI and the built-in agent without an mcp.json.
• opencode support — writes a local MCP server entry to ~/.config/opencode/opencode.json (user) or ./opencode.json (project).
• Codex support — writes an [mcp_servers.vscode-debug] table to ~/.codex/config.toml (user) or ./.codex/config.toml (project). Project scope warns that Codex only loads project config for trusted directories.
• Project-scope installs for every harness: Claude Code writes a shared .mcp.json at the repo root; opencode and Codex write their project config files; and a portable .mcp.json target works with any MCP client.
• A user/project conflict warning before adding a project entry when the same tool is already configured at user scope.

Changed

• First-run setup now offers a single prompt that opens the harness manager, and the “don't ask again” choice is tracked per tool. Reset with Debug MCP: Reset Install Prompts.
• Activation self-heal now re-points stale user-scope registrations for every configured harness, not just Claude Code.
• The status-bar menu's install entry was replaced by "Manage AI harnesses…"; the old Install/Uninstall Claude Code commands now open the manager (the configure command is kept as an alias).
• Sample workspace docs no longer reference the removed HTTP endpoint; the extension serves a per-window MCP server automatically.

Removed

• The standalone Uninstall Claude Code Support… command — uninstall is now per-card in the manager.

---

Install the .vsix attached to this release via:

code --install-extension vscode-debug-mcp-0.4.0.vsix

v0.3.0

v0.3.0

Released 2026-05-30

Highlights

• Each VS Code window now runs its own MCP server on a private Unix socket — no more shared TCP port and no leader/follower coordination between windows. Claude Code reaches the right window automatically.
• Claude Code is now wired up over a stdio bridge instead of an HTTP URL. One user-scope registration works in every workspace; the extension self-heals the registration across updates.

Added

• Per-window MCP server over a Unix domain socket (named pipe on Windows), derived deterministically from the workspace folder so each window is independently addressable.
• A small stdio bridge (out/bridge.js) that Claude Code spawns and that connects to the current window's socket. It resolves its workspace from CLAUDE_PROJECT_DIR, retries transparently if the window is reloading, and falls back to a per-user registry for multi-root or same-folder-twice cases.
• The Claude Code installer self-heals: on activation it re-points an existing vscode-debug registration at the current build if the bridge path is stale (e.g. after an extension update).

Changed

• The Claude Code installer now registers a single stdio server named "vscode-debug" at user scope. The tool prefix (mcp__vscode-debug__*) is unchanged, so existing skills, prompts, and permission allowlists keep working. An existing HTTP "vscode-debug" entry is replaced in place on next activation.
• The scope picker is gone — one user-scope entry works in every window, so there's no per-project .mcp.json to manage.
• The status bar and menu reflect the single-window model; the express dependency is dropped, shrinking the bundle by roughly 60%.

Removed

• The HTTP/Streamable-HTTP MCP server and the cross-window leader/follower coordination layer.
• The bind_workspace and list_workspaces tools — with one server per window there is nothing to demux.
• The vscodeDebugMcp.port and vscodeDebugMcp.host settings (no TCP port is bound any more).

---

Install the .vsix attached to this release via:

code --install-extension vscode-debug-mcp-0.3.0.vsix

v0.2.2

v0.2.2

Released 2026-05-27

Highlights

• Quieter startup — Debug MCP no longer pops information toasts when the server starts, restarts, or a follower joins a leader. Status is shown in the status bar and the Debug MCP output channel instead.

Changed

• Removed the "Debug MCP already active", "Debug MCP running at … (leader)", and "Debug MCP joined as follower …" information toasts. Errors and explicit user actions (copy URL, configure Claude Code, etc.) still show toasts; routine lifecycle events only log to the output channel now.

---

Install the .vsix attached to this release via:

code --install-extension vscode-debug-mcp-0.2.2.vsix

v0.2.1

v0.2.1

Released 2026-05-25

Highlights

• Fix MCP server dying after ~15 minutes of idle SSE stream — the most common stability issue reported on v0.2.0.

Fixed

• SSE stream on GET /mcp no longer drops after ~15 minutes idle. The MCP SDK does not emit application-level keepalives on its standalone SSE stream, so an idle connection was being torn down at the OS/network layer (~899s). The Node HTTP server now uses permissive idle timeouts and enables TCP keepalive on every accepted socket so the connection survives long idle periods between tool calls.

---

Install the .vsix attached to this release via:

code --install-extension vscode-debug-mcp-0.2.1.vsix

v0.2.0

v0.2.0

Released 2026-05-24

Highlights

• First release published to the VS Code Marketplace — install from inside VS Code without a .vsix download.
• Extension is now bundled with esbuild — install size dropped from 2.78 MB / 1837 files to 424 KB / 8 files, and activation is faster.
• MCP server identity now reports the actual package version instead of a hardcoded 0.1.0.

Added

• Marketplace publication under the cgaspard.vscode-debug-mcp listing.
• esbuild-based bundling pipeline (npm run compile / npm run watch / npm run build:production) producing a single out/extension.js.

Changed

• tsconfig.json is now noEmit: true and used only for typechecking; all emission goes through esbuild.
• .vscodeignore excludes node_modules/** entirely now that dependencies are bundled into the extension binary.
• MCP server serverInfo.version is sourced from package.json at build time so it always matches the release.

---

Install the .vsix attached to this release via:

code --install-extension vscode-debug-mcp-0.2.0.vsix

v0.1.4

v0.1.4

Released 2026-05-24

Highlights

• Read state from debug sessions the user started — not just ones the AI launched. When the user hits F5 and runs into a breakpoint, the AI can now see it via list_debug_sessions / get_last_stopped_event.
• The most-recent stopped event (file, line, frame, stack trace) is captured at pause time and remains queryable even after the user continues execution.
• Skill rewritten with "check for an existing user-started session FIRST" as rule #1 — the most common workflow, finally treated as primary.
• Installed skill auto-refreshes on extension upgrade so the user gets new guidance without re-running the installer.

Added

• SessionRegistry that tracks every debug session via DebugAdapterTracker — start, run, pause, continue, terminate. Records the latest stopped event per session with thread, reason, frame, and a 10-level stack snapshot.
• list_debug_sessions tool — returns one entry per active or recently terminated session with { id, name, type, status, isActive, startedAt, lastStopped? }. Available via MCP and the Copilot Language Model Tools API.
• get_last_stopped_event(sessionId?, levels?) tool — detailed snapshot of the most recent pause. Defaults to the active session, falls back to the most recently paused one. Returns frame + stack trace even if the user has already continued execution.
• Skill auto-refresh — on extension activation, if ~/.claude/skills/debug-mcp/SKILL.md exists, it's overwritten with the bundled copy from the new extension version. Idempotent; no-op when contents already match.

Changed

• Skill rewritten end-to-end. Rule #1 is now "list_debug_sessions BEFORE doing anything when the conversation involves runtime behavior." User-paused-at-breakpoint is the lead playbook; AI-started session is secondary.
• README adds a "The most common workflow: user-started debug sessions" section above the architecture diagram so the capability is discoverable.

---

Install the .vsix attached to this release via:

code --install-extension vscode-debug-mcp-0.1.4.vsix

v0.1.3

v0.1.3

Released 2026-05-24

Highlights

• Initial release. Drive your VS Code debugger, launch configs, tasks, terminals, and debug console from AI assistants — over MCP (Claude Code, Cursor, Windsurf) or VS Code's Language Model Tools API (Copilot agent mode, no MCP setup needed).
• Cross-window cluster — multiple VS Code windows share one MCP server. The leader window owns the HTTP endpoint; followers join over IPC. Discovery is by port probing (no lockfile).
• Auto-updates from GitHub Releases. One-line installer, no marketplace needed.

Added

• Streamable HTTP MCP server bound to 127.0.0.1:6736 by default.
• Language Model Tools integration so Copilot agent mode can use the same capabilities without an MCP client. Write-y tools (start/stop debug, run/stop task, set/clear breakpoints, run in terminal, evaluate) confirm with the user before invoking; read-only tools run silently.
• One-click installer for Claude Code. Workspace scope writes .mcp.json into the project (git-shared). User scope shells out to 'claude mcp add --scope user' so the registration lands in ~/.claude.json where Claude Code actually reads user-scope MCP from.
• debug-mcp usage skill installed globally at ~/.claude/skills/debug-mcp/ regardless of MCP scope — skills are description-gated, so a global install only activates in debugging-relevant conversations. Teaches Claude to prefer launch.json + tasks over raw Bash, and to call list_workspaces / bind_workspace at the start of multi-window sessions.
• Smart re-prompting — the install prompt fires whenever the current workspace isn't configured AND user scope isn't configured. Picking 'Don't ask again' suppresses it permanently (until you run 'Reset Install Prompt'). Picking a scope and completing the install does NOT suppress prompts in other workspaces — opening a different repo with no .mcp.json will still prompt if you only configured workspace scope.
• 'Debug MCP - Uninstall Claude Code Support…' command — multi-select picker to remove user-scope registration, current workspace .mcp.json entry, and/or the global skill.
• Best-effort cleanup of the global skill on extension uninstall (deactivate hook).
• Multi-window cluster — first VS Code window to start becomes the leader and owns the HTTP server; subsequent windows register as followers over a Unix socket. The leader exposes GET /cluster so new windows can discover it after port-probe.
• list_workspaces and bind_workspace MCP tools so the AI can route tool calls to a specific window. Workspace ids are sha256(path).slice(0,12) — stable across restarts.
• Launch tools — list_launch_configurations, start_debugging, stop_debugging, continue/pause/step_over/in/out.
• Debug state tools — get_threads, get_stack_trace, get_scopes, get_variables, evaluate_expression.
• Breakpoint tools — set/remove/toggle/clear, get_all_breakpoints, get_breakpoint.
• Task tools — list_tasks, run_task, list_running_tasks, stop_task.
• Terminal capture via shell-integration with read_terminal, list_terminals, clear_terminal_buffer, run_in_terminal.
• Debug console capture via DebugAdapterTracker with read_debug_console, clear_debug_console_buffer, eval_in_debug_console.
• GitHub-release auto-updater — checks every 6 hours, offers in-product install of the latest .vsix. Manual check via 'Debug MCP - Check for Updates'.
• Status-bar menu with context-aware actions — install / reconfigure Claude Code, copy URL, start/stop, check for updates, open log. Status bar shows role: '(leader)', '(follower)', or unadorned for standalone.
• Sample workspace under sample-workspace/ for end-to-end testing.
• Leader failover — when the leader window closes, followers automatically retry the discovery flow and the next candidate naturally becomes the new leader.
• Clear error message when the configured port is held by something other than Debug MCP, instead of a raw EADDRINUSE trace.
• Architecture diagram + workspace-routing explanation in README.

---

Install the .vsix attached to this release via:

code --install-extension vscode-debug-mcp-0.1.3.vsix