Skip to content
Brief Innovation & Growth ·

VS Code will retire its Local harness for Copilot agents in February 2027

GitHub says admin exceptions will not keep the old runtime alive, and sandboxing is not switched on by the move.

In brief
  • GitHub said VS Code 1.146 deprecates the Local harness, and it will be removed in February 2027. The Copilot harness replaces it.
  • Sandbox and permission controls are separate settings. Choosing the new harness does not turn them on.

GitHub said on 16 November that VS Code 1.146 begins retiring the Local harness, with removal set for February 2027. A harness is the go-between that hands the AI model its context and tools during Copilot agent sessions in the editor. New sessions have used its successor, the Copilot harness, by default since version 1.143.

The new harness runs on the same agent engine that powers Copilot CLI and the Copilot app. A session can therefore move between the editor and the Agents window while its Agent Host process stays alive. Work still happens on the user's machine, not in the cloud. Admins can enforce permission and sandbox limits on the new harness that the old one cannot. Those limits are separate settings, so choosing the new harness alone gives no sandbox. Not every customization converts automatically. GitHub gave no figure for how many people still use the Local harness.

The runtime behind a coding agent is a part that changes on the vendor's schedule, and its controls do not carry over by themselves. The temporary enterprise setting vscode.temporaryDefaultToLocalHarness will be removed too, so an exception will not save the old harness. Leaders can ask three things: who holds the exception, which workflows rely on the Local harness, and who confirms the sandbox is set up?

A WebPulse Brief: a short report of an important event, written by the WebPulse Newsroom with AI assistance and checked against the reporting below. When there is more to explain, we follow up with a full story. How we use AI.

Reporting: GitHub.