AI coding · VS Code · Original analysis

VS Code will remove Copilot’s Local harness in February 2027—local files do not automatically move to the cloud

The replacement Copilot harness remains capable of local agent commands, but settings and customizations do not all migrate automatically.

GitHub wordmark above Local harness inventory, Copilot harness migration and permission validation panels in an illustrative VS Code transition
GitHub wordmark with Local-harness inventory, migration and permission validation. Illustrative editorial layout; not a VS Code interface screenshot. Credit: GitHub, Inc.; editorial layout by AI Speed Canada · Public-domain text logo; trademark rights retained. Wordmark placed in a distinct original 1280×720 editorial composition and converted to optimized WebP.

GitHub announced on November 16, 2026 that Visual Studio Code 1.146 deprecates the older Local harness used to coordinate Copilot agent sessions. Microsoft’s Copilot harness has been the default for new sessions since VS Code 1.143, and the Local harness is scheduled for removal in February 2027.

Changing the harness does not automatically upload local files

GitHub says developers can keep working in VS Code and run agent commands on their own machines; selecting the Copilot harness does not by itself move files to the cloud. The new runtime shares foundations with Copilot CLI and the Copilot app, while its Agent Host process can keep a session available between the editor and Agents window.

That statement should not replace a data-flow review. Models, connectors and tools can still send selected context outside the machine according to their own configuration. Record the model, tool and organization policy used in each regulated workflow.

Related sources: GitHub: VS Code retires the Local harness ↗

Existing customizations need explicit compatibility tests

During the transition, Local remains available where organization policy permits, but new features will focus on the Copilot harness. Teams should start a new session, select Copilot under Session Target and test instructions, skills, MCP integrations, hooks and editor tools. GitHub warns that switching does not automatically convert every customization.

Administrators should locate the temporary vscode.temporaryDefaultToLocalHarness exception. It will be removed with Local, so leaving the policy configured cannot preserve the old runtime after the deadline.

Related sources: GitHub: VS Code retires the Local harness ↗

Sandboxing and assisted permissions remain separate decisions

The Copilot harness supports managed runtime permissions and sandbox restrictions that Local cannot enforce, plus assisted permissions that reduce some prompts. GitHub also says selecting the harness does not enable sandboxing automatically, and actions rejected by risk assessment still require confirmation.

Build a migration matrix covering local commands, repositories, connectors, network access, secrets, accessibility and failure recovery. Canadian teams handling regulated data should capture evidence of where execution occurs and which context leaves the device. Complete the move before February rather than discovering incompatibilities when removal lands.

Sources and editorial method

We use the linked original statements and reports to distinguish documented facts from our analysis. Company announcements describe their authors’ plans and claims; they are not independent verification of future outcomes. This article is dated and will be revised if material evidence changes. Read our editorial standards and corrections process.

  1. GitHub: VS Code retires the Local harness ↗ — Official November 16, 2026 notice; deadline, runtime boundary, migration steps and control differences.