GitHub Copilot: VS Code Retires the Local Harness in February 2027
GitHub announced that Visual Studio Code 1.146 deprecates the Local harness, with removal planned for February 2027. The built-in Copilot harness has been the default for new sessions since VS Code 1.143 and shares its runtime with Copilot CLI and the GitHub Copilot app. Users who still rely on the Local harness should start a new session with the Copilot session target.
Key Takeaways
- Local harness removal is scheduled for February 2027, after a three-month transition.
- The Copilot harness has been the default for new VS Code sessions since version 1.143.
- Sessions can continue between the editor and the Agents window because the Agent Host process stays running.
- The harness shares its runtime with Copilot CLI and the GitHub Copilot app, built on the Copilot SDK.
- New capabilities include Copilot Fusion, assisted permissions, connectors and canvases, with connectors and canvases in preview.
- Customizations are not auto-converted, so users should review compatibility before the cutoff.
Local harness deprecated
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. GitHub plans to remove it in February 2027. During the three-month transition it stays available where an organization's policy permits, but new features and improvements will focus on the Copilot harness.
The replacement, the Microsoft Copilot harness, is built into VS Code and has been the default for new sessions since VS Code 1.143. Choosing it does not move files to the cloud. Developers keep working in VS Code and running agent commands on their own machine.
Why switch to the Copilot harness
The Copilot harness is built on the Copilot SDK and shares its coding-agent runtime with Copilot CLI and the GitHub Copilot app. A session can continue between the editor and the Agents window in VS Code while the session's Agent Host process stays running, although editor-provided tools still need a connected editor.
It also unlocks several capabilities. Copilot Fusion can choose models and, on supported tiers, coordinate drafting and review. Assisted permissions reduce approval interruptions, and calls the risk assessment does not approve still come to the user for confirmation. Copilot connectors bring context from team services without configuring MCP servers (in preview), and canvases support task boards and interactive diagrams (in preview). Users who access models through GitHub Copilot keep their existing plan, including Copilot Free, though individual features and Fusion tiers depend on plan, settings, and organization policy.
What to do before February 2027
Anyone still on the Local harness should start a new session in VS Code and select Copilot under Session Target. Customizations should be reviewed for compatibility, because switching harnesses does not automatically convert every one. Administrators should review any vscode.temporaryDefaultToLocalHarness exception and verify workflows, permission controls, and sandbox configuration. That temporary setting is removed along with the Local harness. GitHub provides a Local harness transition guide, and workflow blockers can be reported as VS Code issues.