Home / Blog / VS Code retires the Local harness in February 2027
Tech News

VS Code retires the Local harness in February 2027

Visual Studio Code 1.146 deprecates the Local harness for GitHub Copilot agent sessions and will remove it in February 2027; the Copilot harness is the default.

In short

Copilot users still on the Local harness · VS Code 1.146; removal February 2027 · Three months, where org policy permits · Select Copilot under Session Target

By Dillip Chowdary • Nov 17, 2026 • Source: GitHub Changelog

VS Code retires the Local harness in February 2027
Image: GitHub Changelog

At a glance

Who it is for
Copilot users still on the Local harness
The number
VS Code 1.146; removal February 2027
Available
Three months, where org policy permits
What to do
Select Copilot under Session Target
Default since
New sessions since VS Code 1.143
Admin setting
vscode.temporaryDefaultToLocalHarness

Visual Studio Code 1.146 deprecates the Local harness, the older software that coordinates the model, context, and tools for GitHub Copilot agent sessions in the editor, and GitHub Changelog's report sets removal for February 2027, with the Microsoft Copilot harness as its replacement.

Developers and administrators who still use the Local harness can keep working in VS Code and running agent commands on their machine. Before February 2027 they start a new session, select Copilot under Session Target, and review customizations, while administrators check any vscode.temporaryDefaultToLocalHarness exception.

01Local harness deprecation in 1.146

Visual Studio Code 1.146 deprecates the Local harness, the older software that coordinates the model, context, and tools for GitHub Copilot agent sessions in the editor. The Local harness will be removed in February 2027. Version 1.146 is the deprecation release, and February 2027 is the removal month for that older coordinator.

The Microsoft Copilot harness is the replacement, and it is built into VS Code. It has been the default for new sessions since VS Code 1.143. That default was already in place before the February 2027 removal of the Local harness.

02Default since Visual Studio Code 1.143

The Microsoft Copilot harness has been the default for new sessions since VS Code 1.143. Developers can keep working in VS Code and running agent commands on their machine. Choosing the Copilot harness does not move files to the cloud.

During the three-month transition, the Local harness remains available where the organization's policy permits continued use. New features and improvements will focus on the Copilot harness throughout that three-month transition. The removal month for the Local harness is still February 2027.

03Copilot SDK shared coding runtime

The Copilot harness is built on the Copilot SDK and shares its coding-agent runtime with Copilot CLI and the GitHub Copilot app. The same session can continue between the editor and the Agents window in VS Code. The session's Agent Host process stays running while that session continues.

Editor-provided tools still require a connected editor inside VS Code for those sessions. That requirement stands while the session's Agent Host process stays running and while the runtime stays the one shared with Copilot CLI and the GitHub Copilot app.

Developers who access models through GitHub Copilot can continue to use their existing plan, including Copilot Free. Individual features and Fusion tiers depend on the plan, the settings, and organization policy. Those limits apply to features and to Fusion tiers alike.

Advertisement

Tech Pulse Daily

Get tomorrow's pulse first

Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.

04Fusion connectors and sandbox controls

With the Copilot harness, Copilot Fusion can choose models and, on supported tiers, coordinate drafting and review for the task. Assisted permissions reduce approval interruptions. Calls that are not approved by the risk assessment still come to the developer for confirmation.

Copilot connectors bring context from the team's services without the developer configuring MCP servers for that context. Connectors are in preview. On the same harness, developers can plan work on task boards and explore interactive diagrams with canvases, which are in preview.

Administrators using the Copilot harness can enforce managed runtime permissions and sandbox restrictions that the Local harness cannot enforce. Those permissions and the sandbox restrictions are configured separately from the choice of harness. Selecting the Copilot harness does not enable sandboxing.

ItemLocal harnessMicrosoft Copilot harness
Version statusDeprecated in Visual Studio Code 1.146Default for new sessions since Visual Studio Code 1.143
RemovalFebruary 2027Built into VS Code; new features and improvements focus here
Managed runtime permissionsCannot enforceAdministrators can enforce
Sandbox restrictionsCannot enforceAdministrators can enforce; selecting the harness does not enable sandboxing
Coding-agent runtimeCoordinates the model, context, and toolsCopilot SDK runtime shared with Copilot CLI and the GitHub Copilot app

05Session target and admin exception

Developers who still use the Local harness start a new session in VS Code and select Copilot under Session Target. Customizations need a compatibility review before February 2027. Switching harnesses does not automatically convert every customization, so the review is part of the move.

  1. Start a new session in VS Code if the Local harness is still in use.
  2. Select Copilot under Session Target so the session uses the Microsoft Copilot harness.
  3. Review customizations for compatibility before February 2027, because the switch does not convert every customization.

Administrators review any vscode.temporaryDefaultToLocalHarness exception and verify required workflows, permission controls, and sandbox configuration with the Copilot harness before February 2027. The temporary enterprise-managed setting will be removed along with the Local harness. Keeping the exception configured will not keep the Local harness available.

  1. Review the exception vscode.temporaryDefaultToLocalHarness where it is still configured.
  2. Verify workflows and the required permission controls and sandbox configuration on the Copilot harness before February 2027.
  3. Removal includes the exception The temporary enterprise-managed setting is removed with the Local harness, so keeping the exception configured will not keep the Local harness available.
Command
vscode.temporaryDefaultToLocalHarness

Note: During the three-month transition the Local harness remains available only where organization policy permits, and both that harness and the temporary enterprise-managed setting are removed in February 2027. Selecting the Copilot harness does not enable sandboxing, so sandbox restrictions are configured separately. Follow the Local harness transition guide, and report a VS Code issue if a workflow blocks the move.

Frequently asked questions

When will VS Code remove the Local harness?

Visual Studio Code 1.146 deprecates the Local harness, and the harness will be removed in February 2027. During the three-month transition it remains available where an organization's policy permits.

What replaces the Local harness?

The Microsoft Copilot harness replaces it. The harness is built into VS Code and has been the default for new sessions since VS Code 1.143. Choosing the Copilot harness does not move files to the cloud.

Do files move to the cloud with the Copilot harness?

Choosing the Copilot harness does not move files to the cloud. Developers can keep working in VS Code and running agent commands on their machine.

How do I leave the Local harness in VS Code?

Start a new session in VS Code and select Copilot under Session Target. Review customizations for compatibility before February 2027. Switching harnesses does not automatically convert every customization.

Will vscode.temporaryDefaultToLocalHarness keep the Local harness?

Administrators should review that exception and verify workflows, permission controls, and sandbox configuration before February 2027. The temporary enterprise-managed setting is removed with the Local harness. Leaving the exception configured will not keep the Local harness available.

Sources

Dillip Chowdary

Author

Dillip Chowdary

Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.

Related on Tech Bytes

Advertisement

5-min tech signal

Weekday briefing for engineers who skip the noise.

No spam · Unsubscribe anytime

Advertisement

✈️ CareerPilot

Your AI job-search copilot

Match your resume against live Ashby, Greenhouse & Lever openings — fit scores, job-specific resume optimization and email alerts.

Find matching jobs →

Free Tools

Browse all tools →