VS Code 1.135 Lets You Pick Up an Agent Session in a Different App
The August release adds cross-application session continuity for coding agents and an experimental feature that gets a second opinion from a different model.
Microsoft published the August 2026 update to Visual Studio Code, version 1.135, on August 26. The headline feature lets a developer continue a Copilot or Claude agent session that was started in a different application, rather than treating each app's session as siloed.
The release also adds an experimental feature the team is calling "Rubber Duck," which routes a completed piece of agent work to a second, complementary model for a review pass before the developer sees the final result. Both features live in a reorganized Agents window meant to make longer chat and agent history easier to navigate at a glance.
This follows a pattern the VS Code team has kept up through the year: the February 2026 release focused on making agents practical for longer-running, more complex tasks with better visibility and control, and the run of releases from v1.127 through v1.131 in July concentrated on how developers review agent-proposed changes and navigate chat sessions generally.
The Agents window redesign is meant to address a specific pain point as agent sessions get longer and more numerous: chat history, active sessions, and usage information had been scattered across separate panels. Consolidating them into one window gives a developer a single place to check what an agent is currently doing, review what it has already done, and see how much of a session's budget or context window is left before starting something new.
As with every VS Code release, the update ships through the editor's normal auto-update mechanism, and the full changelog — including smaller fixes across debugging, extensions, and the terminal — is published on the VS Code website alongside every monthly release going back through the product's history. Microsoft has kept up a release like this every month for years, which makes that archive one of the more complete public records of how a single editor's feature set has evolved over time.