Playbooks · Coding tasks
Visual Studio 2026 runs on the Copilot SDK
Written November 12, 2026
Visual Studio's new Copilot Chat is now the default for eligible accounts, and underneath it sits the same Copilot SDK that powers the Copilot CLI and the GitHub Copilot app. The setting that matters day to day is the split the update introduces: how long the agent keeps working, and what it may run, are now two separate choices.
One foundation under the Copilot products
The 18.12.0 release notes, for the November update released November 10, 2026, describe a new Copilot Chat experience that is the default for eligible accounts, unless the account has explicitly switched off editor preview features. Behind the scenes it is built on the Copilot SDK, the shared foundation used by the Copilot CLI and the GitHub Copilot app, so improvements made for those products reach Visual Studio faster. The notes frame it as the next step from Agent (Preview), the first Visual Studio experience built on the SDK.
Autopilot and Manual are separate switches
Conversation mode and tool permission are chosen independently. Interactive is the usual request-and-response flow. Autopilot keeps working until the agent considers the task complete. For tools, Manual and Allow all are separate: with Autopilot and Manual together, any tool that is not configured for automatic approval is rejected rather than left waiting for a prompt — the agent does not stall, the call simply fails. Choosing Allow all shows a warning. Both modes are saved with the session and restored when you return, and defaults for each can be set in Options. That rejection behaviour is the detail to internalize before turning Autopilot on for a long task: an unconfigured tool mid-run is a dead end, not a pause.
Sessions, trust and agent files
The new experience keeps several Chat sessions open in separate tabs, with pop-outs on by default, and Copilot can receive your active file, cursor or selection, file length and visible range, under settings that control whether that context is included and refreshed before tool calls. Trust gets its own list: Copilot trusted paths are managed separately from workspace trust, and Copilot no longer inherits trust just because a workspace is trusted, a path sits in a well-known location, or the general trust service is off. Custom user agents now live in %USERPROFILE%\.copilot\agents by default, matching the Copilot CLI. Visual Studio does not move existing files, so agents in the old .github\agents folder need a manual move or an explicit setting. The same release adds a Test agent in the agent picker, crash-dump analysis started from the dump summary page, and a Debugger MCP with conditional breakpoints and structured inspection of a frame's locals and arguments.
Limits
- The new Chat is the default for eligible accounts, not for every installation at once. If it has not arrived, that is the rollout, not your settings.
- There is an exit: turn off Use new Copilot chat experience under Tools, Options, GitHub, Copilot, Copilot Chat, and restart. Going back also restores the previous testing agent.
- This page covers the Copilot sections of a long release. The November update also carries large IDE, performance and C++ changes that are separate stories.
Related playbooks
- Bring your own agent into Android Studio, and switch when its quota runs out
- Don't resume an Agent SDK session from an untrusted ID
- Cloudflare runs the Codex loop in a Durable Object
- Decide whether Copilot's assisted permissions should approve anything for you
Sources
Back to: Coding tasks playbooks hub · Also: ReSharper 2026.3 brings Claude and Codex in · Copilot CLI now configures MSBuild itself