Guide

VS Code Local Harness Removal: Move to the Copilot Harness

By ยท 16 Nov 2026

A developer seen from behind at a pale beech desk looks at a landscape monitor with one faded grey tile and one bright cream tile against a bright lilac wall, with a blank white keyboard on the desk.

Short answer: VS Code v1.146, released Nov 11, 2026, deprecates the Local agent harness and says it will be removed in February 2027. The Copilot harness has been the default for new sessions since VS Code v1.143, so if your sessions already say Copilot you may have nothing to do. If you still rely on Local, check which harness each session uses, convert prompt files to skills, move MCP servers, agents and instructions to Copilot locations, and rewrite hooks by hand before the removal.

We covered the release as news in our Nov 11 brief. This page is the reference version.

What it is

A harness is the software that runs an agent session. It prepares the context the model receives and coordinates tool calls and approvals. In VS Code you pick it from the Session Target picker.

Local is the legacy harness built into the editor. Its sessions live only in the Chat view, and closing that editor window stops its work. Copilot is built on the Copilot SDK, the shared runtime behind GitHub Copilot CLI and the Copilot app. Its sessions run through the Agent Host, so they keep going in the background and open in both the editor and the Agents window.

Switching harness does not change your model or whether you use GitHub Copilot. It can change how the agent behaves, because the harness decides what context and tools the model gets, so compare results on a task you know.

The timeline:

  • VS Code v1.142 added the vscode.temporaryDefaultToLocalHarness enterprise managed setting so organizations could keep Local as the default.
  • VS Code v1.143 made Copilot the default harness for new sessions and added vscode.temporaryAllowLocalHarness.
  • VS Code v1.146 deprecated Local. For the next three months it still works but is functionally frozen, and new features are not guaranteed to reach it.
  • February 2027 is when Microsoft says Local will no longer be available. The vscode.temporaryDefaultToLocalHarness setting goes away with it.

For organizations, the release notes add that the Copilot harness enforces managed sandbox and permission policies that Local does not.

How-to

Back up your customization files first, and pick one small task that already works in Local to compare after the move.

  1. Confirm your VS Code version. Copilot is the default from v1.143.
  1. Check which harness you are on. In the editor, the active harness is the prefix in the chat title. In the Agents window it is the watermark in the chat input, or hover a session in the list to see it in a tooltip.
  1. Open the migration list. Select Copilot as the Session Target, run Chat: Open Customizations from the Command Palette, and select Migrations.
  1. Convert prompt files to skills. Copilot harness sessions do not load files that end in .prompt.md. Expand Convert Prompt to Skills, select the files and select Migrate. The conversion adds disable-model-invocation: true so the skill still runs only when you call it, but drops any agent, model or tools choice, so recheck those.
  1. Move MCP servers. A workspace .vscode/mcp.json moves to .mcp.json at the workspace root, and a profile mcp.json moves to ~/.copilot/mcp-config.json by default. VS Code writes and verifies each new entry before it removes the old one. Servers that use password or command inputs do not migrate automatically. The docs suggest an environment variable reference instead, and say never to paste a real secret into the file.
  1. Move personal agents and instructions. The Copilot harness does not read agents and instructions stored in VS Code profile data. Migration copies them to ~/.copilot/agents and ~/.copilot/instructions. Shared ones belong in .github/agents, .github/instructions and .github/skills.
  1. Rewrite hooks by hand. There is no automatic hook conversion. Copilot reads hooks from JSON files in folders such as .github/hooks and ~/.copilot/hooks. Its camelCase events use toolName and toolArgs where Local used tool_name and tool_input, and decisions such as permissionDecision move to the top level of the output. Stage the new file with a .json.disabled suffix until you have tested it.
  1. Carry over a conversation you still need. Open the Local session in the editor, open Session Target in its chat input and select Copilot. The handoff brings the history and context, but it only goes one way.
  1. Verify. Start a new Copilot session, rerun your test task, and run /sandbox policy to see the sandbox state. We cover that command for Copilot CLI in our /add-dir and /sandbox policy guide.

The script below inventories one repository before you start.

# We have not run this script end to end on every platform. It prints and checks, and changes no files.
# Run it from the root of the repository you plan to migrate. It writes nothing to your shell profile.
set -u

# Step 1: VS Code version. Copilot is the default harness from v1.143.
if command -v code >/dev/null 2>&1; then
  code --version
else
  echo "No code command on PATH. Check Help, About in VS Code."
fi

# Step 4: prompt files that Copilot harness sessions do not load.
find . -path ./node_modules -prune -o -name '*.prompt.md' -print

