Visual Studio 2026 version 18.12 shipped on November 10, with patch release 18.12.1 following on November 17. Most of it is incremental. One feature is not: the Debugger Agent. Right-click a failing unit test, select Debug with Copilot, and the agent runs the test under the debugger, identifies the exact failure point, proposes a fix, validates it, and iterates — without you sitting there stepping through stack frames. That is not autocomplete. It is a closed-loop bug-fixing workflow running inside your IDE.
How the Debugger Agent Loop Works #
The workflow is deliberately minimal to trigger. When a unit test fails, right-click it in Test Explorer and select Debug with Copilot. The agent then:
- Reads the failing test, the code under test, and recent git commits.
- Queries exception history from GitHub or Azure DevOps — issues, pull requests, commits.
- Proposes a fix at the exact failure line.
- Runs the test under the debugger to validate.
- If the test still fails, it refines its hypothesis using live debugger state and tries again.
- Once passing, it delivers a plain-language summary of what changed and why.
You review proposed changes before anything lands. The agent can also interact with your running application — capturing UI screenshots, traversing the accessibility tree, and clicking controls to gather context that the stack trace alone cannot provide. That matters for UI-layer bugs where static analysis has always been weak.
Microsoft’s official write-up of the feature is on the Visual Studio Blog.
The Debugger MCP Server: What External Agents Can Access #
The bigger story for teams building their own tools is the built-in Visual Studio Debugger MCP server. As of 18.12, it exposes a structured API that any MCP-compatible agent — Claude Code, Codex, OpenCode, your own tooling — can call against a live debugging session:
- Conditional breakpoints with hit counts and tracepoints
- Frame locals inspection: names, types, values, drill-down capability
- Expression evaluation at a stopped frame
- Call stack traversal
- Current exception state
- Build output and Error List
The key call is debugger_get_locals: it returns every argument and local variable for a stopped frame with types and expansion hints. An agent can enumerate what is in scope before deciding what to inspect, rather than guessing expression names. It is a small API detail with an outsized effect on agent reliability.
New Copilot Chat Engine: 20% More Resolved Tasks #
18.12 moves Copilot Chat off Microsoft’s legacy in-house implementation and onto the unified Microsoft Copilot SDK — the same engine running in VS Code, Copilot CLI, and the GitHub Copilot app. It was opt-in in 18.11; it is now the default.
The benchmark: the new engine resolved 124 out of 157 C# coding tasks; the old engine resolved 103. That is 21 more resolved tasks — roughly a 20% improvement on the same test suite. The full benchmark methodology is documented on the Visual Studio Blog.
If the new engine causes regressions in your workflow, rollback is one checkbox away: Tools > Options > GitHub > Copilot > Copilot Chat — uncheck Use the new Copilot chat experience and restart.
Two Agent Commands Worth Knowing #
Type / in Copilot Chat to access built-in agents. Two that do not make it into most summaries:
- /security-review — a security-focused audit of your staged changes.
- /rubber-duck — routes Copilot’s draft plan to a second model for critique before executing, specifically to catch overconfident responses before they reach your code.
Agent skills written for the new SDK work across Visual Studio, VS Code, Copilot CLI, and the GitHub Copilot app without modification. Write once, run everywhere is now real for Copilot agents.
One Breaking Change: Live Share Is Gone #
Visual Studio 2026 18.12 no longer bundles Live Share. Previously installed extensions are disabled on 18.11.3 and later. The VS Code version of Live Share remains in maintenance mode — no new features.
If Live Share is in your team’s workflow, sort out an alternative before upgrading. The first VSSDK targeting VS 2026 18.12 specifically is also now available for extension authors; existing API assemblies remain intact, so most older extensions will not break immediately. The full release notes are on Microsoft Learn. If you are on 18.11.x, the update is available through the Visual Studio Installer.