AI NewsDev toolsAnnouncement

VS Code moves Copilot to a new harness, retires the Local one in February

VS Code makes the Copilot harness the default for agent sessions and retires the Local one in February 2027. Teams have three months to migrate.

AI News

Editorial2 min read

LinkedInX

Why it mattersAny team with custom prompts or chat participants needs to run the migration. Agent sessions quietly use different code after this change.

The code editor that most developers work in is quietly changing which runtime talks to its agent. VS Code made the Copilot harness the default on 18 November. The author of the post is Brigit Murtaugh. The Copilot harness is a runtime shared across the GitHub Copilot CLI, the Copilot app and VS Code. The Local harness is what came before. It was editor-specific and built for interactive coding when no shared runtime existed.

The post says the Local harness is now deprecated. It remains available during a three-month transition. Removal is in February 2027. That removal is not conditional on usage. A team on an organisation with restrictions may get a different timeline through its admin.

The measurements Microsoft published

VS Code ran two kinds of comparison. The first is an online rollout to Copilot Business and Enterprise users on VS Code Stable in October. Those users on the Copilot harness used 14.2 percent fewer tokens per active device than users on the Local harness. Estimated processing cost per active device was 9.6 percent lower. Model requests per device dropped 7.7 percent. The cost per model request fell 2.3 percent.

The second is offline. VS Code ran 12,845 side-by-side comparisons across several days. On 112 long coding tasks from the DeepSWE benchmark, across seven models, the Copilot harness changed three things. Runs ending in error fell from 5.3 percent to 1.9 percent. Runs that hung or crashed fell from 3.1 percent to 0.2 percent. Task completion rose from 54.8 percent to 61.2 percent.

What a team needs to do

The post names the migration. Chat participants need adaptation, because the Chat Participant API predates VS Code's agent loops. Recurring prompt files may need converting to skills. Hooks, MCP setup, authentication and file locations should be reviewed. VS Code has a command for the audit. Run Chat: Open Customizations and open the Migrations view. The command lists the items that need action for the current workspace.

Two features are still being brought over. Remote Bring Your Own Language Model support in SSH, WSL and Dev Containers is in progress. The post says the team is "actively working toward" it before the Local harness is fully retired. Agent Host sessions now persist after the project window closes. That is new to the Copilot harness and not available on the Local one.

Source

The Copilot harness: Building on a shared foundation, Visual Studio Code.

This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.

Share
LinkedInX
Start a project