Text of code.visualstudio.com › updates › v1_136 as Styx crawled it on Nov 18, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Visual Studio Code 1.136

Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. Visual Studio Code 1.136 Follow us on LinkedIn , X , Bluesky , Instagram Release date: September 2, 2026 Update 1.136.1 : The update addresses these issues . Update 1.136.2 : The update addresses these security issues . Downloads for 1.136.2 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the 1.136 release of Visual Studio Code.

This release helps you finish pull requests with agents and manage agent work across complex workspaces and related chats. Agent merge (Preview) : Resolve review feedback, failed checks, and merge conflicts until your pull request is ready to merge. Multi-root workspaces (Experimental) : Work with Copilot and Claude agent sessions across all folders in a multi-root workspace. Chat backgrounds (Experimental) : Personalize the Agents window with built-in patterns or your own images.

Chat sessions : Organize related chats in a session hierarchy and quickly see which ones need your attention. Happy Coding! VS Code is rolling out gradually to all users. Use Check for Updates in VS Code to get the latest version immediately. To try new features as soon as possible, download the nightly Insiders build , which includes the latest updates as soon as they are available. The Story of VS Code: World Premiere Discover the story behind VS Code, from its early beginnings to the platform millions of developers use today, and the community that helped shape it along the way.

Premiere: September 4 at 8:00 AM PT. Join us! Agents Multi-root workspaces in editor window (Experimental) Settings : chat.agentHost.copilotAgent.multiRootEnabled Open in VS Code Open in VS Code Insiders , chat.agentHost.claudeAgent.multiRootEnabled Open in VS Code Open in VS Code Insiders Copilot and Claude agent sessions in the editor window Chat view support multi-root workspaces . This capability is currently scoped to the editor window.

Agent hooks remain scoped to a single workspace folder. If hooks are detected in multiple folders, VS Code prompts you to select the primary folder from which to load them. Redesigned new-session input Start delegated work with less setup in the redesigned new-session input. The updated experience brings the prompt, model selection, workspace selection, and other session controls together in one layout. Improved workspace resolution Agents can resolve workspaces by their project name in addition to absolute paths and workspace URIs.

Session tools also preserve project URIs and all working directories for multi-root workspaces. As a result, you can make requests such as "run this in the vscode workspace" without providing a full path. If multiple workspaces have the same name, the agent reports the possible matches instead of silently choosing one. Remote workspace URIs are supported as well. Navigate related chats and sessions Keep related agent work organized and move between sessions and chats from the sessions list in the Agents window.

Chats appear as children of their parent session, so you can understand which chats belong together without managing a collection of unrelated sessions. Each chat row shows its own title, status, and pending approvals, so you can see which chat needs your input. Expand or collapse the hierarchy, and open, rename, move, or delete individual chats directly from the tree. When an agent delegates independent work to multiple chats, each created chat gets a meaningful title and appears in this hierarchy.

The new session or chat is placed close to its source, and the receiving request includes a source link such as Sent by another session or Sent from another chat . Select the link to return to the exact session or chat that initiated it. Readable breadcrumbs for session files Files created in the internal session state directory previously showed internal session identifiers in editor breadcrumbs. Breadcrumbs now use stable provider and session labels, making it easier to identify the file location without exposing implementation details.

Chat backgrounds in the Agents window (Experimental) Settings : chat.agentSessions.preferredDarkBackgroundImage Open in VS Code Open in VS Code Insiders , chat.agentSessions.preferredLightBackgroundImage Open in VS Code Open in VS Code Insiders , chat.agentSessions.backgroundImageLayout Open in VS Code Open in VS Code Insiders Personalize the Agents window with a decorative chat background: either a theme-aware pattern of built-in VS Code icons or an image of your own.

Run Chat: Set Background... to choose between the Codicons pattern and an image from your machine. The five images you used most recently are offered under Recently Used , and that list is kept on this machine only. When you bring your own image, run Chat: Change Background Layout... to place it. Eleven layouts are available: Repeat , Stretch , Center , and each edge and corner. Moving through the list previews each layout in place, so you can judge the result before committing to it.

Chat: Clear Background returns to the plain surface. Dark and light themes keep separate backgrounds. Every dark theme shares chat.agentSessions.preferredDarkBackgroundImage Open in VS Code Open in VS Code Insiders and every light theme shares chat.agentSessions.preferredLightBackgroundImage Open in VS Code Open in VS Code Insiders , so switching between a dark and a light theme swaps the background along with it. High contrast themes suppress backgrounds entirely, and the three commands are unavailable there.

Chat content carries its own fill so that it stays readable over whatever sits behind it. Your request remains fully opaque, agent responses fade out through the padding on either side, and wide content such as Markdown tables and terminal output stays fully backed. Learn more about personalizing chat . Agent session notifications Settings : chat.notifyWindowOnConfirmation Open in VS Code Open in VS Code Insiders , chat.notifyWindowOnResponseReceived Open in VS Code Open in VS Code Insiders VS Code can notify you when an agent session needs your input or finishes its work.

This is especially useful when you delegate work across multiple sessions, workspaces, or VS Code windows. By default, notifications only appear when the VS Code window is not focused. You can configure notifications separately for sessions that need input and sessions that have received a response. Notifications include a direct link back to the relevant session, so selecting one focuses the correct window and opens the session that needs attention.

Agent merge (Preview) Setting : chat.agentMerge.enabled Open in VS Code Open in VS Code Insiders Agent merge helps you take a pull request across the finish line. It asks an agent to address review feedback, fix failed checks and merge conflicts, and rerun workflows. Agent merge repeats this process until the pull request is ready to merge. To try agent merge, enable chat.agentMerge.enabled Open in VS Code Open in VS Code Insiders .

You can currently enable agent merge for a session only from the Agents window. Run Enable Agent Merge for Active Session or select the Agent Merge button in the title bar. Learn more about using agent merge . Agent host The agent host lets you connect to the same agent session from multiple VS Code windows. It runs agent harnesses in a dedicated process based on the Agent Host Protocol (AHP). The agent host's Copilot agent is powered by the Copilot SDK , which aligns the agent's behavior and functionality with the Copilot CLI, the standalone GitHub Copilot app, and other Copilot products.

We're actively developing the agent host. The following screenshot shows the Copilot harness selected for an agent host in an editor window: Learn more in the agent host documentation and our new agent host blog post , where we share why we built the agent host, what it enables in VS Code, how the architecture and

The rest of this page is on the live site.