Text of code.visualstudio.com › updates › v1_140 as Styx crawled it on Oct 10, 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.140

🎬 Watch The Story of VS Code! VS Code is now on Instagram, follow @vscode.ig for updates, tips, and more. Rewatch GitHub Copilot Day. Visual Studio Code 1.140 Released September 30, 2026 Stable Downloads for 1.140.0 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Already installed? Use Check for Updates in VS Code. For upcoming features, use the Insiders build . Release highlights This release expands agent workflows, improves worktree reuse, and adds enterprise AI controls.

Copilot harness : Use the Copilot harness and get consistent agent behavior across Copilot products. Multi-folder sessions (Experimental) : Work on tasks across multiple folders within a single agent session. Remote delegation (Experimental) : Delegate tasks to connected remote agent hosts. HydraFusion (Research Preview) : Let multiple models draft, critique, and revise coding tasks without coordinating them yourself.

Shared worktree folders (Experimental) : Avoid repeated dependency installs and duplicated artifacts by reusing ignored folders across worktrees. Enterprise controls : Ensure everyone in your org follows AI version requirements and defaults. Agents Copilot harness The Copilot harness adds exciting new agent functionality to VS Code while keeping the way you work familiar. It's powered by the Copilot SDK, so its behavior and capabilities are consistent with other Copilot products, including the standalone GitHub Copilot app and the Copilot CLI.

To start using the Copilot harness, select it from the harness picker in the chat input. In this release, it might already be the default selection for you. You can continue working as you normally do. The harness runs in a dedicated agent host process based on the Agent Host Protocol (AHP), so you can connect to the same agent session from multiple VS Code windows. Learn how to work with the Copilot harness , or explore the architecture and workflows in the agent host blog post .

If you have feedback or requests, please file an issue . HydraFusion model orchestration (Research Preview) HydraFusion is an adaptive model orchestration system that chooses the models and workflow for each coding task. It can solve a task with one model, escalate to a stronger model, or have another model critique and revise the result. This approach aims to improve result quality while balancing speed and cost, without requiring you to coordinate models yourself.

Eligible users with preview features enabled can select HydraFusion in the model picker. Multi-folder sessions (Experimental) Multi-folder sessions let you coordinate related work across repositories or isolated worktrees in one session. Previously, every chat in a multi-chat session shared the same folder and checkout. In this release, each chat can use its own folder or worktree without changes leaking between chats.

Each chat uses its folder for its terminal, tasks, changes, pull request, and Agent merge state. Chats that use the same folder share that state. In the sessions list, hover over a session to see a summary across all its folders, or hover over a nested chat to see details for only its folder. Example use cases include: Implement a feature across repositories : Ask the main chat to work in one repository and create a peer chat for a second repository.

Compare approaches in separate worktrees : Ask the main chat to create peer chats that each use a fresh worktree of the same repository. Each approach gets its own branch, changes, and pull request. Multi-folder sessions are experimental and disabled by default. The settings are not shown in the Settings editor. In your user-scoped settings.json file, set the setting for your harness to true , and then create a session: Copilot: chat.agentHost.copilotAgent.multiRootEnabled Open in VS Code Open in VS Code Insiders Claude: chat.agentHost.claudeAgent.multiRootEnabled Open in VS Code Open in VS Code Insiders Codex: chat.agentHost.codexAgent.multiRootEnabled Open in VS Code Open in VS Code Insiders New sessions pick up setting changes without restarting the Agent Host.

There is no UI for adding a folder or choosing the folder of a peer chat, so ask the main chat to create the peer chat and describe the repository or worktree it should use. Archive chats in a session Keep the rest of a session active when one chat finishes its work. Because sessions can contain multiple chats, select Mark as Done to archive only the finished peer chat, not the entire session. To restore it with its title and transcript intact, select the Done filter in the sessions list.

Automatic Dev Container cleanup Settings : chat.agentHost.devContainer.enabled Open in VS Code Open in VS Code Insiders , chat.agentHost.devContainer.idleTimeout Open in VS Code Open in VS Code Insiders (Agents window only) When all sessions that use a Dev Container are inactive for five minutes, VS Code stops the container. It restarts automatically when you continue working. Marking as done or deleting the last session removes the container.

Faster Dev Container startup Setting : chat.agentHost.devContainer.enabled Open in VS Code Open in VS Code Insiders (Agents window only) Dev Container sessions let agents use your project's tools and dependencies in an isolated environment. Fresh containers can reuse cached VS Code Server and CLI downloads, which reduces setup time and repeated downloads across projects. Choose the session relationship and workspace for delegated work Make two separate decisions when you ask an agent to delegate work.

First, decide whether the task belongs to the current session's plan or deliverable. Then specify a workspace only if the task needs repository files, and request a worktree only if file changes need isolation. Related work can still use a different workspace. Create a peer chat for related work : Ask the agent to create a peer chat in the current session. To reuse the current workspace and checkout, say so in your prompt.

Because the peer chat shares the checkout, use this option for research, planning, or related work that doesn't need isolated file changes. Create a peer chat in this session that reuses the current workspace and checkout to review the authentication flow. Do not modify files. Create an independent session for unrelated work : Ask the agent to create an independent session with no workspace when a separate deliverable doesn't need repository files.

The new session doesn't inherit the source folder. If the work does need a repository, name the project or folder and explicitly request a worktree when its changes need isolation. Create an independent session with no workspace to research licensing options for a separate project. Learn more about orchestrating chats and sessions . Create workspace-less chats on remote agent hosts Setting : sessions.chat.unifiedWorkspacePicker.enabled Open in VS Code Open in VS Code Insiders (Agents window only) Agent Host lets you run and track agent sessions on a remote host.

This release adds support for running workspace-less chats on a remote host. Select a connected host from the unified workspace picker without choosing a workspace. The Chat entry identifies the selected host, so you can confirm where the session runs before you start. Remote folders also appear alongside local folders in the main picker. This makes frequently used remote workspaces easier to select without opening the Remote submenu.

Delegate tasks to remote agent hosts (Experimental) Settings : chat.remoteAgentHostsEnabled Open in VS Code Open in VS Code Insiders , chat.remoteSessions.tools.enabled Open in VS Code Open in VS Code Insiders (Agents window only) Your agent can delegate work to connected remote agent hosts from the Agents window, without you selecting a host in a picker for each task. The new built-in tools let your agent: Discover hosts, models, resource capacities, and session load with list_agent_hosts .

Start a session with create_remote_session . Spec

The rest of this page is on the live site.