VS Code 1.136

[Agents] Agent merge (Preview): Setting: chat.agentMerge.enabled 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 . 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.

[Agents] 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 open protocol work, and workflows you can try yourself. If you have any feedback or requests, please let us know by filing an issue.

[Chat] Enterprise controls for dictation data: Administrators can manage the dictation model and language-model transcript cleanup through enterprise policies. The new controls make it possible to require on-device transcription and disable language-model cleanup, so dictation remains available while preventing dictation data from being sent to cloud transcription or a Copilot model. Learn more about enterprise controls for dictation data.

[Agents] Multi-root workspaces in editor window (Experimental): Settings: chat.agentHost.copilotAgent.multiRootEnabled , chat.agentHost.claudeAgent.multiRootEnabled 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.

[Agents] 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.

[Agents] 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.

[Agents] 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.

[Agents] Agent session notifications: Settings: chat.notifyWindowOnConfirmation , chat.notifyWindowOnResponseReceived 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.

[Editor experience] Layout density for the editor window (Experimental): Settings: workbench.experimental.modernUI , window.density.layout Fit more content in the editor window with the Compact layout density. When workbench.experimental.modernUI is enabled, you can choose between two layout densities: Default layout density is the same as the current editor window layout. Compact layout density removes the spacing between panels and reduces inner panel spacing. This setting is available in the Layout Density section of the Settings menu and can also be set using window.density.layout .

[Agents] 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.

[Agents] Chat backgrounds in the Agents window (Experimental): Settings: chat.agentSessions.preferredDarkBackgroundImage , chat.agentSessions.preferredLightBackgroundImage , chat.agentSessions.backgroundImageLayout 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

[Accessibility] Screen Reader Optimized badge in the Agents window: The Screen Reader Optimized badge in the Agents window title bar makes the active accessibility mode easier to identify. The badge appears when Screen Reader Optimized mode is enabled. Select the badge to disable this mode.

[Integrated browser] Spell check suggestions: Right-click a misspelled word in an editable field to select a suggested correction. In sessions that use persistent data storage, you can also select Add to Dictionary.

[Code editing] Word wrapping improvements: Injected text no longer pushes wrapped lines outside the editor viewport. Word wrapping takes the visual width of color decorators, inlay hint spacing, inline progress indicators, and breakpoint placeholders into account. Please have a look below for the before and after screenshots. On the picture above you can see that rgba is slightly cropped. While on the second picture it isn't.

[Terminal] Reduced delay when running commands: Terminal commands executed by extensions no longer incur an unnecessary delay when shell integration is ready under certain timing conditions. Users of the JavaScript debugger who hit this case will no longer experience a five-second delay when starting their programs.