GitHub announced on Nov. 16, 2026, that VS Code 1.146 deprecates the Local harness and plans to remove it in February 2027. The Copilot harness has been the default for new sessions since VS Code 1.143. For developers, the main preparation is checking which customizations and active conversations need attention before the change. (GitHub’s announcement)

Treat changing the session target as the start of migration, not the whole job: check each customization and test the workflow it supports.

Which VS Code customizations need a closer look?

Migration depends on the customization. VS Code can convert or move some items, but those paths may not preserve every setting. Hooks have no automatic conversion, while Chat Participants and some MCP configurations may need manual changes or a replacement. (VS Code’s customization migration guide)

CustomizationDocumented migration pathWhat to check
Prompt filesCan be converted to skills.Agent, model, and tool selections specific to the prompt do not carry over.
HooksNo automatic conversion.Plan a manual migration for any workflow that depends on them.
Chat ParticipantsUse a publisher-provided replacement or make a direct request to the agent.Check whether the replacement supports the task your workflow needs.
MCP configurationsSome entries or settings may need manual handling.Review unsupported fields, authentication, and sandbox behavior.

If your MCP setup spans VS Code and Copilot, our guide to configuring MCP across both covers the separate configuration formats. Keep that setup review distinct from the broader harness change.

Before retiring a working setup, back up relevant files and settings, review detected items in Chat: Open Customizations under Migrations, then test a representative task. A new session starts by opening a chat, choosing Copilot under Session Target, and selecting an available model and agent. (VS Code’s migration guide)

What happens to an existing Local conversation?

VS Code describes handing a Local conversation to Copilot with its history and context. Depending on conversation-import support, the result may be an imported session or a new Copilot conversation with the transcript attached; the original conversation remains available. Review the tools, model, and permissions before continuing, since they can differ after the handoff. (VS Code’s conversation migration guide)

Choosing the Copilot harness does not move workspace files to cloud storage. A cloud sandbox is a separate execution option, and administrators configure its restrictions separately. (GitHub’s announcement, VS Code’s migration guide)

What should administrators prepare?

Administrators should test the workflows their teams rely on, along with managed permissions and sandbox settings. Selecting Copilot does not configure those controls automatically. GitHub also says the temporary vscode.temporaryDefaultToLocalHarness setting will be removed with the Local harness, so it will not preserve access after the planned removal. (GitHub’s announcement, VS Code’s migration guide)