Microsoft announced that the Local harness, previously used to run GitHub Copilot sessions in VS Code, will be retired by February 2027. The Copilot harness, integrated directly into the editor and based on the Copilot SDK, will become the exclusive runtime environment.
- Local harness deprecated and removed by February 2027
- Copilot harness enhances security with managed runtime and sandbox controls
- Migration requires reviewing and updating customizations for compatibility
Infrastructure signal
The retirement of the Local harness reflects a strategic move to unify GitHub Copilot agent execution within VS Code through the integrated Copilot harness. This harness shares its runtime environment with related tools such as Copilot CLI and the GitHub Copilot app, facilitating operational consistency across platforms. From an infrastructure standpoint, this reduces fragmentation and enables centralized management of agent workflows.
Cloud cost implications remain neutral as neither harness moves source files into the cloud—the processing remains local or connected through VS Code. However, the enhanced sandboxing and managed runtime permissions offered by the Copilot harness improve security posture, potentially lowering risk-related costs and operational overhead. Administrators benefit from enforcing runtime restrictions directly, which were not possible with the Local harness.
Developer impact
For developers, switching from the Local harness to the Copilot harness means improved continuity and session management. Sessions can persist across VS Code windows with a shared Agent Host process, allowing developers to maintain workflow context without interruption. The Copilot harness is now the default for new sessions, emphasizing a smoother and more integrated developer experience.
However, developers using the Local harness must review any custom configuration or extensions for compatibility, as not all customizations will transfer automatically. During the transition period, the Local harness remains available where permitted, but new features and updates will target Copilot harness users exclusively, encouraging prompt migration to stay current with improvements.
What teams should watch
Development and IT teams administering VS Code environments must prepare for the mandatory removal of the Local harness by February 2027. This includes auditing any exceptions such as vscode.temporaryDefaultToLocalHarness settings, verifying permission policies, sandbox configurations, and workflow interactions with the new Copilot harness to avoid disruption.
Teams should also track updates from official migration guidance and report any blocking issues promptly to ensure compliance and continuity. Observability enhancements tied to the Copilot harness's managed runtime can aid monitoring and troubleshooting, so teams should update monitoring tools and policies accordingly to leverage these new capabilities.