Visual Studio Code 1.145
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. Visual Studio Code 1.145 Release date: November 4, 2026 Stable Update 1.145.1 : The update addresses these issues . Update 1.145.2 : The update addresses these issues . Update 1.145.3 : The update addresses these security issues . Downloads for 1.145.3 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Release highlights This week, your remote agent sessions feel a bit more local.
Preview apps and use canvases right in VS Code, fine-tune automation schedules with cron, and turn down the noise in chat. And when you need a break, Blobby is ready to play. Remote agents : Preview apps and use interactive canvases from remote agent sessions without leaving the Agents window. Automations : Run recurring agent tasks on custom schedules beyond the built-in presets with cron. Agent verbosity : Keep chats concise or see the full details of the agent's reasoning and tool calls, your choice.
File exclusions : Exclude folders while keeping the files you need visible and searchable. Fun : Take a short break with a platform-jumping game starring Blobby, the VS Code pet. Already installed? Use Check for Updates in VS Code. For upcoming features, use the Insiders build . Remote agents Browse over remote agent host connections (Preview) Setting : workbench.browser.enableRemoteProxy Open in VS Code Open in VS Code Insiders When an agent session runs on a remote agent host , the integrated browser in the Agents window now loads pages through that host, as it already does in remote workspaces .
When the agent starts a dev server on the remote machine, you can open it right in the Agents window to preview the app, validate the agent's changes, and give it feedback, as you would in a local session. Enable workbench.browser.enableRemoteProxy Open in VS Code Open in VS Code Insiders to try it out, and file any issues you encounter in the VS Code repository . Remote canvases (Preview) Settings : workbench.browser.enableRemoteProxy Open in VS Code Open in VS Code Insiders , chat.canvases.enabled Open in VS Code Open in VS Code Insiders Thanks to the remote agent host connections support, you can now also use canvases that are hosted on a remote agent host.
Enable chat.canvases.enabled Open in VS Code Open in VS Code Insiders and workbench.browser.enableRemoteProxy Open in VS Code Open in VS Code Insiders to try it out, and file any issues you encounter in the VS Code repository . Agents Mix and match agent harnesses in one session (Preview) Setting : chat.agentHost.multipleChatProviders.enabled Open in VS Code Open in VS Code Insiders Nested sessions let you keep related conversations together within a single main chat session.
Previously, every nested session inherited its parent session's harness. If you wanted a second opinion from another agent, you had to start a separate session and lose that grouping. In this release, nested sessions can use different harnesses than their parent session. For example, ask Claude to review the plan that a Copilot chat wrote, or give Codex the same task, side by side in the same session. When you create a new nested session, use the harness picker to switch to a different harness.
Each chat has its own model, agent, and permission levels, based on its harness. Changing them in one chat doesn't affect the others. When you move a chat, it keeps its history and continues with its selected harness. When you fork a nested session, it continues with the same configuration. A chat that uses a different harness than its session names its harness when you hover over its chat tab or its row in the sessions list.
Enable chat.agentHost.multipleChatProviders.enabled Open in VS Code Open in VS Code Insiders to get started. Let us know what you think by filing an issue . Cron schedules and custom agents for local automations Instead of manually running agent tasks one by one, you can use automations to schedule and run them automatically, either on demand or on a set schedule. This release gives you more flexibility for local automations and keeps the Automations view focused on active work: Use cron schedules: Select Cron to enter a five-field cron expression when the other schedule presets aren't precise enough.
The dialog validates the expression and describes the resulting schedule. Cron schedules are not available for cloud automations. Use workspace custom agents: Choose a custom agent from the selected workspace when you create or edit a local automation. Focus on active automations: Disabled automations appear in a collapsed Disabled automations section, so they don't obscure run history and active automations. Learn more about creating and managing agent automations .
Pin canvases to sidebar (Experimental) Setting : chat.canvases.enabled Open in VS Code Open in VS Code Insiders To make it easier to access frequently used canvases, you can now pin a canvas to appear in the left sidebar. To pin a canvas, open it and select the Add to Sidebar button above the canvas. Pinned canvases remain accessible in the sidebar even when you navigate away from them. Copilot harness The Copilot harness continues to be 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 .
To help you adopt the Copilot harness with your existing workflows, we've added a Local-to-Copilot harness transition guide . It covers customization compatibility, session continuity, and organization rollout and verification. Thank you for the feedback that continues to shape these improvements. Please continue filing issues about your experience, especially if a workflow or integration prevents your organization from moving off the Local harness.
Learn how to work with the Copilot harness , or explore the architecture and workflows in the agent host blog post . Working set improvements (Experimental) Setting : chat.editor.workingSet.enabled Open in VS Code Open in VS Code Insiders Last release, we introduced the working set for Copilot harness sessions, letting you review pending agent edits. You can keep or undo changes, as you could do with the Local harness.
We are further improving the working set experience in Copilot harness sessions: Files in WSL, Dev Containers, and SSH workspaces open from the working set on the correct host. When several tool calls edit the same file in parallel, the working set tracks those edits and the editor's inline review controls remain available after editing finishes. The working set functionality remains enabled by default in the editor window.
Learn more about reviewing agent edits with the working set , including which edits it tracks. Improved guidance when required sandboxing is unavailable Agent sandboxing limits what terminal commands can access, like the file system and network resources. Your organization can require it with managed settings that disallow bypassing the sandbox. If your organization requires sandboxing but your machine can't run it, the warning banner explains why terminal commands are blocked and how to resolve the problem.
It shows the specific cause, such as a missing dependency, and links to troubleshooting steps. If your account and organization support cloud sessions (Experimental) , consider running agent tools in the cloud instead of on your machine. Chat Choose agent verbosity (Experimental) Setting : chat.persistentProgressVerbosity Open in VS Code Open in VS Code Insiders Keep long chats readable, or follow the agent's
The rest of this page is on the live site.