AI engineering

VS Code Local Harness Retirement: Move to the Copilot Harness

VS Code 1.146 deprecates the Local harness, which will be removed in February 2027. Check whether you are affected, switch Session Target to Copilot and migrate your customizations.

By EpiFive Editorial TeamReviewed/updated 11 min readHow we check articles
On this page

GitHub announced on November 16, 2026 that Visual Studio Code 1.146 deprecates the Local harness, the older software that coordinates the model, context and tools for GitHub Copilot agent sessions in the editor. The Local harness will be removed in February 2027. To move, start a new chat or Agents session, open Session Target, select Copilot, and then review your customizations before the removal.

This guide covers who is affected, how to check which harness you use, and the migration steps and admin settings that GitHub and the VS Code documentation describe. Nothing here was run on a live installation; see "What we checked" for the details.

What the Local harness retirement is

A harness is the layer that runs an agent session: it coordinates the model, the context and the tools. VS Code's documentation lists several: Copilot, Local, Claude, Codex, and Cloud. Cloud is described as an execution target rather than a separate harness. The Local harness runs in VS Code's built-in harness and extension host; the documentation says sessions stop when the editor window closes and that it is available only in the Chat view, not in the Agents window.

According to the announcement:

  • VS Code 1.146 deprecates the Local harness.
  • It will be removed in February 2027, with a three-month transition period during which it stays available where organization policy permits.
  • The Copilot harness has been the default for new sessions since VS Code 1.143.
  • The replacement is the Microsoft Copilot harness, built into VS Code on the Copilot SDK, sharing its coding-agent runtime with Copilot CLI and the GitHub Copilot app.

The harness is separate from the model and from where code runs. The VS Code migration page states that choosing a Claude model does not switch harnesses, and choosing Copilot does not move files to the cloud.

What the Copilot harness adds, per the VS Code migration page: local sandboxing for builds, tests and commands within configured file system and network boundaries; Copilot Fusion, which selects models and coordinates drafting and review; delegating tasks in the Agents window and continuing the same session in the editor; assisted permissions; and, as preview or experimental features, Copilot connectors, canvases and cloud sessions.

Who it affects and availability

GroupEffect, per the official pages
Individual VS Code users on LocalMove to the Copilot harness before February 2027; review customizations for compatibility.
Teams with prompt files, hooks, MCP servers or custom agentsSwitching harnesses does not automatically convert every customization.
VS Code administratorsReview any vscode.temporaryDefaultToLocalHarness exception; it is removed with the Local harness.
Organizations needing enforced sandbox and permission rulesThese can be enforced only on the Copilot harness.

Existing Copilot plans work, including Copilot Free, according to the announcement. It adds that feature availability depends on your plan, settings and organization policy. The announcement and the pages we opened did not list a separate price for the Copilot harness, and we did not find any region restriction. The announcement does not say which countries are covered, so check your organization policy rather than assuming.

Requirements

  • VS Code version: Local is deprecated in 1.146. The Copilot harness has been the default for new sessions since 1.143, and the enterprise-managed settings below apply on 1.143 or later.
  • Account: sign in with your approved Copilot account. VS Code's page says to update to the approved VS Code release first.
  • No separate install: the VS Code FAQ says no separate Copilot CLI or SDK install is needed.
  • Admin settings: the managed settings must be set as enterprise-managed settings, not user or workspace settings.
  • Desktop app running: for local sessions the Agent Host must keep running, so do not quit VS Code or shut down the machine.

How to check whether you're affected

  1. Open the Chat view or the Agents window and look at the active harness. VS Code's harness page says to check the chat title prefix (editor), the chat input watermark (Agents window) or the session list tooltip.
  2. Open Session Target in a new chat. If you still pick Local, you are on the deprecated harness. The control only lists targets whose requirements are met in the current window.
  3. Look for Local-specific customizations. The migration pages name these: prompt files (*.prompt.md), hooks, tool sets (.toolsets.jsonc), chat participants, workspace MCP servers in .vscode/mcp.json, and agents or instructions kept in the profile's user data.
  4. Administrators: check whether vscode.temporaryDefaultToLocalHarness or vscode.temporaryAllowLocalHarness is set, and run Developer: Policy Diagnostics from the Command Palette to see effective values.

How to migrate to the Copilot harness, step by step

Individual users

  1. Back up or commit your customization files and settings. VS Code warns that original and migrated copies do not sync.
  2. Pick a small task that works on Local and write down its expected result, tools and approvals, so you can compare later.
  3. Open the Chat view or the Agents window.
  4. Select New Chat (+) in the Chat view, or New in the Agents window, and select your project.
  5. Open Session Target and select Copilot. You must choose the harness before your first prompt; changing the model or agent does not change it.
  6. Select an available model and agent. The built-in Copilot agents are Ask, Agent and Plan.
  7. To reduce routine approval prompts, open the permissions picker in the chat input and select Assisted permissions. Calls the risk assessment does not approve still need confirmation.

