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:
- Copilot sessions run in the background. Copilot sessions run through the Agent Host, so they keep running when the editor window closes, and you can reach them from the editor window and from the Agents window. Copilot is built on the Copilot SDK, the shared foundation across Copilot products. For organizations, it also enforces managed sandbox and permission policies that Local does not.
- Inbox mode gathers what needs attention. Inbox mode, experimental and off by default (
sessions.list.inboxEnabled), gives one view of sessions across projects: the ones that need attention sit at the top, above Working, Ready to merge, On hold, and Done. Sessions that can wait can be dismissed from the Inbox, put on hold, or snoozed. A dismissed session is not archived. To archive it, select Mark Session as Done. - Permission prompts get more granular. Copilot used to suggest broad tool-level allowances — fetching a URL defaulted to "Allow in this Session", which covered any URL for the session. Prompts now add allowances for specific domains, commands, and directories by default.
- A transition guide covers the move. Microsoft's transition guide covers customization compatibility, continuing existing Local conversations, and organization rollout and verification.
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
- This page covers the 1.146 release notes only. No session was moved between the two, and no Inbox mode or permission prompt was tried.
- The release notes do not say what happens to a Local conversation that is still open when Local is removed. The transition guide is the place to check before February 2027.
- 1.146 is a separate release from 1.145, which introduced the Agent Host sessions this release builds on.
Related playbooks
- Factory Droid 1.0 and the harness-efficiency claim
- Foundry Local runs Qwen3.8-27B on your GPU
- MAI-Code-1.1-Flash: local coding on RTX Spark
- Run Muse Spark in another harness via the Model API
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