Skip to main content

VS Code 1.144

Release Date: October 28, 2026

Verdict up front: VS Code 1.144 is the most "hands off" release Microsoft has shipped all year, and that is both its strength and the thing to think about before you click update. The October 2026 build, released on October 28, pushes agents out of the editor tab and into their own persistent sessions, and it adds a multi-model layer on top of Copilot. If you live in the terminal-plus-editor loop, you will feel the difference within an hour. If you keep AI features disabled, this release is mostly plumbing.

Agents That Outlive the Editor Window

The headline change is continuity. In previous releases, closing a window meant ending whatever the agent was doing inside it. In 1.144, agent work no longer depends on a single editor staying open. Local agent sessions persist, and cloud sessions let the same work continue in a remote environment. Microsoft frames this as agents that follow you across local and remote setups rather than being tied to one machine.

For me that changed the shape of a workday. I kicked off a dependency refactor, closed the laptop to take a call, and came back to a session that had kept going. That is a small sentence to write and a large change in how the tool behaves. It also means the mental model shifts from "my editor is running this" to "a session is running this and my editor is a window into it."

Copilot Fusion: Several Models, One Request

Copilot Fusion is the second big piece. Instead of pinning every request to a single model, it orchestrates across multiple models. The practical effect is that routine edits and harder reasoning tasks can be routed differently without you choosing a model in a dropdown for every prompt.

I tested it on a mixed bag: renaming a component across a workspace, writing a test for a parsing function, and asking for a review of a diff. The routing was invisible, which is the point. Whether that is better than picking your own model depends on how much you care about knowing exactly which system answered. Debugging a strange suggestion is easier when you know the model, and Fusion deliberately blurs that line.

Image Generation and Computer Use

Two smaller but notable additions round out the release. Image generation is now available inside the editor, which is useful for quick mockups, placeholder assets, and diagrams that used to require a browser tab. Computer use is the more exotic one: the agent can operate a computer environment rather than only editing files. That opens up flows like driving a browser to reproduce a bug, at the cost of a much wider surface for mistakes.

Treat computer use the way you would treat giving a contractor SSH access. It is powerful, it is genuinely useful for reproduction steps, and it deserves a workspace where nothing irreplaceable lives.

What I Changed in My Setup

Three settings-level adjustments made 1.144 feel less noisy:

  • Session visibility: I keep the agent session list pinned so I can see what is still running after I close a tab. Orphaned sessions are the new orphaned processes.
  • AI feature gating: the release notes ship with a settings guide. I disabled image generation in repositories where generated assets would end up in a commit by accident.
  • Workspace trust: persistent sessions make trust decisions more consequential. I now open unfamiliar clones in a restricted window before letting an agent touch them.

The Caveats

Most of 1.144 assumes a GitHub Copilot plan. The agent, Fusion, and the image tools are not free features that happen to be off by default; they are the paid surface of the product. Cloud sessions also mean source context leaves your machine, which is a policy question for teams before it is a technical one.

The other caveat is cadence. With monthly releases, 1.144 will be superseded within weeks, so pinning an extension set to an exact build is still the sane approach for teams that need stability. I would not reorganize a workflow around a feature that may be renamed by 1.146.

How to Upgrade

Use Help > Check for Updates on Windows and Linux, or Code > Check for Updates on macOS. Package manager installs, including Homebrew and the Debian and RPM repositories, pick up the new build on their usual schedule. After restarting, open the agent session view once and confirm that your previous local sessions are listed where you expect them.

If you run VS Code in a regulated environment, read the release notes for 1.144 before updating, specifically the sections on sessions and cloud environments. The editor itself is the same editor. What surrounds it is not.

Other Versions

We use cookies for ads and analytics.