VS Code: Agent Host Becomes the Default, Carefully
The team pushed Agent Host Copilot toward becoming the default chat provider while simultaneously hardening the plumbing underneath it—MCP enablement, tool ownership across clients, and telemetry consistency—and then walked the default rollout back behind an experimental flag after review.
Duration: PT2M39S
Episode overview
This episode is a short developer briefing from VS Code.
It explains recent repository work in plain language.
- Show: VS Code
- Published: 2026-07-17T13:06:05Z
- Audio duration: PT2M39S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's July 17th, 2026.
The headline today: VS Code is making Agent Host Copilot the default chat experience, but doing so cautiously, with a same-day course correction.
Tyler Leonhardt's PR 326086 threaded a new flag through the default session-type logic so first-time users land on Agent Host Copilot instead of Local, once the agent host is enabled. But just hours later, a follow-up commit gated that entire behavior behind a new experimental setting, chat dot default to Copilot…
Underneath that default-provider work, several PRs were fixing real cracks in the Agent Host foundation. Connor Peet landed two related fixes: PR 326063 reconciled MCP server enablement so disabling a server doesn't leave stale state in Copilot or Claude runtimes, and PR 326251 made that enablement persistent across…
Sandy Ostergaard-style fix from Sandy081, PR 326169, is in the same vein—a subagent progress indicator getting stuck because the client subscribed before the host had registered the resource. A race condition, not a logic bug.
Second theme: voice and dictation matured quickly. Three PRs from Ahmed and Cnops fixed barge-in protocol, streaming mode, and dropped narration handling,…