Skip to content
worth noting AI agents

VS Code is phasing out the Local harness for GitHub Copilot; the Copilot harness is the replacement

clearly official source

VS Code 1.146 has marked the Local harness for the GitHub Copilot agent as deprecated; it will be removed in February 2027 and replaced by the built-in Copilot harness, which has been the default since version 1.143.

Visual Studio Code version 1.146 has marked the Local harness, the older software that coordinates the model, context, and tools for GitHub Copilot agentic sessions in the editor, as deprecated. The Local harness will be removed in February 2027. Its replacement is the Copilot harness from Microsoft, which is built into VS Code and has been the default for new sessions since VS Code 1.143.

According to GitHub, work remains local - choosing the Copilot harness does not move the user's files to the cloud. During the three-month transition period, the Local harness remains available wherever organizational policy allows it, but new features and improvements will focus solely on the Copilot harness. It is built on the Copilot SDK and shares a runtime with Copilot CLI and the GitHub Copilot app, so users can continue the same session between the editor and the Agents window in VS Code as long as the Agent Host process is running.

According to the source, users keep their existing plan, including Copilot Free, but specific features and Fusion tiers depend on the plan, settings, and organizational policy. With the Copilot harness, administrators can enforce runtime permission management and sandbox restrictions that the Local harness did not allow - however, these controls need to be configured separately; selecting the Copilot harness does not automatically enable sandboxing.

Local harness users are advised to start a new session and select Copilot under Session Target, check compatibility of their custom modifications, and report any issues as a VS Code issue. Administrators should review the vscode.temporaryDefaultToLocalHarness exception before February 2027, since this temporary setting will be removed together with the Local harness.

What changed

Why it matters

This concerns anyone who uses GitHub Copilot's agentic features in VS Code with custom settings or workflows built on the Local harness - these will not be migrated automatically when switching to the Copilot harness and need to be verified in advance. For companies and their administrators, it also represents a change in permission enforcement and sandbox restrictions, since the existing temporary exception for keeping the Local harness will disappear along with it.

Two audiences, two different impacts

What this means

01

For individuals

Developers using the Local harness in VS Code must switch to the Copilot harness by February 2027 and verify in advance that their custom settings and workflows work, since they will not be migrated automatically.

What to do In a new session in VS Code, select Copilot under Session Target and check compatibility of your custom settings before February 2027.
More practical updates →
02

For a business

By February 2027, administrators must verify permission enforcement and sandbox restrictions for the Copilot harness, because the setting allowing a temporary stay on the Local harness will be removed along with it.

Development
What to decide Verify the vscode.temporaryDefaultToLocalHarness setting and the required permissions/sandbox rules for the Copilot harness before February 2027.
More business impacts →
Copilot harness GitHub Copilot Local harness Microsoft VS Code

Check the original

Event sources

clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.

1
GitHub Copilot Changelog primary source · first detected VS Code retires the Local harness in February 2027