Daily brief
Copilot Drops Three Models, Enterprises Can Require Plugins for Customizations, and Claude Code v2.1.326 Flags Broken Tool Rules
By Steven Sorensen ยท 17 Nov 2026

At a glance
- Three older Copilot models left the model picker, so any workflow that names them needs a new choice now.
- Enterprise admins can now require that Copilot skills, agents, hooks, MCP servers and extensions come only from plugins or managed settings.
- The newest Claude Code build warns about incomplete tool rules at startup and tells you when a settings file could not be saved.
- Copilot CLI and Codex shipped only prerelease builds, and both Cursor changelogs are unchanged.
GitHub posted the model retirement and the customization control on the GitHub Changelog on Nov 16, and Anthropic published Claude Code v2.1.326 to npm at about 1:43 PM ET Mon Nov 16. All three are inside our usual window.
Treat today as a check your pins day: replace any retired Copilot model your scripts or prompts name, decide whether your enterprise should require plugins for Copilot customizations, and watch for new startup warnings after you move Claude Code.
Top Stories
1. Copilot retires Claude Opus 4.8, Claude Opus 5 and GPT-5.6 Terra
As of Nov 16, GitHub has deprecated three models across most Copilot experiences, including Copilot Chat, inline edits, ask and agent modes, and code completions. GitHub announced the change on Oct 15, so this is the date arriving rather than a surprise. It is a different set of models from the Dec 14 retirements we covered Nov 14 and Nov 15. The suggested replacement for both Claude models is Claude Opus 5.5, and for GPT-5.6 Terra it is GPT-6.1 Sol or GPT-6 Luna.
There are two exceptions in the post. Claude Opus 4.8 stays available to individual Copilot subscribers on annual plans, and Claude Opus 5 is gone from the picker but remains available as a fallback when a request is refused, through access that was already authorized. Existing enterprise model policies continue to apply.
For Copilot Business and Enterprise, the suggested alternatives are switched on automatically under default model enablement, unless an admin turned off the global default or disabled the model. If your organization turned off that default, someone has to enable the replacements in the model policies before developers see them.
Practical dev impact: If a prompt file, a team guide or an automation names one of these three models, update it today so nobody falls back to a model they did not choose. Admins who turned off default enablement should open the model policies today, because the replacements will not appear on their own.
If your team still runs the VS Code Local harness, our guide to moving to the Copilot harness walks through the switch.
2. Enterprise admins can require plugins for Copilot customizations
GitHub added a managed setting, strictPluginOnlyCustomization, that blocks standalone Copilot customizations that come from user or project configuration. Customizations that arrive through eligible plugins or managed settings are still allowed, subject to your other policies.
You can apply it to all five supported categories or pick some of them. The categories are skills, custom agents, hooks, MCP servers and executable Copilot extensions. GitHub gives the example of restricting MCP servers and extensions while leaving skills, agents and hooks open. Extensions here means executable canvas providers, not VS Code Marketplace extensions.
GitHub is careful to say this is not an allowlist of marketplaces and does not mean only enterprise managed plugins. To limit where plugins can come from, pair it with strictKnownMarketplaces, and your existing managed settings can still require or block specific plugins. The control is for GitHub Enterprise Cloud, for members whose Copilot Business or Copilot Enterprise license comes from the enterprise or one of its organizations.
Practical dev impact: If your team keeps MCP servers or hooks in project files today, those would stop loading once an admin restricts that category. Before anyone turns this on, move the approved items into a shared plugin, so the change removes only the setups nobody reviewed.
3. Claude Code v2.1.326 warns about tool rules and settings that silently failed
Claude Code v2.1.326 is now the latest build on npm, while the stable tag still points at v2.1.311. The changelog adds a startup warning when an --allowedTools, --disallowedTools or --tools value has an entry that does not look like a complete rule. It also explains why MCP servers stop loading when an administrator adds a managed MCP file during a session, and /status gains a row that says when your provider or an environment variable turns features off.
Several fixes are about settings that looked saved but were not. Rules added in /permissions or at a tool prompt, and folders added with /add-dir, could look saved when the settings file could not be written, and the terminal now warns and names the file. A settings file saved with an error during a session was skipped silently and now gets a warning too. The transcript also stops describing commands that delete or overwrite files, such as find -delete or sort -o, as a search or a read.
Practical dev impact: If you pass tool rules in scripts or CI, run them once on v2.1.326 and read any new startup warning, because a rule it flags may never have matched. Teams on the stable tag can wait, since these changes are on the latest channel only for now.
Practical Impact Analysis
Our read: the model retirement has the widest reach and the only deadline that has already passed, so it leads. The plugin control reaches fewer people, but it changes where customizations may live for whole enterprises, and the Claude Code release matters most to anyone who relies on tool rules in automation.
The common thread is configuration that fails quietly. A retired model name, a project MCP server that an admin later blocks, and a tool rule Claude Code could not parse can all leave a developer running something other than what they set up. The useful habit this week is to read the warnings and the policy pages rather than assume your setup still holds. Copilot CLI tagged v1.0.113-1, a prerelease whose notes add a managed setting that lets admins turn off its built in Browser Use, and Codex posted more v0.171.0 alpha builds. Keep both on a test machine only and stay on the current stable releases for daily work.
Tutorial
- Open a test shell. Every command below only reads files, versions or public package data.
- Step 1 prints the current npm tags for Claude Code and Copilot CLI and compares them with this morning's snapshot.
- Step 2 shows which Claude Code build is on this machine.
- Step 3 searches the current project for the three retired model names and for tool rule flags worth checking.
# We have not run this script end to end on every platform. It prints and checks, and changes no files.
# Run it in a test shell. Nothing is written to your shell profile.
# Snapshot at 5:58 AM ET Tue Nov 17 2026:
# claude-code latest v2.1.326, stable v2.1.311
# copilot latest v1.0.112, prerelease v1.0.113-1
# 1. Current npm tags.
if command -v npm >/dev/null 2>&1; then
npm view @anthropic-ai/claude-code dist-tags
npm view @github/copilot dist-tags
else
echo "No npm command on PATH."
fi
# 2. Claude Code on this machine.
if command -v claude >/dev/null 2>&1; then
claude --version
else
echo "No claude command on PATH."
fi
# Optional installs, left commented. Pick one channel on purpose.
# Default to the stable pin.
# stable channel, v2.1.311 as of 5:58 AM ET Tue Nov 17 2026:
# npm install -g @anthropic-ai/claude-code@2.1.311
# latest channel, v2.1.326 as of 5:58 AM ET Tue Nov 17 2026, test machine only:
# npm install -g @anthropic-ai/claude-code@2.1.326
# 3. Retired model names and tool rule flags in this project.
# A search for Claude Opus 5 may also list Claude Opus 5.5, the suggested replacement.
grep -l -r -F --exclude-dir=node_modules --exclude-dir=.git "Claude Opus 4.8" .
grep -l -r -F --exclude-dir=node_modules --exclude-dir=.git "Claude Opus 5" .
grep -l -r -F --exclude-dir=node_modules --exclude-dir=.git "GPT-5.6 Terra" .
grep -l -r -e "--allowedTools" -e "--disallowedTools" -e "--tools" --exclude-dir=node_modules --exclude-dir=.git .
echo "Done. Nothing was installed or changed on disk."
If npm shows newer tags than your snapshot, read the release notes before you change versions.
Sources:
- GitHub Copilot models deprecated on Nov 16, 2026 (GitHub Changelog)
- Control where GitHub Copilot customizations come from (GitHub Changelog)
- Claude Code changelog
- Claude Code on npm
- Copilot CLI v1.0.113-1 prerelease
- Codex releases
- Cursor changelog
- Cursor CLI changelog
- GitHub Changelog
Recommended AI prompt
Copy this paragraph into ChatGPT, Claude, Gemini, Grok, or whatever AI you use.
You are my developer tooling lead for Tue Nov 17, 2026. Story 1: GitHub deprecated Claude Opus 4.8, Claude Opus 5 and GPT-5.6 Terra across most Copilot experiences on Nov 16, suggests Claude Opus 5.5, GPT-6.1 Sol or GPT-6 Luna instead, and enables the replacements automatically only where default model enablement is on. Story 2: enterprise admins can use the managed setting strictPluginOnlyCustomization to require that Copilot skills, custom agents, hooks, MCP servers or executable extensions come from plugins or managed settings, paired with strictKnownMarketplaces to limit sources. Story 3: Claude Code v2.1.326 on the latest npm tag warns at startup about incomplete tool rules and now names settings files it could not save. Ask which Copilot plan, admin policies and Claude Code channel my team uses, then give a short checklist for each story, and link the official posts instead of inventing settings, flags or model names.