On 16 November 2026 GitHub announced that VS Code will retire the Local harness in February 2027, with a three-month transition period. VS Code 1.146 marks it as deprecated.
What GitHub says
- What it is. The Local harness is the older layer that coordinates the model, context and tools for Copilot agent sessions inside the editor.
- What replaces it. The Copilot harness, which has been the default for new sessions since VS Code 1.143. It shares its runtime with Copilot CLI and the GitHub Copilot app, and choosing it does not move your files to the cloud.
- During the transition. The Local harness stays available only where an organisation’s policy permits it. New features will go to the Copilot harness.
- Customisations. GitHub warns that switching does not automatically convert every customisation, so they need reviewing before February.
- Admins. The
vscode.temporaryDefaultToLocalHarnessexception will be removed with the Local harness, so keeping it will not keep the old harness alive.
Why a non-developer should care
If your product team or agency uses AI coding agents in VS Code, the tooling underneath them is changing on a fixed date. Custom instructions, permission rules and sandbox settings that work today may behave differently on the new harness. It is a small migration, but it is exactly the kind that breaks quietly if nobody owns it.
So what
Ask whoever builds your product whether they use Copilot agent sessions in VS Code, and who is responsible for checking their setup before February 2027. A well-run AI-assisted team treats tooling changes like this as routine maintenance, not a surprise. Our AI-assisted development service builds that discipline in. To talk it through, start a project.