VS Code to Remove the Legacy Local Harness for Copilot Agents in February 2027
VS Code 1.146 has deprecated the Local harness, the legacy "scaffolding" that connects the model, context, and tools in Copilot agent sessions. It will be removed in February 2027, while the Copilot harness has been the default since version 1.143. Files stay on your machine, and agent commands still run locally. Customizations are not converted automatically during the switch, so it's better to check them in advance.
AI-processed from GitHub Changelog; edited by Hamidun News
If you use GitHub Copilot's agent mode in VS Code, a harness runs under the hood. It's the program that decides which model to call, what context to show it, and which tools to give it. In VS Code 1.146, the older option, the Local harness, has been deprecated. It will be removed in February 2027. There is enough time, but teams with configured policies and customizations may run into surprises, so it's better to check everything in advance.
What Exactly Is Changing
The replacement already exists and works: the Copilot harness. It's built into VS Code and has been used by default in new sessions since version 1.143. This means many developers are already on it without thinking about it. Those who remain on the Local harness only need to open a new session and select the Copilot harness.
GitHub stresses separately that choosing the new harness does not move files to the cloud. You keep working in the editor, and agent commands run on your machine, as before.
The transition period is three months. The Local harness remains available where organization policy allows it. However, all new features and improvements will now be built for the Copilot harness. The older option is effectively being frozen.
What Users Get
The main technical difference is the shared runtime. The Copilot harness uses the same coding agent engine as Copilot CLI and the GitHub Copilot app. As a result, a session can be continued between the editor and the Agents window in VS Code, because the Agent Host process that hosts the session stays running. One caveat: tools provided by the editor itself still require a connected editor.
GitHub names several specific capabilities:
- model selection and, on supported plans, coordination of drafting and review within a single task;
- fewer confirmation prompts: automatic risk assessment lets safe calls through, while questionable ones still come to you for approval;
- connectors to team services without manual MCP server setup (currently in preview);
- work planning on task boards and interactive diagrams.
No separate payment is needed for the switch: if the models are available through GitHub Copilot, your current plan applies, including Copilot Free. However, the set of individual features and Fusion tiers depends on your plan, settings, and organization policy.
What Administrators and Teams Should Do
For enterprise customers, security matters most. With the Copilot harness, administrators can set managed execution permissions and sandbox restrictions, which the Local harness cannot enforce. But there is a catch: this must be configured separately. Simply selecting the new harness does not enable the sandbox, so "secure by default" does not apply here.
A practical checklist looks like this:
- Set up a test session on the Copilot harness and run your typical workflows through it.
- Check customizations for compatibility. GitHub warns that they are not converted automatically when the harness changes.
- Review permissions and sandbox settings: the restrictions you need must be set explicitly.
- Look in your configuration for the vscode.temporaryDefaultToLocalHarness exception, if you have one.
The last item is especially tricky. It is a temporary setting for enterprise management, and it will disappear along with the Local harness. Keeping the exception will not extend the life of the old option: after removal, it will simply stop working. If you relied on it to keep your team on the old harness, it's time to draw up a migration plan.
Honest Limitations
The announcement does not include a full list of what will not carry over when the harness changes: GitHub refers to a separate migration guide and asks users to report any scenario that blocks migration. Some capabilities, such as connectors, are still in preview, so it's too early to rely on them for critical processes. The availability of individual features depends on your plan and organization policies.
The bottom line is simple: until February 2027 there are three months to test your scenarios on the new harness. Those already on it need do nothing. Everyone else should start with a new session, a check of customizations, and an audit of policies. It's better to spend an evening on this now than to deal with broken agent sessions after the removal.
- Nov 21, 2026Оператор АЭС Constellation не боится демократов после распродажи ИИ-акций на $2,5 трлн
- Nov 21, 2026Islo Raises $15M from Insight Partners for AI-Agent 'Software Factory'
- Nov 21, 2026AI agents added 30% more code for engineers, but review of changes took 49% longer
- Nov 21, 2026Applied Digital Asks Oracle and Meta for Billions in Power Guarantees
Key Questions Answered
What Exactly Is Changing?
The replacement already exists and works: the Copilot harness. It's built into VS Code and has been used by default in new sessions since version 1.143. This means many developers are already on it without thinking about it. Those who remain on the Local harness only need to open a new session and select the Copilot harness. GitHub stresses separately that choosing the new harness does not move files to the cloud. You keep working in the editor, and agent commands run on your machine, as before.
What Users Get?
The main technical difference is the shared runtime. The Copilot harness uses the same coding agent engine as Copilot CLI and the GitHub Copilot app. As a result, a session can be continued between the editor and the Agents window in VS Code, because the Agent Host process that hosts the session stays running. One caveat: tools provided by the editor itself still require a connected editor.
What Administrators and Teams Should Do?
For enterprise customers, security matters most. With the Copilot harness, administrators can set managed execution permissions and sandbox restrictions, which the Local harness cannot enforce. But there is a catch: this must be configured separately. Simply selecting the new harness does not enable the sandbox, so "secure by default" does not apply here. A practical checklist looks like this: Set up a test session on the Copilot harness and run your typical workflows through it.
Build & Ship Production AI Agents Without Boilerplate Code
Start your free 72-hour trial at Hamidun Academy (academy.hamidun.com) — interactive lessons on Claude Code & Cursor, live Tech Radar, and production agent templates.
The AI world, distilled — once a week
Seven stories that actually mattered, hand-picked. No noise, no reposts, no press releases.
Done! Check your inbox for a confirmation.