Visual Studio's new agent runs on the Copilot CLI engine

Microsoft shipped a new Agent (Preview) in Visual Studio 18.8's Copilot Chat, built on the GitHub Copilot SDK, the same engine that runs Copilot CLI. Per the Visual Studio Blog, the goal is consistent behavior across CLI, the GitHub app, VS Code and Visual Studio, not separate implementations per surface.

The SDK consolidation is what's worth watching, not the CLI-IDE parity promise. A single SDK means a fix or a regression in Copilot CLI now shows up in Visual Studio's chat agent too. If you use Copilot across more than one surface, you're no longer debugging four tools. You're debugging one engine wearing four different UIs.

The release also adds curated .NET and Azure skills you enable selectively, and Git branches join commits, changes and PRs as an attachable context type. Neither is the headline. The engine change is.

Shipping the CLI first and retrofitting the IDE onto the same core is the cheaper build order. CLI is faster to iterate on than an IDE surface. If that's what happened here, Visual Studio's agent inherits whatever Copilot CLI already worked through, for better and worse. The blog post doesn't say whether the reverse holds, whether IDE-specific bugs flow back into the CLI. It also doesn't say whether the surfaces diverge again as each adds skills like the .NET and Azure ones.