VS Code 1.146 gives the Local harness three months to live
Microsoft's November 11 release deprecates the Local harness — frozen from now, removed in February 2027 — and consolidates agent sessions on the Copilot harness, while adding an Inbox for sessions that need attention, model comparison with a judge, and skills delivered over MCP.

Photo: Pavel Danilyuk / Pexels (Pexels License).
Release notes usually add. The most consequential line in the notes for Visual Studio Code 1.146, released November 11, subtracts: the Local harness — the original runtime that powered agent sessions inside the world's most-used code editor — is deprecated. It stops evolving today, frozen where it stands, and in three months, in February 2027, it is removed. Everything Microsoft is building for agents in VS Code now flows through a single successor, the Copilot harness. The rest of the release — an Inbox for agent sessions, model comparison with a judge, skills arriving over MCP — is best read as furniture being arranged in the new runtime's house.
To see why a deprecation deserves the headline, you have to know what a harness is. It is the layer that actually runs an agent session: it decides which tools the model may call, what it must ask permission for, what runs in a sandbox and what runs free, and where the session lives while it works. For most users the harness is invisible — they chat with Copilot and code appears. For the enterprises now rolling agents out to thousands of developers, the harness is the product, because it is where control lives. VS Code has had two of them, and 1.146 is the release where Microsoft stops pretending both have a future.
Two harnesses, two philosophies
The Local harness is the first-generation design: sessions run the way the editor has always run things, close to the workspace, under the user's own authority. The Copilot harness, built on the Copilot SDK and the Agent Host, is the governed design. Sessions run in the background, reachable from the editor and from the dedicated Agents window whether or not you are looking at them; the harness enforces sandboxing and managed permission policies — the kind administrators set centrally — in ways the release notes state plainly the Local harness does not. That asymmetry is the whole argument. An agent that can edit files, run commands and open pull requests is, from a security team's chair, a new kind of employee; the Copilot harness is the one that comes with a manager. Microsoft made it the default for new sessions back in 1.143. Version 1.146 simply sets the date on which the alternative stops existing.
Sessions that live in the background
The Agent Host deserves a sentence of its own, because it changes where work happens. Under the Copilot harness, a session is not a panel you keep open; it is a process with an address. It keeps running in the background, it can be reopened from the editor or from the Agents window, and in 1.146 the host learns new territory: it now works in virtual repositories, canvases resume more gracefully behind permission prompts, and — in an experimental touch that says much about where this is heading — you can share this machine with a session through GitHub Environments or Dev Tunnels. The editor is quietly acquiring the properties of a workplace rather than a workbench: places where agents are assigned, supervised and handed resources, with the human arriving to review outcomes rather than to witness keystrokes. The Local harness, bound to the open workspace and the user's own session, was never going to be that place. Its deprecation is less a removal than an eviction notice served by architecture.
The three-month clock, and the exits closing
The deprecation is engineered to leave no comfortable halfway house. The Local harness is not merely marked legacy; it is frozen — the notes say feature work goes to the Copilot harness only. And the escape hatch is being removed with it: the enterprise setting vscode.temporaryDefaultToLocalHarness, introduced just four releases ago in 1.142 so organisations could pin their users to the old runtime while they evaluated the new one, is itself deprecated. That is a deliberate sequence — offer a temporary bridge, let the fleet cross, then dismantle the bridge on a published date. Microsoft ships an official transition guide for moving from the Local harness to the Copilot one, and for most individual users the honest summary is that nothing needs doing: new sessions have defaulted to the Copilot harness for three releases already. The users with homework are the ones who deliberately stayed — teams that pinned the Local harness for its behaviour, its permissions model or its predictability. Their three months are for rebuilding that control on the new harness's policy machinery, and the clock in the release notes is not a suggestion.
The Inbox: the editor admits what the job now is
If the deprecation is the release's strategy, the Inbox is its confession. Inbox mode — experimental, behind the sessions.list.inboxEnabled setting — gathers every agent session that needs something from you into a single list, grouped as Working, Ready to merge, On hold and Done. Sessions can be snoozed, dismissed or put on hold; with inline actions enabled, you can fix failing checks and answer review comments directly from the list, without opening the session at all. Consider what that interface assumes: that a developer now supervises several agents the way a manager supervises a team's queue — most of them working unattended, a few waiting on a human decision, one or two ready to land. The editor's centre of gravity is shifting from the file you are editing to the sessions you are conducting. The Inbox is simply the first screen in VS Code designed for the conductor rather than the player.
The rest of the release, in the new house
Around those two poles, 1.146 fills in the Copilot-harness feature set. Chat windows, in preview, let a conversation move into its own window with reorderable parts — editor, terminal, chat — that persist across restarts. Model comparison, also in preview, runs models against each other with a judge and a synthesizer, and Copilot Fusion can serve as attempt, judge or synthesizer; an agent can even launch and read comparisons itself. Skills over MCP, in preview under specification SEP-2640, lets an MCP server hand skills to the model automatically — with an approval prompt the first time a connection offers them — extending the editor's talents from the same protocol that already feeds it tools. And the /code command closes the loop with the terminal: from Copilot CLI 1.0.107 or later, /code carries a live session out of the command line and into the editor's Chat view with its history, model, effort, mode and permissions intact — listing, before it hands over, any CLI-only permissions that will not survive the trip.
What February means in practice
For a team still on the Local harness, the migration is mostly not about code. It is about translating expectations of control from one runtime to the other: the permissions you granted wholesale will be re-asked granularly, per domain, command and directory; the environment variables your sessions quietly inherited will be masked in the sandbox unless you say otherwise; the workflows that lived in a terminal will meet an editor that now lists, before a /code handoff, exactly which permissions do not transfer — a small dialog that tells you the two runtimes never spoke the same policy language. Three months is generous for an individual and merely adequate for a fleet with a compliance review in the middle, which is presumably why Microsoft published the date in November rather than discovering it in January. The frozen harness will not get worse at its job between now and February. It will simply be standing still while everything around it — the features, the policies, the protocol extensions — moves into the other house.
The smaller print points the same direction: extensions can now be installed and managed from the Agents window; permission prompts have gone granular, asking per domain, command or directory instead of for the whole session; the sandbox masks environment variables and the input box now says “(sandbox enabled)” out loud; Copilot sessions work behind the PAC and Kerberos proxies of real corporate networks. None of these is a headline. All of them are governance — the unglamorous machinery that decides whether an enterprise lets agents run at all. Read together with the deprecation, the release has a single thesis: there will be one runtime for agents in VS Code, it will be the governed one, and February is when the alternative becomes a memory. Teams still on the Local harness have their assignment, and it is not any of the shiny features. It is the migration.
𝐆𝐄𝐓 𝐅𝐑𝐄𝐄 𝐅𝐔𝐋𝐋 𝐌𝐀𝐆𝐀𝐙𝐈𝐍𝐄 𝐀𝐓 thebuyerspulse.com
Sources
- Microsoft (Nov 11, 2026), “Visual Studio Code 1.146” release notes (code.visualstudio.com/updates/v1_146): the Local harness deprecation and three-month removal window, the feature freeze, the Copilot harness on the Copilot SDK and Agent Host as default since 1.143, the removal of vscode.temporaryDefaultToLocalHarness, Inbox mode and inline actions, chat windows, model comparison and Copilot Fusion, skills over MCP (SEP-2640), the /code handoff from Copilot CLI 1.0.107+, granular permission prompts and sandbox environment-variable masking.
- AI/TLDR (Nov 11, 2026), release summary of Visual Studio Code 1.146: corroboration of the stable release date and the headline changes.
- Photo: Pavel Danilyuk / Pexels — hands typing code on a laptop in low light, editor on screen (Pexels License).