Visual Studio Code 1.146 marks the end of the Local harness, the component that previously coordinated GitHub Copilot agent sessions. The change forces anyone using Copilot‑driven workflows to switch to the built‑in Microsoft Copilot harness before the February 2027 removal deadline, a shift that touches runtime permissions, sandbox enforcement, and integration points across development and operations tooling.
What changed in VS Code
The Local harness is now deprecated and will be removed in February 2027. Since VS Code 1.143, the Microsoft Copilot harness has been the default for new sessions and is fully integrated into the editor. Selecting the Copilot harness does not move files to the cloud; it continues to run agent commands locally.
Impact on AI and DevOps workflows
The Copilot harness shares its runtime with the Copilot CLI and the GitHub Copilot app, allowing a single session to persist between the editor and the Agents window while the Agent Host process remains active. New capabilities focus on the harness, including:
- Copilot Fusion can automatically select models and, on supported tiers, coordinate drafting and review tasks.
- Assisted permissions reduce approval prompts, though unapproved risk assessments still require manual confirmation.
- Copilot connectors (preview) let you import context from team services without configuring MCP servers.
- Task‑board planning and interactive canvases (preview) enable diagramming and work‑item organization directly in VS Code.
- Existing GitHub Copilot plans, including Copilot Free, remain usable for model access.
Editor‑provided tools continue to need a connected editor, so remote or headless scenarios must still maintain an active VS Code instance.
Operational and security considerations
Administrators gain the ability to enforce managed runtime permissions and sandbox restrictions that the Local harness could not provide. These controls are configured separately; simply selecting the Copilot harness does not enable sandboxing automatically. Teams should audit any vscode.temporaryDefaultToLocalHarness exceptions and verify that required workflows, permission checks, and sandbox policies function with the new harness before the removal date. The temporary enterprise‑managed setting tied to the Local harness will disappear alongside it, so retaining the exception will no longer preserve the old harness.
Next steps for practitioners
- Open a new session in VS Code and choose
Copilotunder Session Target. - Review custom extensions, scripts, or configuration files for compatibility with the Copilot harness.
- Validate permission and sandbox configurations in a test environment.
- Update or remove any
vscode.temporaryDefaultToLocalHarnesssettings and confirm that enterprise‑managed policies reflect the new harness. - Follow the official Local harness transition guide and file a VS Code issue if a workflow cannot be migrated.
Related CloudNinjas coverage: AI engineering.
What This Means For Practitioners
Teams must treat the February 2027 deadline as a hard cut‑off for the Local harness and proactively migrate sessions, permissions, and sandbox policies to the built‑in Copilot harness. Early testing will surface compatibility gaps, allowing remediation before the removal removes the fallback option.


