Skip to content

VS Code retires the Local harness by February 2027

VS Code 1.146 deprecates the older Copilot agent runtime, with removal set for February 2027 and the Microsoft Copilot harness already the default.

Draftship Editorial3 min read

VS Code moves agent sessions onto the Copilot harness

On 16 November 2026, GitHub's changelog set out the VS Code Local harness retirement: Visual Studio Code 1.146 deprecates the Local harness, described in the post as the older software that coordinates the model, context and tools behind GitHub Copilot agent sessions in the editor, and the component will be removed in February 2027. The replacement is the Microsoft Copilot harness, which is built into VS Code and has been the default for new sessions since version 1.143. The post on the GitHub Changelog treats this as a runtime swap, not a move of your work off your machine.

What the source confirms

The deprecation lands in 1.146 and removal in February 2027. Choosing the Copilot harness does not move files to the cloud, and agent commands still run on your machine. The Local harness stays available during a three-month transition, but only where an organization's policy permits it, and new features and improvements will go to the Copilot harness instead.

The Copilot harness is built on the Copilot SDK and shares its coding-agent runtime with Copilot CLI and the GitHub Copilot app. Sessions can continue between the editor and the Agents window in VS Code while the session's Agent Host process keeps running. Tools supplied by the editor still need a connected editor. Existing Copilot plans, including Copilot Free, remain usable, though individual features and Fusion tiers depend on plan, settings and organization policy.

How the two harnesses differ in practice

The post lists four capabilities that come with the Copilot harness. Copilot Fusion can pick models and, on supported tiers, coordinate drafting and review. Assisted permissions cut down approval interruptions, with calls that the risk assessment does not approve still routed to you for confirmation. Copilot connectors, in preview, pull context from a team's services without you configuring MCP servers. Canvases, also in preview, cover planning work on task boards and exploring interactive diagrams.

There is also an administrative difference. With the Copilot harness, administrators can enforce managed runtime permissions and sandbox restrictions that the Local harness cannot enforce. The post is explicit that these controls are configured separately and that selecting the Copilot harness does not turn sandboxing on.

What builders need to do

If you still use the Local harness, the instruction is to start a new session in VS Code and pick Copilot under Session Target. Customizations should be reviewed for compatibility before February 2027, because switching harnesses does not automatically convert every customization. Administrators are asked to review any vscode.temporaryDefaultToLocalHarness exception and check required workflows, permission controls and sandbox configuration against the Copilot harness. That temporary enterprise-managed setting disappears along with the Local harness, so leaving it configured will not keep the old runtime alive.

Limits and open questions

The announcement does not say which customizations fail to carry over, or how much of that the linked Local harness transition guide covers. It does not say whether connectors and canvases will leave preview, or what the separate sandbox and permission configuration involves beyond the fact that it exists. It also leaves open what teams should do when organization policy blocks the Copilot harness before the February 2027 removal, other than reporting a VS Code issue if a workflow is blocked.

What it means for building apps with AI

For anyone who leans on an editor agent, the harness is becoming part of the platform decision rather than an implementation detail: the same runtime now sits under the editor, the CLI and the Copilot app, and admin controls are attached to it. Nothing in the post describes effects on tools outside VS Code. Draftship, which publishes this news section, is a separate AI app builder where you describe an app in plain language and it writes, builds and hosts the code, with a built-in database, sign-in and hosting; paid plans add a choice of AI model and GitHub push. If you move code between an editor agent and a hosted project, the GitHub and Vercel page covers how that connection works on Draftship's side.

Primary sources

This article was drafted with AI assistance from the primary sources listed below and checked automatically against them. An editor hasn't reviewed it yet.