ACN · Presented by Levr
ACN WIRE

Coding tools

VS Code moves its agent to the Copilot harness

New default for agent sessions · Local harness removed Feb 2027

Written with AI assistance, reviewed by the ACN desk.

“By sharing fixes and optimizations instead of repeating work on separate harnesses, we can deliver improvements faster”
VS Code team, VS Code blog, Microsoft
0:00 / 0:00

Image: VS Code blog

The quick hit

  • VS Code has made the Copilot harness the default for new agent sessions.
  • The older Local harness is deprecated and scheduled for removal in February 2027.
  • VS Code reports 14.2% fewer tokens per active device in an October rollout.

VS Code has made the Copilot harness the default for new agent sessions, according to the VS Code blog. A harness is the runtime that drives the agent. The Copilot harness is built on the Copilot SDK. It shares a runtime with Copilot CLI, the GitHub Copilot app and other Microsoft products. For local projects, it still runs on the user’s machine.

The post, by Brigit Murtaugh, reports an October rollout to Copilot Business and Enterprise users on VS Code Stable. Devices on the Copilot harness used 14.2% fewer tokens than those on the Local harness. They made 7.7% fewer model requests. In 12,845 offline side-by-side runs, task completion rose from 54.8% to 61.2%. Runs ending in an error fell from 5.3% to 1.9%.

VS Code says sharing fixes and optimizations across one runtime means it can “deliver improvements faster.” The Local harness, the original editor-specific harness, is now deprecated. It stays available for a three-month transition before removal in February 2027, unless an organization restricts its use.

Not every customization migrates automatically, according to the post. Chat participants, for example, need adaptation, and a Migrations view lists what needs attention. VS Code says work continues on remote bring-your-own-key model support for SSH, WSL and Dev Containers before the Local harness is retired.

“By sharing fixes and optimizations instead of repeating work on separate harnesses, we can deliver improvements faster”
VS Code team, VS Code blog, Microsoft

Sponsor

Sources

  1. VS Code blog · Nov 18, 2026

Spot an error? Email corrections@aicodingnews.si. Fixes are logged on the corrections page.

From our sponsors

Sponsor

Sponsor

Also in

Sponsor

Sponsor