VS Code ships Copilot browser tools for web app validation

• VS Code shipped Copilot browser-agent tools for building and validating web apps, with the update pointing readers to the full changelog and VS Code's launch post.
• The new Agents window is in preview for parallel agent workflows, and Pierce Boggan's demo shows grouped chats, workspace-less chats, and bring-your-own-key setup.
• The same Copilot wave adds model discovery for BYOK, cost visibility, Autopilot improvements, and new VS Code Learn courses, according to VS Code's launch post.
• Agentic sessions can use Git worktrees for isolation; Boggan's reply says choosing the “Local” option avoids creating one.

The official 1.128 release notes are the page to keep open. Boggan's short demo is the fastest look at the Agents window changes, while his worktrees reply answers the first operational question teams will hit when parallel agents start cloning or isolating workspaces.

VS Code framed the headline Copilot change as browser-agent tooling for web app work: build the app, open it in a browser, validate behavior, then loop back into the editor.

The practical shift is that browser validation is now part of the Copilot surface in VS Code, rather than a separate manual handoff after code generation. The launch post groups it with Autopilot improvements, model discovery for BYOK, and cost visibility.

The Agents window is the preview feature for running and managing parallel agent workflows.

Boggan called out three visible changes in 1.128:

• grouped chats
• workspace-less chats
• bring-your-own-key setup

The demo also matters because it shows the feature as an editor workflow, not just a Copilot Chat sidebar update.

VS Code's launch post puts bring-your-own-key support next to two management features: model discovery and cost visibility.

That pairing is the useful part. BYOK without discovery and spend feedback turns into another settings maze; VS Code is exposing the controls beside the agent workflow.

Parallel agents create a boring but real repo problem: where does each session write files?

Boggan said one reported extra checkout came from Git worktrees, used “for isolation between agentic sessions.” His reply also gives the behavior split:

• choose the dropdown's “Local” option to avoid creating a worktree
• add an already-cloned repo from its existing folder if VS Code opens a separate clone

Git's worktree docs describe the underlying mechanism: multiple working trees can attach to the same repository.

The release wave was not only agent plumbing. VS Code also promoted the CodeSnap extension for faster code screenshots, and the Copilot changelog mentioned new VS Code Learn courses.

CodeSnap is a small quality-of-life ship, but it fits the same pattern as the agent work: VS Code is pulling more of the developer loop into editor-native tools.