Visual Studio Code 1.143
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. Visual Studio Code 1.143 Follow us on LinkedIn , X , Bluesky , Instagram Welcome to the 1.143 release of Visual Studio Code. Downloads for 1.143.1 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 .
Update 1.143.1 : The update addresses these issues . Release highlights This release makes the Copilot harness the default for new sessions and adds tools to compare models, reclaim storage, run models locally, and navigate file changes. Copilot harness by default : The default for new sessions, built on the Copilot SDK, lets you switch between editor and Agents window. Compare models (Preview) : Run the same task with multiple models in the Agents window, then compare and combine their solutions.
Reclaim worktree storage (Experimental) : Free disk space by reviewing and removing inactive agent session worktrees. On-device models (Experimental) : Run MAI Code 1.1 Flash locally on your device for your agent tasks. Multi-diff file list (Experimental) : Keep an overview of and jump between changed files in the multi-file diff editor. Agents Copilot harness as the default The Copilot harness is now the default for new sessions in VS Code.
It's our latest harness, built on the Copilot SDK, a shared foundation that helps align behavior, capabilities, and improvements across Copilot products. When you start a new session, Copilot in the harness picker indicates that the session uses the Copilot harness: In VS Code, you can keep Copilot harness sessions running in the background and access them from both the VS Code editor window and the Agents window. These sessions run through the Agent Host .
Thank you so much to everyone who has shared valuable feedback. This release includes more improvements shaped directly by your feedback. We're continuing to improve performance and reduce latency based on the scenarios and setups you share. For example, reports of long waits before chat responses helped us reduce delays caused by MCP servers that don't finish loading their tools. We're also continuing to make our documentation clearer based on the feedback and questions you've shared.
Learn how to work with the Copilot harness , or explore the architecture and workflows in the agent host blog post . Please continue filing issues to let us know how the Copilot harness is working for you. Your feedback is a huge help and directly shapes the harness experience. Initial file-level working set support (Experimental) Setting: chat.editor.workingSet.enabled Open in VS Code Open in VS Code Insiders You gave us feedback that when using the Copilot harness, approving or rejecting agent edits in the editor was challenging.
As of this release, we are introducing initial file-level working set support to help you manage and review changes more effectively. Copilot harness sessions in the editor window now support file-level Keep in the experimental working set above the chat input. Enable chat.editor.workingSet.enabled Open in VS Code Open in VS Code Insiders to try it. Select Keep on a file, or in the heading for all files, to mark changes as reviewed and remove them from the working set.
The edits stay on disk, and files return if the agent changes them again. What's next: We plan to add file-level Undo to the working set and bring Keep and Undo back into the editor for individual changes. These are planned for later releases, landing in Insiders first, then Stable. Discard changes from more changesets in the Agents window The Changes view in the Agents window lets you see all the modifications made by the agent.
Until now, discarding pending changes was only available in the Uncommitted Changes changeset. In this release, the Branch Changes , Session Changes , and Last Turn Changes changesets also offer the possibility to discard changes. Select Discard Changes on a file in the Changes view or in the multi-file diff editor. What VS Code discards depends on the changeset: Branch Changes : restores the file to its version where the branch diverged from its base branch, and deletes files that the branch added.
Session Changes : reverts the session's edits to the file and keeps changes made outside the session, such as your own edits. Last Turn Changes : reverts only the latest turn's edits to the file and keeps all other changes to it. Compare model results (Preview) Setting : sessions.chat.compareAgents.enabled Open in VS Code Open in VS Code Insiders (Agents window only) Compare how different models and harnesses approach the same coding task.
Run attempts in parallel, review their results, and combine ideas into one solution. To get started, enable sessions.chat.compareAgents.enabled Open in VS Code Open in VS Code Insiders in the Agents window, then select Compare Models in the model picker. Choose the approaches to compare: Select two or more models to attempt your task independently. You can mix Copilot, Claude, and Codex harnesses and configure different reasoning levels.
Run the attempts: Enter one prompt and start all selected attempts together. Follow progress side by side: Each attempt runs in its own session, so you can compare its approach and open the worktree or changes at any time. Evaluate and combine the results: Optionally select a Judge model to evaluate the attempts and recommend a solution. Its scorecard shows time and token usage, with expandable rationale, validation evidence, and links to each attempt.
You can then select Synthesize to build on the recommended attempt with ideas from the others. Synthesis starts only when you request it. Tab shortcuts in an empty side pane When you closed every tab in the Agents window side pane, the editor area was left blank, and you had to find the Add Tab (+) menu to get back to your session's changes or files. The empty editor area now lists the tabs you can add, such as Changes , Files , Browser , and Search , each with its icon and keyboard shortcut.
Select an entry to open that tab. If you have a canvas extension installed, a Canvas entry lists the available canvases. When you switch to a session whose editor area is empty, VS Code shows this list instead of reopening the Changes and Files tabs automatically. Session Activity Bar (Experimental) Sessions : sessions.showSessionActivityBar Open in VS Code Open in VS Code Insiders , sessions.sessionActivityBar.showLayoutActions Open in VS Code Open in VS Code Insiders The Session Activity Bar brings a session's Changes , Files , Browser , and available canvases next to the side pane, keeping these editors and artifacts visually connected to where they open.
You can still open session artifacts from the pills at the top of the session. The Session Activity Bar is a slim vertical strip of icons at the right edge of the active chat. Select an icon to open that tab in the side pane. If the side pane is closed, it opens with that tab active. If the tab is already open, VS Code focuses it instead of opening a second copy. If you have a canvas extension installed, a Canvas entry opens a submenu of the available canvases.
You can drag the Session Activity Bar up or down by its grip to move it out of your way, and double-click the grip to reset its position. When you split the chat area, only the focused group shows the Activity Bar. To keep session-related layout actions together, right-click the Activity Bar and select Show Layout Actions . This moves the Toggle Side Panel and Toggle Panel actions from the title bar into the Activity Bar.
The Session Activity Bar is off by default in Stable. Select View > Appearance > Session Activity Bar to turn it on. To hide it again, right-click the Activity Bar and select Hide Session Activity Bar . You can also configure these options with sessions.showSessionActivityBar Open in
The rest of this page is on the live site.