Inter-office memo
- To
- Everyone using GitHub Copilot’s agent in VS Code
- From
- Mo, Chief Executive
- Date
- November 16, 2026, 9:08 PM CST
- Re
- VS Code’s Local harness
VS Code removes its Local harness in February 2027. What changes, and how to switch
VS Code removes the Local harness, the older software behind Copilot’s agent in the editor, in February 2027, GitHub said on November 16, 2026; VS Code 1.146 deprecated it. The Copilot harness, the default since VS Code 1.143, replaces it on the same plans, Copilot Free included. Prompt files, hooks, tool sets and chat participants don’t move by themselves, and own-key and Ollama models need an experimental setting.
What changed on November 11 and 16
VS Code 1.146, released November 11, deprecates the Local harness: “As of this release, the Local harness is deprecated and will be removed in three months (February 2027).” Until then, “it’s functionally frozen. New features and improvements will focus on the Copilot harness and are not guaranteed to be supported by the Local harness.” After that, “The Local harness will no longer be available.”
GitHub filed it under “Retired” on its changelog on November 16, calling the Local harness “the older software that coordinates the model, context, and tools for GitHub Copilot agent sessions in the editor.” Its replacement, the Copilot harness, “is built into VS Code and has been the default for new sessions since VS Code 1.143.” It runs on the Copilot SDK and “shares its coding-agent runtime with Copilot CLI and the GitHub Copilot app.” Microsoft introduced it on October 28 as the harness that “powers Copilot Code, Copilot Studio, the GitHub Copilot app, the CLI, VS Code, and more.”
The names mislead. Local “is a harness name, not a synonym for running on your machine,” VS Code’s harness guide says, and GitHub adds that “Choosing the Copilot harness doesn’t move your files to the cloud.” The harness doesn’t change your model either: “selecting a Claude model in a Copilot harness session still uses the Copilot harness.” What changes is the software around the model, so “The same prompt and model can therefore produce different results in Local and Copilot harness sessions.”
The two harnesses side by side
| From VS Code’s docs, checked November 16, 2026 | Local harness | Copilot harness |
|---|---|---|
| Status | Deprecated and frozen; removed in February 2027 | The default for new sessions since VS Code 1.143 |
| Where the agent runs | VS Code’s extension host; closing the editor window stops it | The Agent Host; it keeps going after you close the window, while VS Code stays open |
| Agents window | Not available | Yes, and a session moves between it and the editor |
Prompt files (.prompt.md) |
Yes | No; convert them to skills |
| Tool sets and chat participants | Yes | Not supported |
| Hooks | Its own | Copilot’s own; no automatic conversion |
| Memory | Local memory files | Copilot Memory, cloud-backed by default |
| Your own API keys and Ollama | Without a GitHub account or Copilot plan | Experimental, behind a setting |
| Admins’ sandbox and permission rules | Not enforced | Enforced |
| Plans | A Copilot plan, or your own keys | “your existing plan, including Copilot Free” |
Who has to act
Most people, nothing yet. “Because the Copilot harness is already the default for new sessions, you might not need to take any new actions,” the release notes say. To check a session, look at its chat title in the editor, where “the active harness is shown as a prefix,” or at the watermark in the Agents window’s chat box.
You, if you still choose Local, and especially if you rely on any of these: prompt files, custom agents or instructions saved in your VS Code profile, hooks, MCP servers that prompt for a key, tool sets, an extension’s @ participant, or your own API keys and Ollama models without a Copilot sign-in. They’re what doesn’t move by itself, below.
Admins who set vscode.temporaryDefaultToLocalHarness. It goes with the Local harness, “so keeping the exception configured won’t keep the Local harness available,” GitHub says.
How to move
- Update VS Code to 1.146, or your organization’s approved release.
- Start a Copilot session. Select New Chat (
+) in the Chat view, or New in the Agents window, then open Session Target and select Copilot, per VS Code’s transition guide. - Back up your customizations, then run Chat: Open Customizations and select Migrations. Migrate “performs supported file moves and conversions,” and Migrate with Agent “starts an agent-led conversation to adapt the workflow and uses Copilot credits.” “Original and migrated files don’t synchronize,” so don’t leave two live copies.
- Bring a Local conversation along, if you need it. In its chat input, open Session Target and select Copilot. “The handoff carries the conversation history and context,” but “This is not a two-way harness switch.”
- Rerun a task you know, and compare the edits, commands and tests, not just the agent’s summary.
What doesn’t move by itself
VS Code’s migration guide lists what to check:
- Prompt files. Copilot harness sessions “do not load
*.prompt.mdfiles.” Convert them to skills. - Agents and instructions in your profile. “The Copilot harness does not read custom agents and instructions stored in VS Code profile user data.” Migration copies them to
~/.copilot/agentsand~/.copilot/instructions. - MCP servers. A workspace’s
.vscode/mcp.jsonmoves to.mcp.jsonat its root, and your profile’s to~/.copilot/mcp-config.json. Servers with password or command inputs,envFile,cwd, SSE or a VS Codeoauthobject don’t migrate automatically, and “Input prompts and stored editor secrets don’t automatically transfer.” Don’t paste the key into the file instead; VS Code warns against “a literal credential in a shared or personal configuration file.” - Hooks. “There is no automatic hook migration.” The guide walks through rewriting each script.
- Tool sets and chat participants. Both “are deprecated and are not supported in the Copilot harness.” For participants, VS Code suggests plugins that combine skills and MCP tools.
- Memory. “Switching harnesses doesn’t convert the existing files.” Copilot sessions use Copilot Memory, stored in the cloud by default.
- Extension tools. They “require an editor window where the extension is running.”
If you use your own keys or Ollama
This is the biggest change for anyone without a Copilot plan. In the Local harness, VS Code’s model docs say, “BYOK models work without signing into a GitHub account and without a Copilot plan,” “including offline scenarios with local models such as Ollama.” In the Copilot harness you turn on chat.agentHost.byokModels.enabled, which VS Code calls an “Experimental Agent Host BYOK setup.” With it, “BYOK models can run in the desktop Agents window without GitHub sign-in,” says its Agents window guide; the browser version “always requires GitHub sign-in.”
Two more things change for Ollama. “The built-in Ollama provider is deprecated”: install the official Ollama extension “and remove the built-in provider configuration to keep using Ollama models without interruption.” And as before, your own models cover chat only: “semantic search, inline suggestions (code completions), and features that rely on embeddings” still need a GitHub account.
If the experimental setting isn’t enough, there are other ways to keep your own keys:
- The Claude harness in VS Code takes an Anthropic API key, set as
ANTHROPIC_API_KEY, and can run without a GitHub sign-in, which VS Code marks experimental. - Codex in VS Code works with a ChatGPT sign-in; for its experimental Agent Host version, “A free ChatGPT account is sufficient.”
- Copilot CLI “automatically discovers models served by Ollama running on your machine,” per GitHub’s docs, which don’t say whether that needs a Copilot plan.
- Outside VS Code, OpenCode finds the models Ollama runs on your computer, and Enjoy runs OpenCode beside Claude Code and Codex. Our local model guide compares the ways.
For admins
- The exception goes away. Remove
vscode.temporaryDefaultToLocalHarnessfrom your plans: it’s removed “along with the Local harness” in February 2027. - To require the Copilot harness now, set
temporaryAllowLocalHarnessandtemporaryDefaultToLocalHarnesstofalseundervscodein enterprise-managed settings, on VS Code 1.143 or later, per the enterprise guide. It “prohibits the Local, Claude, and Codex harnesses.” To nudge people instead, theChatEditorPreferCopilotHarnessdevice policy picks Copilot “without prohibiting other harnesses.” - Switching doesn’t add protection by itself. “Requiring the harness doesn’t turn on sandboxing or add permission rules. Deploy those controls separately.” Then check them with Developer: Policy Diagnostics and
/sandbox policyin a session. - A fallback to Local drops your rules. “The Local harness cannot enforce Copilot runtime-only permission and sandbox controls,” so VS Code says an administrator “must review and accept this gap before permitting fallback.”
What Microsoft and GitHub haven’t said
- The day. Both say only “February 2027”; the harness guide says “by February 2027.”
- What happens to old Local sessions. VS Code says “Local sessions are editor-only” and shows how to carry one over, but not whether they’ll still open once the harness is gone. Move the ones you need before February.
- Whether own-key models leave experimental first. Nothing says when, or if, the Copilot harness’s BYOK setting becomes standard.
- The Chat Participant API’s future. It “remains available for Local harness compatibility, but new integrations should not depend on it,” without an end date of its own.
9.Questions.
What is the Local harness in VS Code?
- It’s the older, editor-only software that runs GitHub Copilot’s agent sessions in VS Code, coordinating “the language model, context, and tools,” in VS Code’s words. Its replacement, the Copilot harness, runs on the Copilot SDK that Copilot CLI and the GitHub Copilot app use. “Local” is only a name; both can run on your own computer.
Do I need to do anything before February 2027?
- Probably not, if you started using Copilot’s agent recently. The Copilot harness has been the default for new sessions since VS Code 1.143, and the chat title shows which harness a session uses. If yours says Local, start a new session, choose Copilot under Session Target, then run Chat: Open Customizations and select Migrations to see what needs moving.
Will my Ollama or own-key models still work after the Local harness goes?
- Only through an experimental setting, for now. The Local harness runs them without a GitHub account or a Copilot plan; the Copilot harness needs the chat.agentHost.byokModels.enabled setting turned on, and VS Code marks that experimental. VS Code has also deprecated its built-in Ollama provider, so install the Ollama team’s extension instead.
Does the Copilot harness need a paid Copilot plan?
- No. GitHub says “you can continue to use your existing plan, including Copilot Free,” though some features and Fusion tiers depend on your plan. Migrate with Agent, which adapts your customizations for you, uses Copilot credits.
Why don’t my prompt files or @ participants work in the Copilot harness?
- Because the Copilot harness doesn’t support them. VS Code says its sessions “do not load” prompt files, so convert them to skills, and that tool sets and chat participants, including extensions’ @ participants, “are deprecated and are not supported in the Copilot harness.”
Can I move a Local conversation to the Copilot harness and back?
- You can move it once. Open it, choose Copilot under Session Target, and its history comes with it, but VS Code says “This is not a two-way harness switch.” Where your organization requires the Copilot harness, opening an old Local conversation can move it for you and archive the original as read-only.