Developers still using VS Code’s Local agent harness should move their workflows to Copilot and check their customizations before February 2027. Microsoft deprecated Local in VS Code 1.146, released November 11, 2026, and scheduled its removal for February. It has not specified an exact removal day.
The move from Local to Copilot does not require cloud execution. A harness is the software coordinating the AI model, conversation and tools. Copilot can still run commands on your machine; Cloud is a separate execution target. Local execution does not mean the language model runs offline or on your computer.
Check whether your workflow still uses Local
Copilot has been the default for new sessions since VS Code 1.143. If your required workflows already work there, you may not need to migrate anything. Check the actual session, not just the model name: changing models does not change its harness.
Before changing files, follow Microsoft’s preparation guidance: use an approved VS Code release and the intended Copilot account, back up settings and customizations, and pick one small task that already works. Record its expected result, required integrations and approvals.
In the Chat view, select New Chat; in the Agents window, select New. Open Session Target and choose Copilot, then select an available model and agent. The harness guide explains how to identify existing sessions. Available choices depend on your setup and organization’s policies.
Convert supported files, then inspect what changed
Run Chat: Open Customizations and open Migrations to review detected items. Migrate performs supported file operations. Migrate with Agent starts an agent conversation that consumes Copilot credits; that assistance is experimental. These are different migration paths. Budget for agent assistance separately.
Prompt files become skills. Copilot does not load
*.prompt.mdfiles. Conversion retains reusable instructions but drops the prompt’sagent,modelandtoolsselections. Recreate any necessary choices or restrictions separately. Generated skills includedisable-model-invocation: true, preserving explicit invocation rather than automatic selection.Personal agents and instructions need the right location. Files in VS Code profile storage can move to Copilot’s user folders. Microsoft notes that the migrated files are not included in Settings Sync. Keep personal workflows at user scope.
MCP server entries need a backup and enabled-state check. MCP connects agents to external tools and services. Compatible migration verifies destination entries before removing migrated source entries. User-level disablement can be lost, so inspect each destination client before using a previously disabled server.
Tool sets and chat participants need adaptation. Local-specific tool aliases and participant workflows are not automatically preserved. Use supported tools, custom agents, skills or the integration publisher’s replacement, following the compatibility checklist.
A converted prompt can appear in the menu yet behave differently because its old tool selection is gone. Treat file conversion as preparation, not acceptance. In a fresh session, invoke the skill yourself and inspect its output and tool activity.
Restore service access and review hooks
MCP definitions that depend on editor input or command variables are not forwarded to Copilot. Its authentication reference also documents no built-in bridge from prompted secrets or VS Code SecretStorage to an HTTP authentication header. Use the service’s supported authentication flow, such as OAuth where available. Do not fix a missing connection by pasting credentials into personal or shared JSON.
Portable Copilot MCP files use mcpServers in workspace-root .mcp.json or the execution host’s user configuration. Merely moving an editor file is insufficient: its envFile behavior and per-server sandbox settings do not transfer through forwarding. Review the destination configuration and verify the actual service tools.
Hooks—scripts triggered by agent events—need manual adaptation. Review event names, arguments, outputs and failure handling against the Copilot hook contract. For command preToolUse hooks, documented errors deny the call, while timeouts fall through to normal permissions. Those are different outcomes to check.
Also check which hooks are active. Copilot can combine repository, user and plugin hooks; a new copy does not replace the old one. Local controls such as chat.useHooks do not preserve disablement in Copilot. Avoid duplicate execution and keep intentionally disabled hooks inactive.
Check editor-dependent integrations separately. Client-provided tools need a connected VS Code client. A continuing agent session does not guarantee that an extension’s tools remain available. Enabling a tool also does not grant approval for every action it can take.
Verify permissions on the machine running the task
Switching harnesses does not by itself turn on sandboxing. The VS Code setting defaults to off unless enabled or required. In the destination session, run /sandbox policy to inspect the execution host and effective file and network restrictions. Microsoft says this policy report neither starts a model turn nor changes settings.
For Remote SSH, WSL or containers, check the host that actually runs commands. A working setup on a developer’s laptop does not establish that the same integrations and restrictions work remotely.
Administrators should distinguish preferring Copilot from requiring it. From VS Code 1.143, the enterprise-managed vscode.temporaryAllowLocalHarness: false control prohibits Local, Claude and Codex harnesses. Review effective managed policies before rollout; a default choice is not equivalent enforcement. Merge changes with existing settings rather than replacing them.
Carry over conversations without assuming a reversible switch
For an existing Local conversation, open it in the editor and choose Session Target → Copilot. The handoff carries history and context, but the receiving harness cannot simply hand the session back. Recheck the destination’s model, tools and permissions before continuing.
A policy-required move has a different path. On hosts with import support, it preserves history and unsent input and archives the original read-only. Otherwise, Continue in Copilot attaches the transcript to a new conversation, preserves the unsent draft and retains the original. Neither route automatically submits the unsent prompt.
Check usage costs and the model separately
Do not budget this as a fixed-price migration. Ordinary file conversion differs from agent-assisted adaptation and the model calls used to validate the result. On usage-based plans, GitHub calculates AI credits from model and token consumption, with one credit equivalent to US$0.01. Using an included allowance is not necessarily an extra charge. Existing annual request-based plans have separate rules.
Check model availability before comparing results. Where access permits, keeping the same model makes it easier to isolate a harness change. Model retirement is a separate task; our guide to Copilot’s November model replacements covers the November 16 changes.
Accept the workflow only after two separate checks
A useful acceptance rule is to check both whether the intended task works and whether its boundaries still hold. A successful edit does not establish that a denied action would be blocked; a stricter destination may correctly reject something the old setup allowed.
Check the work. Run the small task in a fresh Copilot session. Inspect changed files, results, invoked tools and recorded usage. Confirm that required skills, hooks and integrations actually ran—not merely that their files appeared.
Check the boundaries. In a disposable workspace, use harmless examples to verify expected approval and denial behavior. Check hook errors and timeouts separately. Repeat the relevant checks on each host type your team uses.
If your workflow includes another agent reviewing a plan, include that step in the comparison. The VS Code second-opinion coding-plan guide explains the separate context and file-access decisions; do not assume a harness migration preserves them.
Keep backups until the replacement works, including originals of MCP entries already removed by automatic migration. If an integration remains blocked, record the version, execution host and a minimal non-secret reproduction for its publisher or your administrator. Temporary Local availability depends on policy, and its default override is also scheduled for removal in February 2027. Resolve the dependency before then rather than weakening managed controls to complete the switch.
