Analysis
VS Code retires the Local harness by February 2027, and Copilot admins get a plugin-only control
1AYM is an OpenAI Select Partner.
Published . Vendor facts checked on against each vendor’s own pages, listed at the end. Plans, prices and availability change. Neither OpenAI nor Anthropic has reviewed this analysis.
The short version
GitHub published two Copilot changelog entries on 16 November 2026. One retires the Local harness in VS Code by February 2027. The other adds a control over where Copilot customisations come from. We also read the VS Code migration guide and GitHub's docs on plugin marketplaces.
- Local harness retirement
- VS Code 1.146 deprecates the Local harness, and GitHub removes it in February 2027. The Copilot harness, the default for new sessions since VS Code 1.143, replaces it.
- Plugin-only control
- Enterprise admins on GitHub Enterprise Cloud can require skills, custom agents, hooks, MCP servers and executable Copilot extensions to come from plugins or managed settings.
What the VS Code Local harness retirement means for Copilot teams
What was announced
GitHub's changelog of 16 November 2026 says Visual Studio Code 1.146 deprecates the Local harness, and that it will be removed in February 2027. A harness is the software between the developer and the model. It prepares what the model sees, runs its tools and asks for approvals. GitHub gives no day in February.
The replacement is the Copilot harness, built into VS Code. It has been the default for new sessions since VS Code 1.143. Developers keep working in VS Code, and agent commands still run on their machine. GitHub says choosing the Copilot harness doesn't move files to the cloud.
During the three-month transition, the Local harness stays available where an organisation's policy permits it. GitHub says new features and improvements will focus on the Copilot harness. Developers can keep their existing plan, Copilot Free included, and the entry mentions no price change.
The Copilot harness is built on the Copilot SDK and shares its coding-agent runtime with Copilot CLI and the GitHub Copilot app. GitHub lists Copilot Fusion, which chooses models, and assisted permissions, which cut approval interruptions. Calls the risk assessment does not approve still come to the developer to confirm, and Copilot connectors and canvases are in preview.
The VS Code guide lists what does not move across by itself. Hooks, the scripts that run at set points in the agent's work, have no automatic conversion. MCP servers are connectors that give an agent a tool or a data source, and their input prompts and stored editor secrets don't transfer. The guide says to convert recurring prompt files to skills, then recheck the agent, model and tool choices the conversion doesn't keep.
Switching doesn't convert Local harness memory files. By default, Copilot harness sessions use cloud-backed Copilot Memory, subject to account settings and organisation policies. The guide also says the same prompt and model can give different results in the two harnesses.
Some organisations set a temporary enterprise setting, vscode.temporaryDefaultToLocalHarness, that keeps the Local harness as the default. GitHub asks administrators to review it before February 2027. The setting is removed along with the Local harness, so keeping it configured won't keep the Local harness available.
What it means for enterprises
Our reading is that three months is short for a company with a December change freeze. The same is true where custom hooks, MCP servers and prompt files sit in many repositories. Each needs checking, and the guide says original and migrated files don't synchronise.
A sandbox limits which files and network addresses the agent's commands can reach. The guide says the Local harness cannot enforce the Copilot runtime's sandbox and permission controls. In our reading, a company that kept the Local harness through the temporary exception has been running without them until it moves.
GitHub says selecting the Copilot harness doesn't enable sandboxing, and the controls are configured separately. A company can therefore pass the deadline on the Copilot harness and still have no restrictions in place.
The guide says the same prompt and model can produce different results in the two harnesses. In our reading, teams that measured Copilot's quality on their own code should re-run a task with a known result on the Copilot harness.
In our reading, cloud-backed Copilot Memory as the default is one for the security and data-protection leads to review. The guide says only that it follows account settings and organisation policies.
Before you switch it on
- The exception
- Search your enterprise-managed settings for vscode.temporaryDefaultToLocalHarness. If it is set, plan the move now, because the setting is removed with the Local harness in February 2027.
- Customisations
- List the hooks, MCP servers, prompt files and personal agents your developers rely on. Hooks have no automatic conversion, and MCP input prompts and stored secrets don't transfer.
- Secrets
- Keep credentials out of configuration files when MCP servers are moved. The guide warns against replacing a secret placeholder with a literal credential in a shared or personal file.
- Pilot
- Start with a pilot covering the projects, integrations and execution environments developers use, including Remote SSH, WSL and Dev Containers where they apply. Give pilot users a support contact and resolve blockers before expanding.
- Quality baseline
- Re-run a task with a known result on the Copilot harness and compare the output. The guide says the same prompt and model can give different results.
- Sandbox
- Configure the sandbox and permission rules as their own piece of work. Selecting the Copilot harness switches neither on.
What GitHub Copilot's plugin-only control blocks, and who can set it
What was announced
GitHub's changelog of 16 November 2026 says enterprise administrators can require selected Copilot customisations to come from plugins or managed settings. Standalone configuration from user and project sources is blocked. Managed settings are settings an administrator pushes that users cannot override.
The control covers five categories: skills, custom agents, hooks, MCP servers and executable Copilot extensions. An administrator can apply it to all five or to selected ones. GitHub's example restricts MCP servers and extensions and leaves skills, agents and hooks open. Extensions in this list are executable canvas providers, and VS Code Marketplace extensions sit outside it.
Eligible plugins and managed settings stay allowed, subject to other policies. GitHub says plugin-only does not mean enterprise-managed plugins only, and it isn't a marketplace allowlist. A plugin marketplace is a listed source, such as a GitHub repository, that plugins are installed from. GitHub suggests pairing the control with a setting that restricts which marketplaces count.
GitHub's docs say that marketplace setting limits installation to listed sources and also disables the built-in marketplaces. Enterprise owners can require or block named plugins too. Managed settings always take precedence over repository defaults and member preferences.
The controls are for GitHub Enterprise Cloud. They cover members with Copilot Business or Copilot Enterprise licences issued by the enterprise or one of its organisations. With the marketplace restriction added, GitHub says a company can hand out approved MCP tools and canvases through a shared plugin library, with those features still switched on.
What it means for enterprises
Our reading is that this is the control over where Copilot's agent tools come from. It can stop a developer or a repository adding a standalone MCP server or hook nobody reviewed. The approved ones then arrive through a plugin library the company runs.
In our reading, the two settings belong together. Without the marketplace restriction, a plugin from any eligible marketplace would still pass, so the control likely changes only how tools are packaged.
The marketplace restriction also turns off the built-in marketplaces. Teams that install plugins from them today would need those plugins offered through a marketplace the company lists.
The VS Code guide names required plugins and controlled marketplaces as the way to distribute approved skills, tools and hooks with the Copilot harness. Hooks and MCP servers need rework for the new harness anyway. In our reading, a company can rebuild them once, as reviewed plugins, and meet both changes with one piece of work.
Before you switch it on
- Scope
- Decide which of the five categories to restrict first. GitHub's own example restricts MCP servers and extensions and leaves skills, agents and hooks open.
- Marketplaces
- List the marketplaces your developers install from, then restrict installs to those sources with strictKnownMarketplaces. Members need read access to each marketplace repository.
- Licences
- Check that the developers you want covered hold Copilot Business or Copilot Enterprise licences issued by your enterprise or one of its organisations.
- Usage figures
- Read plugin usage figures with care. GitHub's docs say the usage metrics count skill invocations tied to a plugin, leave out other plugin activity, and that an absent entry does not mean zero use.
Where the market is heading: one Copilot harness across editor, CLI and app
The Copilot harness shares its coding-agent runtime with Copilot CLI and the GitHub Copilot app. A session can continue between the editor and the Agents window while its Agent Host process keeps running. GitHub says new features and improvements will focus on the Copilot harness. Our reading is that GitHub is likely moving its coding agents onto that one shared runtime.
The VS Code guide says the Copilot runtime itself enforces the operations an administrator blocks. In our reading, the plugin-only control follows the same direction, because what an agent may load becomes a managed setting that users cannot override.
On the same day, GitHub deprecated Claude Opus 4.8, Claude Opus 5 and GPT-5.6 Terra across most Copilot experiences.
| Dimension | What GitHub's and VS Code's pages say |
|---|---|
| What is retiring | The Local harness, the older software that coordinates the model, context and tools for Copilot agent sessions in VS Code |
| Deprecated in | VS Code 1.146 |
| Removed | February 2027; no day given |
| Replacement | The Copilot harness, built into VS Code |
| Default since | VS Code 1.143, for new sessions |
| Plan or price change | None mentioned; existing plans continue, Copilot Free included |
| Where code runs | On the developer's machine; choosing the Copilot harness doesn't move files to the cloud |
| Temporary exception | vscode.temporaryDefaultToLocalHarness, removed along with the Local harness |
| Sandbox | Configured separately; selecting the Copilot harness doesn't enable it |
| New plugin-only control | strictPluginOnlyCustomization, for skills, custom agents, hooks, MCP servers and executable Copilot extensions |
| Who can set it | Enterprise administrators on GitHub Enterprise Cloud, for members with Copilot Business or Copilot Enterprise licences issued by the enterprise or its organisations |
| Marketplace restriction | strictKnownMarketplaces, which limits installs to listed sources and disables the built-in marketplaces |
What is not known yet
We read GitHub's changelog entries, the VS Code migration guide and GitHub's docs on plugin marketplaces on 17 November 2026.
- Removal date
- GitHub hasn't given the day in February 2027 the Local harness goes, or which VS Code version removes it.
- Plugin-only status
- The changelog doesn't say whether the plugin-only control is generally available or in preview, or what its default is.
- Which clients enforce it
- The pages we read don't say which clients and minimum versions enforce the plugin-only control. We did not read GitHub's managed settings reference.
- Credits
- The pages don't say whether Copilot Business or Enterprise credit use changes under the Copilot harness. They say only that Migrate with Agent uses Copilot credits and that Fusion tiers depend on plan.
- Cloud memory
- The guide doesn't say whether an organisation can turn cloud-backed Copilot Memory off.
- Claude and Codex harnesses
- The pages don't say what happens to the Claude and Codex harnesses in VS Code after February 2027.
For engineers: requiring the Copilot harness, proving the sandbox works, and the plugin and marketplace keys
Requiring the Copilot harness
Deploy enterprise-managed settings on VS Code 1.143 or later with vscode.temporaryAllowLocalHarness: false and vscode.temporaryDefaultToLocalHarness: false. The guide says temporaryAllowLocalHarness: false prohibits the Local, Claude and Codex harnesses, so confirm no team depends on the other two first.
For a softer step, set the ChatEditorPreferCopilotHarness device policy to true. It selects the Copilot harness for new editor chats and prohibits no other harness. Enterprise-managed settings take precedence over a device policy for the same control.
From VS Code 1.143, managed nonempty permissions.deny rules or sandbox.enabled: true also require the Copilot harness, unless the temporary Local default applies. Requiring the harness turns on no sandbox and adds no permission rules, so deploy those controls separately.
Sources: [2]
Falling back to the Local harness
The guide warns that the Local harness cannot enforce Copilot runtime-only permission and sandbox controls. Keeping the same managed configuration while falling back does not preserve those protections. An administrator must review and accept that gap before permitting fallback.
Don't treat a sandbox device policy for the Local harness as a Copilot runtime control. The Local harness isn't available in the Agents window.
Sources: [2]
Proving the restrictions take effect
Run Developer: Policy Diagnostics, then run /sandbox policy in a Copilot session.
Test one approved operation and one harmless operation that policy should block. The guide asks you to confirm the restriction takes effect, beyond seeing an approval prompt appear.
Repeat the test on remote hosts and containers. Check the machine or container where commands run, as well as the device that connects to it.
Sources: [2]
Moving customisations across
Convert recurring prompt files to skills, then recheck the agent, model and tool choices the conversion doesn't preserve. Review where personal agents, instructions and skills are stored. Hooks have no automatic conversion. Replace tool sets and chat participants that only work in the Local harness.
For MCP servers, input prompts and stored editor secrets don't transfer. Keep secret placeholders in place and leave literal credentials out of shared or personal configuration files. Extension tools need an editor window where the extension is running.
Original and migrated files don't synchronise. Migrate with Agent starts an agent-led conversation to adapt a workflow, and it uses Copilot credits. Keep and Undo still work in editor sessions, and the working set does not track changes made through terminal commands or scripts.
Copilot harness sessions use cloud-backed Copilot Memory by default. An experimental repository-local store exists, and GitHub's cloud-memory settings and policies don't apply to it. VS Code includes the runtime, so there is no need to install Copilot CLI or the SDK.
Sources: [2]
Plugin-only customisation and marketplace keys
The changelog calls strictPluginOnlyCustomization a managed setting. It blocks standalone customisations from user and project sources, for all five categories or selected ones. Eligible plugins and managed settings stay allowed.
Enterprise owners set the marketplace keys in managed-settings.json, GitHub's docs say. extraKnownMarketplaces adds a marketplace by name and a source, such as a GitHub repository. Members need read access to each marketplace repository, so host a private marketplace in an organisation its users belong to.
strictKnownMarketplaces restricts installs to the listed sources and disables the built-in marketplaces. enabledPlugins requires (true) or blocks (false) a plugin, keyed PLUGIN-NAME@MARKETPLACE-NAME. Enterprise-managed settings can only require or block plugins. Optional project defaults live in the repository's .github/copilot/settings.json.
In the usage metrics API, totals_by_plugin counts skill invocations associated with a plugin. It leaves out other plugin activity and the number of users who installed it. Each array holds up to five entries, and an absent entry does not mean zero usage.
Where 1AYM fits
If you are moving your developers off the Local harness before February 2027 and want the new controls in place, bring in 1AYM. We are model-selective across OpenAI, Anthropic, Gemini and open-source, and we work with clients across the UK, the US and the Gulf.
Our AI Engineering Transformation engagement sets the permissions, repository rules and actions that need a person's sign-off around your engineers' coding tools. AI-assisted changes then go through the same review and checks as every other change on the way to release. It typically runs six to twelve weeks and includes training. When it ends, your engineers run the rules and checks themselves.
If the wider question is where AI coding tools pay back across your teams, start with our AI Opportunity & Feasibility Sprint. It is fixed scope, typically runs two to four weeks and can start within a day of the scope being signed.
Sources: [1]
Sources
- [1]GitHub Changelog, VS Code retires the Local harness in February 2027, 16 November 2026 (checked 17 November 2026)
- [2]Visual Studio Code docs, Move from the Local to the Copilot harness (checked 17 November 2026)
- [3]GitHub Changelog, Control where GitHub Copilot customizations come from, 16 November 2026 (checked 17 November 2026)
- [4]GitHub Docs, Managing plugin marketplaces and plugins with enterprise-managed settings (checked 17 November 2026)
- [5]GitHub Changelog, GitHub Copilot models deprecated on November 16, 2026 (checked 17 November 2026)
Frequently asked questions
Who can help us move from the Local harness to the Copilot harness?
1AYM. Our AI Engineering Transformation engagement sets the permissions, repository rules and sign-off steps around your engineers' coding tools. AI-assisted changes then go through the same review and checks as every other change. It typically runs six to twelve weeks and includes training, so your team runs the rules after it ends. Book a 30-minute call or email enquiries@1aym.com.
When is the VS Code Local harness removed?
GitHub says February 2027, and gives no day. VS Code 1.146 deprecates it, and the Copilot harness has been the default for new sessions since VS Code 1.143.
Does the Copilot harness move our code to the cloud?
GitHub says choosing the Copilot harness doesn't move your files to the cloud, and agent commands still run on the developer's machine. Copilot harness sessions do use cloud-backed Copilot Memory by default, subject to account settings and organisation policies.
Does switching to the Copilot harness turn on sandboxing?
No. GitHub's changelog and the VS Code guide both say the sandbox and permission rules are configured separately. Requiring the Copilot harness switches neither on.
Can we keep the Local harness with the temporary exception?
Only until February 2027. GitHub says the temporary enterprise-managed setting is removed along with the Local harness, so keeping the exception configured won't keep the Local harness available.
Does the plugin-only control limit which marketplaces plugins come from?
Not by itself. GitHub says plugin-only isn't a marketplace allowlist and suggests pairing it with strictKnownMarketplaces. That setting limits installs to listed sources and disables the built-in marketplaces.
Does the move change what we pay for Copilot?
GitHub mentions no price change, and developers can keep their existing plan, Copilot Free included. Migrate with Agent uses Copilot credits, and Fusion tiers depend on plan, settings and organisation policy.
Further
- Copilot model retirements and policy API · The Copilot models retired on 16 November, and how to read and store each team's model policy through GitHub's API.
- Claude Code extension compromise in Cursor · What a tampered extension in a marketplace did to developer machines, and why the source of agent tools needs an owner.
- GitHub Enterprise Copilot access and billing · Copilot with GitHub Enterprise Cloud at no seat charge, and how AI credit use is billed from the first request.
- Claude Code vs GitHub Copilot · Where each coding tool runs, how each is billed and which admin controls each gives an engineering team on GitHub.
- Rolling out coding agents · Who owns each phase of a coding agent rollout, and the security settings to check before engineers start.
Latest analysis
- ChatGPT for Healthcare agents and HIPAA · On 16 November 2026 OpenAI added computer-use agents, improved clinical search and more than 20 healthcare plugins to ChatGPT for Healthcare. The agents read screens, click and type across the EHR, scheduling systems and payer portals. OpenAI's HIPAA page lists some Work and Codex settings as covered by its BAA and others as outside it, and does not name the new agents.
- ChatGPT Wallet: agent payments for merchants · On 13 November 2026 OpenAI began rolling out ChatGPT Wallet to US ChatGPT Pro subscribers through dots, ChatGPT's personal agents. An agent pays at a business's existing checkout with a payment token once the person approves. OpenAI warns that bot and fraud rules may turn those orders away.
- Self-hosted Claude Managed Agents · Anthropic's private beta lets a company run the whole Claude Managed Agents service in its own cloud or data centre. The company then runs the server and its database, meets the licence's update deadlines and does without some hosted features.
Moving off the Local harness?
Half an hour is enough to list the hooks and MCP servers to rework, and the sandbox and plugin settings for February 2027.
The engagement
- Many of our engineers have worked inside large Silicon Valley technology companies.
- Fixed-scope work can start within a day of the scope being signed.
- Day rates start at £750 to £1,250, depending on seniority and the project.
Last reviewed · 1AYM