Skip to main content
Post

VS Code retires the Local harness in February 2027

VS Code deprecated the Local harness in version 1.146 and will remove it in February 2027. The Local harness is the older software that coordinates the model, context, and tools for GitHub Copilot agent sessions in the editor. Its replacement, the Copilot harness, has been the default for new sessions since VS Code 1.143.

Nothing about where your work runs changes. You keep working in VS Code, agent commands still run on your machine, and choosing the Copilot harness doesn't move your files to the cloud. Until removal, the Local harness stays available where your organization's policy allows it, but new features will go to the Copilot harness.

If you still use the Local harness, start a new session and pick Copilot under Session Target. The move guide covers the rest. Switching doesn't convert every customization, so check prompt files, hooks, and MCP servers first. Hooks have no automatic conversion. To keep an existing Local conversation, open it and change its Session Target to Copilot, which carries the history and context over.

The Copilot harness is built on the Copilot SDK and shares its runtime with Copilot CLI and the GitHub Copilot app. You can continue the same session between the editor and the Agents window while its Agent Host process stays running. It adds Copilot Fusion model selection, assisted permissions that cut routine approval prompts, and preview features like Copilot connectors and canvases. Fusion tiers and individual features depend on your plan, settings, and organization policy.

Administrators can enforce managed permissions and sandbox restrictions that the Local harness can't. Sandboxing has to be configured separately, and the temporary vscode.temporaryDefaultToLocalHarness setting will be removed too.

Loading replies