Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding

VS Code 1.146 retires the Local harness

Written November 11, 2026

Visual Studio Code 1.146, released November 11, deprecates Local. It will be removed in February 2027. Copilot, the default for new sessions since 1.143, is the replacement — and this release changes how its sessions live and how they ask permission.

The problem

If you still run agent sessions on Local, you have three months to move. Local is functionally frozen from this release: new features and improvements go to Copilot and are not guaranteed to work on Local. After three months it stops being available at all. The enterprise setting that let an organization pin Local as the default, vscode.temporaryDefaultToLocalHarness, goes away with it.

What 1.146 changes

The 1.146 release notes put the deprecation first, and the rest of the release follows from the same move to Copilot:

The same release notes carry Copilot Fusion going generally available. That is covered by the existing Copilot Fusion page, not this one.

What to do

Open the Session Target picker when you start a new session and check that it says Copilot. If it does, you may not need to do anything — Copilot has been the default for new sessions since 1.143. If you are still on Local, plan the move before February 2027, using the transition guide for existing conversations and customizations. Organizations should stop relying on the vscode.temporaryDefaultToLocalHarness setting now, since it is removed with Local.

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: VS Code 1.145: Agent Host keeps sessions alive · Copilot Fusion is generally available: what it does to your AI-credit bill · Copilot CLI 1.0.109: CIDR sandbox rules · Copilot CLI now configures MSBuild itself