# Step 5: old and new MCP config files.
for f in .vscode/mcp.json .mcp.json ~/.copilot/mcp-config.json; do
  if [ -f "$f" ]; then
    echo "found $f"
  else
    echo "not found $f"
  fi
done

# Step 5: inputs that do not migrate automatically.
if [ -f .vscode/mcp.json ]; then
  grep -l -e 'input:' -e 'command:' -e 'envFile' .vscode/mcp.json
fi

# Steps 6 and 7: Copilot locations for agents, instructions, skills and hooks.
for d in .github/agents .github/instructions .github/skills .github/hooks ~/.copilot/agents ~/.copilot/instructions ~/.copilot/hooks; do
  if [ -d "$d" ]; then
    echo "found $d"
  else
    echo "not found $d"
  fi
done

echo "Done. Nothing was changed."

Gotchas

  • No exact removal day is published yet. Microsoft says Local will be removed in February 2027, and some doc pages also say removed by February 2027, but the release notes and migration docs do not name a calendar day.
  • Requiring Copilot also blocks Claude and Codex. Setting vscode.temporaryAllowLocalHarness to false prohibits the Local, Claude and Codex harnesses. It does not affect Claude or OpenAI models picked inside a Copilot session.
  • Requiring the harness does not turn on sandboxing. Deploy sandbox and permission rules separately. Since v1.143, a managed sandbox.enabled of true or a nonempty permissions.deny list routes sessions to Copilot unless the temporary Local default is set.
  • The temporary Local default has a security cost. Local does not enforce the runtime sandbox and permission rules that Copilot sessions do, and the docs say an administrator must accept that gap first.
  • These keys belong in enterprise managed settings. The docs say to add them there, not to user or workspace settings, and a developer cannot restore a Claude or Codex harness that policy disables by changing their own settings.
  • MCP details can change. A server you disabled at user level can come back on, per server sandbox settings do not transfer, and workspace variables are written as resolved values, so read the new file before you commit it.
  • Memory does not move. Local memory files and Copilot Memory are separate systems.
  • Tool sets and chat participants are not supported in the Copilot harness. Replace tool sets with tools listed in a custom agent, and participants with a publisher's plugin, MCP server or a direct request.
  • Subagent calls change name. Local calls subagents with runSubagent, while the Copilot harness uses its own task tool. Instructions that name the Local tool need rewording.
  • Hook timeouts can fail open. The migration guide notes that GitHub documents timeouts that continue through normal permissions, including for policy hooks, so test error and timeout paths separately.

FAQ

What changed in VS Code v1.146? The Local agent harness is deprecated and frozen. Copilot has been the default for new sessions since v1.143, so the release notes say you might not need any new action. Check that your prompt files, MCP servers and hooks work in a Copilot session.

How do I keep Local for now? If your organization allows it, start a new session in the Chat view and select Local under Session Target. It is not in the Agents window. On an unmanaged editor, experimental settings keep Local visible: chat.editor.localAgent.enabled true, with chat.defaultToCopilotHarness and chat.editor.preferCopilotHarness false.

How do admins require the Copilot harness? On VS Code v1.143 or later, deploy {"vscode": {"temporaryAllowLocalHarness": false, "temporaryDefaultToLocalHarness": false}} in enterprise managed settings. To nudge without requiring it, set the ChatEditorPreferCopilotHarness device policy to true. Then confirm new sessions use Copilot.

What happens in February 2027? Microsoft says Local and the vscode.temporaryDefaultToLocalHarness setting will be removed in February 2027. No exact day is published yet. Anything that only works in Local, such as prompt files, needs a Copilot replacement before then.

What if something breaks after the switch? Run Developer: Policy Diagnostics to see effective policy values and their sources, and run /sandbox policy in the session. The docs say not to turn off enforcement as a first step. Report product gaps through the VS Code Issue Reporter.

Sources: VS Code v1.146 release notes, VS Code v1.143 release notes, Move from the Local to the Copilot harness, Migrate customizations to the Copilot harness, Agent harnesses, and Manage AI settings.

Recommended AI prompt

Copy this paragraph into ChatGPT, Claude, Gemini, Grok, or whatever AI you use.

Prompt

Act as my VS Code migration reviewer. VS Code v1.146 deprecated the Local agent harness, which Microsoft says will be removed in February 2027, and the Copilot harness has been the default since v1.143. I will paste an inventory of my prompt files, MCP config files and agent, skill and hook folders. Ask me which ones my team uses daily, whether we run under enterprise managed settings, and which MCP servers need secrets. Then give me an ordered migration plan and the checks to run before we retire Local. Cite the VS Code docs "Move from the Local to the Copilot harness" and "Migrate customizations to the Copilot harness", and do not invent settings or commands.