Skip to content
← Back to Articles

Visual Studio Weekly: The New Copilot Chat Becomes the Default

┬╖ 5 min read
Developer Experience AI Visual Studio Productivity

Visual Studio just stopped being a special snowflake in the Copilot ecosystem. With the November Update 18.12.0, released November 10, the new Copilot Chat is the default for eligible accounts, it’s built on the same Copilot SDK as the CLI, and it reads the same AGENTS.md file your other tools already use.

That’s the real headline. Not a new button. A convergence.

What shipped

Here’s the short version of 18.12.0, per the release notes:

AreaChange
Copilot ChatNew experience default for eligible accounts, built on the Copilot SDK
CustomizationAGENTS.md at solution root, org instructions, skill toggles, instruction browser
ModelsBring-your-own model API formats, multiple connections per provider
Debugging”Debug with Copilot” on the dump summary page
IDESolution Explorer File System view, MSBuild Restore in Open Folder
PerformanceFaster C++ solution parse and quicker large-solution close

The new Copilot Chat

The release notes say the new experience is built on the Copilot SDK, “the shared foundation used by the Copilot CLI and the GitHub Copilot app.” I’ve argued in my piece on the Copilot SDK that a shared agent runtime is the only sane way to ship agents across surfaces. Visual Studio moving onto it validates that thesis. Fixes and features land once and show up everywhere.

The practical changes are good ones:

One detail I like: Autopilot plus Manual means tools not configured for automatic approval are rejected rather than waiting on a prompt. That’s the correct failure mode for unattended runs. A stuck approval dialog is worse than a refused tool call.

Trusted paths, finally separate

Copilot no longer inherits trust just because a workspace is trusted or a path is in a well-known location. There’s a separate Copilot trusted paths list, persisted in settings and manageable by organization policy. If agents can run tools on your machine, trust should be explicit. Good call.

AGENTS.md and the end of per-tool instruction copies

This is the part that matters most to teams. Put your build steps, conventions, and testing guidance in AGENTS.md at the solution root, and Visual Studio’s Copilot uses it. The notes say you no longer need a separate copy “just for Visual Studio.”

# AGENTS.md
## Build
- `dotnet build MySolution.sln -c Release`
## Testing
- `dotnet test --no-build`; integration tests need Docker running
## Conventions
- Nullable reference types on; no `#pragma warning disable` without a comment

New sessions also pick up your organization’s Copilot custom instructions, refreshed in running and resumed sessions when they change, and custom agents receive them too. AI Customization now lets you browse instruction files by scope and enable or disable individual skills.

This is context engineering becoming a first-class IDE feature. The quality of what your agent does is a function of the context you give it, and one canonical file beats four drifting copies. For how custom agents fit in, my plan mode vs custom agents write-up covers it.

A migration gotcha

User custom agents now default to %USERPROFILE%\.copilot\agents, matching Copilot CLI, instead of %USERPROFILE%\.github\agents. Visual Studio doesn’t move existing files. Either move them or set the user-agent directory back explicitly. Workspace agents stay in the repo’s .github\agents. If your agents vanish after updating, this is why.

Bring your own model, with caveats

Model management now lets you choose an API format when adding a custom model: Completions or Responses for supported non-Anthropic providers, Messages for Anthropic. Existing configs migrate to each provider’s default (Messages for Anthropic, Completions for the rest), so check the format if your deployment expects the Responses API. You can also keep multiple configurations per provider, such as work and personal accounts. If you’re weighing which SDK or API surface to standardize on, choosing the right AI SDK is relevant.

Debugging: Copilot on crash dumps

Open a dump file, go to the Debug tab on the dump summary page, and select Debug with Copilot. Visual Studio starts the dump-debugging session and launches Copilot analysis automatically, tailored to the situation: an exception, an async hang where the main thread is waiting on a task, or a general analysis.

Dump analysis is tedious, high-value work, which makes it a great fit for an agent. The notes say results are best when the matching solution is open and source and symbols are available. No surprise: symbols are context too.

IDE and performance

File System view in Solution Explorer

Solution Explorer gets a File System view showing the repo as it exists on disk, including docs, build assets, and config files outside your projects. Double-click a solution file to open it, and right-click a project for Build, Rebuild, Clean, or Set as Startup Project. Use New Solution Explorer View to put Solution and File System side by side. For repos with several solutions, this is overdue.

Open Folder also gets a Restore action on supported solution or project files, which runs the MSBuild Restore target. It doesn’t apply to CMake or other build providers, and it excludes C++ .vcxproj files.

Faster loading and closing

The release notes cite about 20% less time in the measured Parse Solution phase for Chromium and 9% for Unreal Engine. They’re explicit that this is that phase, not total solution-load time, so don’t expect a 20% faster open. Closing large solutions also gets cheaper because it no longer rescans every open document for each removed project.

What it means

My opinion: the interesting story isn’t any single feature, it’s that Visual Studio is joining the shared-agent-infrastructure model. Same SDK, same AGENTS.md, same agents folder as the CLI. That’s what agentic development maturity looks like at the tooling layer: your configuration travels with you rather than being locked to an editor.

For enterprise .NET and C++ shops, org-level instructions plus path trust controls are what make this adoptable. Policy-managed trust and shared guidance are what security teams ask for.

Bottom line

Update to 18.12, move your agents to %USERPROFILE%\.copilot\agents, and consolidate your instructions into AGENTS.md. Then try Debug with Copilot on the next ugly dump. Visual Studio is converging on the same agent foundation as the rest of Copilot, and I expect every future release to lean harder on that shared runtime.


← All Articles