To continue an existing Local conversation, open it and select Session Target > Copilot in its chat input. History and context carry over, but this is not a two-way switch. VS Code's page also says you can use Open in Agents in the editor and Open in Editor in the Agents window.

Migrate your customizations

  1. With Session Target set to Copilot, select Review Migrations when prompted, or run Chat: Open Customizations from the Command Palette and select Migrations.
  2. Review the detected groups. Migrate performs the supported file moves and conversions. Migrate with Agent (experimental) starts an agent-led chat for semantic changes and uses Copilot credits.
  3. Start a new Copilot session and confirm your items appear in the Agent Customizations editor.
  4. Repeat your test task, check tool activity and approvals, make sure the old and new copies are not both active, then commit workspace changes and remove old files.

What each customization does, according to the migration page:

CustomizationSourceResult
MCP servers (workspace).vscode/mcp.json.mcp.json at the workspace root
MCP servers (profile)Profile mcp.json$COPILOT_HOME/mcp-config.json, or ~/.copilot/mcp-config.json if COPILOT_HOME is unset
Prompt files*.prompt.mdSkills, with disable-model-invocation: true added; agent, model and tools selections are not preserved
User agents and instructionsProfile user data~/.copilot/agents, ~/.copilot/instructions; not part of Settings Sync
HooksVariousManual only

Points that often catch people:

  • MCP: migration adds tools: ["*"], which you should narrow. Password inputs, command inputs, cwd, envFile and VS Code oauth objects do not convert. Replace secret prompts with environment-variable references such as ${SERVICE_API_KEY} and never paste literal credentials.
  • Hooks: configuration and scripts must both be rewritten. Event names change, for example PreToolUse becomes preToolUse and Stop becomes agentStop; standalone files need version: 1, and command preToolUse errors deny the tool. Test the script directly with sample stdin and in a disposable session.
  • Tool sets and chat participants: deprecated in Copilot; replace with custom-agent tools lists, plugins, MCP servers or direct requests.
  • Subagents: Local's runSubagent becomes the Copilot harness's task tool.
  • Memory: Copilot Memory is separate from Local memory files and is not converted.

Administrators

  1. Pilot first, including Remote SSH, WSL and Dev Containers where you use them. VS Code says remote and container sandbox prerequisites differ.
  2. To require the Copilot harness on VS Code 1.143 or later, use enterprise-managed settings (not user or workspace settings): temporaryAllowLocalHarness: false (this prohibits Local, Claude and Codex) and temporaryDefaultToLocalHarness: false.
  3. To encourage without requiring, set the ChatEditorPreferCopilotHarness device policy to true.
  4. Optionally set model to "auto" and a fusionTier of "standard", "high" or "max". VS Code says these are starting defaults, not restrictions.
  5. Configure permissions and sandboxing separately. Requiring the harness does not enable them, although nonempty managed permissions.deny rules or sandbox.enabled: true also route to the Copilot harness from 1.143.
  6. After deployment, start a new editor chat and Agents session, confirm the harness and model, and run Developer: Policy Diagnostics. In a Copilot session, run /sandbox policy to see the sandbox state, file access and network restrictions.

Limitations, testing and rollback

  • Temporary fallback only: per VS Code's page, you can select Local under Session Target in the editor for a new session, but not in the Agents window. Administrators can set vscode.temporaryDefaultToLocalHarness to true, but this does not override vscode.temporaryAllowLocalHarness: false and does not restore Claude or Codex. It is a blocker-only measure, and the announcement says it ends with the removal.
  • Security gap on Local: the harness page says Local does not enforce runtime-only sandbox and permission rules, and SDK Policy Hooks do not load in it. An administrator must accept that gap before allowing the fallback.
  • Not every tool exists on Copilot: not all built-in or extension tools are available, and extension tools need an editor window where the extension runs.
  • Session continuity: local Agent Host sessions need desktop VS Code to keep running; closing a window is different from quitting the app.
  • Experimental pieces: cloud sessions, mixed-harness chats, computer use and the customization migration feature are labeled experimental or preview.
  • Rollback: VS Code's migration page has no dedicated rollback procedure. The closest guidance is to keep customization backups until migrated results are verified and to remove any temporary Local exception before February 2027.

Suggested test list, from VS Code's verification checklist: run a representative task and check the edits, command results and tests; confirm customizations load and required tools are available; run Developer: Policy Diagnostics; test one approved and one policy-blocked operation on a disposable path; repeat on remote hosts and containers.

