Visual Studio Code 1.146
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. Visual Studio Code 1.146 Release date: November 11, 2026 Stable Downloads for 1.146.0 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Release highlights Save your brainpower for the work that needs it. Inbox mode keeps the right sessions on your radar while agents take on model comparisons.
Shape your agent workspace around the task with chat windows and extensions. Inbox mode (Experimental) : Focus on sessions that need your attention across all your projects, and snooze others for later. Model comparison (Preview) : Compare results with Copilot Fusion in the mix, or let an agent run comparisons for you. Chat windows (Preview) : Give chats their own windows and rearrange chats, editors, and terminals to fit the task.
Extensions in the Agents window (Experimental) : Find and install extensions for a richer agent experience. Local harness deprecation : Move to the Copilot harness before the Local harness is removed in February 2027. Happy coding! Already installed? Use Check for Updates in VS Code. For upcoming features, use the Insiders build . Agents Copilot harness and deprecation of the Local harness The Copilot harness is our latest agent harness and has been the default for new sessions since VS Code 1.143 .
It's built on the Copilot SDK, a shared foundation that helps align behavior, capabilities, and improvements across Copilot products. Copilot harness sessions run through the Agent Host , so you can keep them running in the background and access them from both the VS Code editor window and the Agents window. For organizations, the Copilot harness also enforces managed sandbox and permission policies that the Local harness doesn't.
Thank you to everyone who has shared feedback on using the Copilot harness as your default. Your feedback has shaped the harness experience, and it will continue to guide us through this next step. As of this release, the Local harness is deprecated and will be removed in three months (February 2027) : Next three months : You can still use the Local harness while you move your workflows, but it's functionally frozen. New features and improvements will focus on the Copilot harness and are not guaranteed to be supported by the Local harness.
After three months : The Local harness will no longer be available. The vscode.temporaryDefaultToLocalHarness enterprise-managed setting, introduced in VS Code 1.142 to keep the Local harness as the default , will also be removed. Because the Copilot harness is already the default for new sessions, you might not need to take any new actions. To confirm you're using the Copilot harness, look for Copilot in the harness picker when you start a new session: If you still use the Local harness, plan to move completely to the Copilot harness before February 2027.
The Local-to-Copilot harness transition guide covers customization compatibility, continuing existing Local conversations, and organization rollout and verification. If you run into any problems, let us know by filing an issue . Inbox mode for sessions (Experimental) Setting : sessions.list.inboxEnabled Open in VS Code Open in VS Code Insiders Keep track of your agents without checking each workspace. Inbox mode gives you one view of what needs your attention, what's still running, and what's ready to merge.
Enable the sessions.list.inboxEnabled Open in VS Code Open in VS Code Insiders setting (off by default), and then select Grouping > Inbox Mode in the Agents window's sessions list. Sessions that need your attention appear at the top, above the Working , Ready to merge , On hold , and Done groups. If a session can wait, use Dismiss from Inbox , Put on Hold , or Snooze to set it aside. Select Undo if you change your mind.
Dismissing a session doesn't archive it. To archive it, select Mark Session as Done . Session list inline actions (Experimental) Setting : sessions.list.inlineActions Open in VS Code Open in VS Code Insiders Fix failing checks and address review comments directly from the Agents window's sessions list. Enable this setting (off by default) to show inline actions for fixing checks, addressing comments, or both. Each action sends a request to that row's session or nested session in the background without opening it.
The setting does not enable Agent Merge or change action permissions. Chat windows (Preview) Setting : sessions.chatWindows.enabled Open in VS Code Open in VS Code Insiders When several chats run at once, keeping them all in one Agents window means switching between them and losing sight of the one you are waiting on. With chat windows, you can open a chat in a window of its own, and arrange that window so that the chat, its editors, and its terminals fit the task.
To try this preview feature in Stable, enable sessions.chatWindows.enabled Open in VS Code Open in VS Code Insiders . It is enabled by default in VS Code Insiders, and off by default in Stable. Learn more about chat windows in our documentation. To open a chat in a new window, right-click the session or chat in the sessions list and select Open in > New Window . You can also drag a chat out of the Agents window to create a new window.
You can move it back with the Move to Main Window command. The following video shows opening a chat in its own window. A chat window can hold several chats from one or more sessions: pick another session in its title bar, drag a chat in from another window, or select New Session ( ⌘N (Windows, Linux Ctrl+N ) ) at the left of the title bar to start a new session in that window. Chat windows reopen with their chats and editors after you restart VS Code.
The content within a chat window is organized into parts, which you can arrange freely to fit your workflow. Move parts: Drag a part by the grabber on the top edge of its card to another side of the window, or beside another part. You can also use Move Part Left , Move Part Right , Move Part Up , and Move Part Down . Move tabs between parts: Drag a tab to another part, or drop it on a part's edge to split that part. Use Move Editor to Part or Move Editor into New Part Left/Right/Above/Below to do the same from the Command Palette.
Drag an editor tab onto the chat input to attach it to the chat as context. Place the terminal: Dragging the terminal under the editor or under the chat sets Terminal Position to Under Editor or Under Chat . Dropping it on the bottom edge of the window sets Full Width . You can also change the position from the ... menu of the terminal. Switch the layout: Use Configure Layout in the title bar to show the chat, the editor, or both, side by side or stacked.
In the stacked layout, Agents: Toggle Chat Conversation collapses the chat to only its input, so the editor takes the rest of the window. Use Developer: Reset Chat Window Layout to return a window to how it first opened. The following video shows rearranging a chat window and resetting its layout. Let us know what you think by filing an issue . Install and manage extensions in the Agents window (Experimental) The Extensions section of Agent Customizations lets you choose which installed extensions run in the Agents window without changing their enablement in editor windows.
Previously, adding an extension meant switching to an editor window to install it. In this release, you can find, install, and uninstall extensions without leaving the Agents window: Install from the Marketplace : Searching also queries the Marketplace and lists matching extensions that you don't have yet, with their publisher, install count, and rating. Installing an extension adds it to VS Code and enables it in the Agents window.
To install a different version, such as a pre-release, use the dropdown next to Install . Know what won't work before installing : Extensions that contribute views, debuggers, status bar items, or walkthroughs without
The rest of this page is on the live site.