# GitHub — VS Code retires the Local harness in February 2027

- Company: GitHub (github.com)
- Announced: 2026-11-16T19:22:56+00:00
- Category: deprecation
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://github.blog/changelog/2026-11-16-vs-code-retires-the-local-harness-in-february-2027
- Record: https://forck.live/items/37015-vs-code-retires-the-local-harness-in-february-2027
- Subject: Copilot

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 will remove it in February 2027. Its replacement, the Microsoft Copilot 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, and users can keep working in VS Code and running agent commands on their own machine. During the three-month transition the Local harness remains available where an organization's policy permits, but new features and improvements will focus on the Copilot harness. Built on the Copilot SDK, the Copilot harness shares its coding-agent runtime with Copilot CLI and the GitHub Copilot app, and a session can continue between the editor and the Agents window while the session's Agent Host process stays running. Administrators can enforce managed runtime permissions and sandbox restrictions that the Local harness cannot enforce, though selecting the Copilot harness does not enable sandboxing. Users who still rely on the Local harness should start a new session, select Copilot under Session Target, and review customizations for compatibility, since switching harnesses does not automatically convert every customization.

## Evidence

Verbatim from https://github.blog/changelog/2026-11-16-vs-code-retires-the-local-harness-in-february-2027:

> 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.
> 
> Its replacement, the Microsoft Copilot harness , is built into VS Code and has been the default for new sessions since VS Code 1.143. You can keep working in VS Code and running agent commands on your machine. Choosing the Copilot harness doesn’t move your files to the cloud.
> 
> During the three-month transition, the Local harness remains available where your organization’s policy permits. However, new features and improvements will focus on the Copilot harness.
> 
> Built on the Copilot SDK , the Copilot harness shares its coding-agent runtime with Copilot CLI and the GitHub Copilot app. You can continue the same session between the editor and the Agents window in VS Code while the session’s Agent Host process stays running. Editor-provided tools still require a connected editor.
> 
> With the Copilot harness, you can:
> 
> Let Copilot Fusion choose models and, on supported tiers, coordinate drafting and review for your task.

---

Record: https://forck.live/items/37015-vs-code-retires-the-local-harness-in-february-2027
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