Privacy and admin notes

  • Where code runs: the announcement says selecting the Copilot harness does not move your files to the cloud. Cloud sessions are a separate, experimental Session Target.
  • Approvals vs. sandboxing: VS Code's approvals page lists three permission levels on the Copilot harness: Manual permissions (the default), Assisted permissions ("Uses an LLM judge to assess each tool call") and Allow all. Sandboxing is independent of the level, and an enabled sandbox still restricts terminal file system and network access under Allow all.
  • Sandbox status: preview on macOS, Linux and WSL2, experimental on Windows, per the approvals page. Restart VS Code after changing the network filter settings it lists.
  • Enterprise controls: organizations can set a managed default permission level; policy-blocked levels stay visible but disabled. Claude and Codex harnesses are disabled when Copilot enterprise-managed settings apply.
  • Telemetry: OpenTelemetry is available for both harnesses, but VS Code says to verify the exporter, capture settings and attributes after switching.
  • Training data: we did not find a statement about model training on these pages, so we make no claim either way.
  • Support: VS Code's page points to your AI enablement or IT team for policy, the VS Code Issue Reporter for bugs, and GitHub Support for Business and Enterprise customers. Remove credentials and sensitive policy details before sharing logs.

For related context, see our posts on GitHub Copilot model deprecation in December 2026 and Copilot connectors.

What we checked

  • Opened the GitHub Changelog announcement dated November 16, 2026 on 2026-11-17: Local deprecated in VS Code 1.146, removal in February 2027, Copilot harness default since 1.143.
  • Opened VS Code's "Move from the Local to the Copilot Harness" page on 2026-11-17: the February 2027 removal and the enterprise-managed settings match the announcement.
  • Cross-checked the Session Target labels (Copilot, Local, Claude, Codex, Cloud) between the agent harnesses page and the migration page.
  • Cross-checked vscode.temporaryDefaultToLocalHarness and vscode.temporaryAllowLocalHarness across the announcement, the migration page and the customization migration page.
  • Opened the customization migration and approvals pages on 2026-11-17 for the file paths, hook event mapping and permission level names quoted above.
  • The announcement gives no exact day in February 2027, and the pages we opened do not either; we did not guess one.
  • Not tested in a live VS Code installation or organization; steps follow the official pages as of 2026-11-17, and the migration feature is labeled experimental.

Last tested: 2026-11-17

Sources

Questions people ask

When is the VS Code Local harness removed?

GitHub's announcement of November 16, 2026 says VS Code 1.146 deprecates the Local harness and that it will be removed in February 2027. VS Code's own documentation gives the same month. Neither page gives an exact day in February.

Will my Copilot chats, files or code move to the cloud if I switch?

No. The announcement says selecting the Copilot harness does not move your files to the cloud, and you can still run agent commands on your machine. Cloud is a separate Session Target that VS Code documents as experimental.

Does keeping vscode.temporaryDefaultToLocalHarness keep the Local harness after February 2027?

No. The announcement says this temporary enterprise-managed setting will be removed together with the Local harness, so keeping it configured will not keep the Local harness available. It is a blocker-only fallback for the transition period.

Do my hooks and MCP servers move automatically?

MCP servers can be migrated automatically with Migrate in the Customizations editor, although some properties are dropped and you must verify authentication. Hooks have no automatic migration and must be converted by hand, including their scripts.

Does switching harness also turn on sandboxing?

No. GitHub says selecting the Copilot harness does not enable sandboxing. Managed runtime permissions and sandbox restrictions can be enforced only on the Copilot harness, and administrators must configure them separately.

VS CodeGitHub CopilotCopilot harnessAgent modeMCP
  1. Build Your First MCP Server in Python: Tools, Resources and Testing

    Build a Model Context Protocol server in Python with the official SDK, expose a tool and a resource, test it with MCP Inspector and a Python client, and connect it to VS Code.

    AI engineering9 min read
  2. GitHub Copilot Model Deprecations on Dec 14, 2026: What to Switch To

    GitHub will deprecate six Copilot models on December 14, 2026. See which models go, the suggested replacements, and how users and admins should switch.

    AI engineering8 min read
  3. Handling LLM API Rate Limits: Retry, Backoff and Queues in Python

    Handle 429 errors from the OpenAI API in Python with Retry-After, exponential backoff with jitter, a concurrency limiter and a queue, without retry storms.

    AI engineering9 min read
  4. Microsoft 365 Copilot License Assignment: Prerequisites and Rollout

    Check base licenses, update channels, mailboxes, OneDrive, Teams and network access, then assign Copilot licenses with group-based licensing or Microsoft Graph PowerShell.

    AI engineering11 min read
  5. Building a Golden Dataset to Regression-Test LLM Features

    Build a golden dataset for an LLM feature: collect cases, label them, choose code-based and LLM graders, run it in CI and grow it from production failures.

    AI engineering10 min read
  6. Build RAG Over SharePoint Documents Without Breaking Permissions

    Ground an internal AI assistant on SharePoint files so each user only gets answers from documents they can open, using the Copilot Retrieval API or Azure AI Search with ACL ingestion.

    AI engineering12 min read