VS Code deprecates legacy AI agent harness
Microsoft has functionally frozen Visual Studio Code's legacy Local agent harness, scheduling complete removal for February 2027. Teams must migrate extensions, permissions, and hooks to the Copilot harness to maintain background session support.
The death of the window-bound Local harness signals VS Code's shift from an interactive editor assistant to an autonomous background agent platform. This is an enterprise security overhaul disguised as runtime cleanup.
- –Stricter execution boundaries: Moving to the Copilot harness enforces centralized sandbox controls and auto-approval policies, stripping extensions of unmonitored command execution.
- –Multi-session persistence: The Copilot SDK runtime decouples agents from individual editor windows, enabling features like Inbox mode and cross-project agent management.
- –Enterprise settings expiration: Fallback flags like vscode.temporaryDefaultToLocalHarness will be erased in February 2027, forcing DevSecOps teams to audit permission rules now.
- –Extension migration pressure: Community and internal extensions tied to legacy chat participant APIs must adopt the Copilot SDK before the freeze breaks automated workflows.
DISCOVERED
2h ago
2026-11-15
PUBLISHED
2h ago
2026-11-15
RELEVANCE
AUTHOR
OutworkVentures