Skepra / Web recovery & resilience

VS Code retires the Local harness in February 2027

A VS Code agent workflow depends on a harness scheduled for removal and its replacement has not been accepted.

Discuss the next maintenance decision

GitHub's November 16 weekly release notes say that the Copilot harness is already the default for new sessions in VS Code and that the Local harness is scheduled for removal in February 2027. The same notes point to a transition guide. This is a support-end and compatibility decision for teams that rely on agent sessions, extensions, terminals or repository instructions. It is not evidence that a particular client's current build is broken.

Find the sessions that depend on the old harness

Inventory the VS Code version, Copilot extension, session type, harness selection, extension integrations, terminal assumptions and repository instructions. Record which workflows are interactive and which are part of a client release or review process. A team may have different behavior for existing sessions, new sessions and centrally managed settings.

Compare one real workflow

Use a sanitized repository and run the same acceptance set under the current and target harness:

  • open the repository and identify the working directory;
  • inspect and edit a fixture;
  • run the approved test command;
  • use the required extension or MCP integration;
  • review the diff and produce a handoff summary;
  • interrupt and resume the session if the workflow depends on recovery.

Record prompts, tool permissions, terminal output, extension warnings and the resulting diff. Do not use a customer production repository as the first migration test.

Agree a migration checkpoint

If the target harness passes, set a team migration date before February 2027 and update onboarding instructions. If it fails, record the exact incompatibility and assign it to the extension, workspace policy or workflow owner. Do not promise that the Local harness will remain available beyond the stated removal window.

The client-facing artifact is a harness inventory, test matrix, supported configuration, migration owner and fallback plan. This lets an agency explain whether the work is a planned compatibility change or a separate application defect.

Applicability and limits

The source describes GitHub Copilot in VS Code and its harness transition. Plan, extension, organization policy and preview availability may change the observed behavior. No repository, client or deployment is asserted affected.

Primary source: GitHub Copilot weekly releases - November 9.