On November 16, 2026, three GitHub Copilot models stop working — and if your team has any pinned in an IDE picker, a CLI script, or an agent-mode workflow, it breaks overnight. GitHub gave 32 days’ notice in GitHub’s official changelog announcement on October 15.
For teams that bill by the hour, that’s a cost event, not a footnote. Here’s what disappears, what replaces it, the one exception, and how to profit from the migration.
What GitHub is removing: the official deprecation table
Straight from the changelog — the models leaving all Copilot experiences on November 16, 2026:
| Model | Deprecation date | Suggested alternative | Exception |
|---|---|---|---|
| Claude Opus 4.8 | 2026-11-16 | Claude Opus 5.5 | Stays available for individual subscribers on annual plans |
| Claude Opus 5 | 2026-11-16 | Claude Opus 5.5 | No exception |
| GPT-5.6 Terra | 2026-11-16 | GPT-6.1 Sol or GPT-6 Luna | No exception |
The headline numbers:
- 3 models deprecated in a single cut on November 16, 2026
- 5 Copilot surfaces affected — Chat, inline edits, ask/agent modes, completions
- 1 exception — Claude Opus 4.8 survives only for individual subscribers on annual plans
- 32 days between the October 15 announcement and the cutoff
- Third deprecation wave since October 2, 2026 — 10 Copilot models retired in total, per pondero.ai’s tracking
Two key changelog quotes: “No action is required to remove the models after they have been deprecated.” The models vanish on their own — your workflows don’t migrate themselves. Under default model enablement, replacements auto-enable — unless an admin turned off the global default.
That “unless” is where the money leaks.
The money problem: what this deadline really costs
A model deprecation is a hidden invoice: failed agent runs, downgraded completions, hours nobody budgeted.
1. Pinned model configs are ticking time bombs
Search your stack now for any pinned reference to the retiring models:
- IDE model pickers — VS Code/JetBrains/Neovim setups where Opus 5 is still the default chat model
- Agent-mode instructions — custom agents that hardcode a retiring model name
- Copilot CLI scripts — automation, scaffolding, and PR-review scripts that pass a model flag
- CI and docs automation — release-note generators and code-review bots built on Copilot
On November 16, each either silently falls back or fails loudly mid-run. An agent-mode workflow that dies halfway through a client task is billable time you can’t invoice — and trust damage you can’t undo.
2. The Business/Enterprise admin gotcha
The changelog buries the trap in one sentence: replacements are auto-enabled for Business and Enterprise — unless an admin turned off the global default or explicitly disabled the model. Locked-down orgs wake up on November 16 with:
- Old models gone
- Replacements blocked by policy
- A helpdesk queue full of “Copilot is broken”
Admins: re-enable alternatives via model policies in Copilot settings. Developers in locked-down orgs: ping your admin this week — not on the 16th.
3. Freelancers and agencies: protect client workflows
A retainer client whose flow depends on GPT-5.6 Terra doesn’t care whose fault it is — they care that their pipeline broke. Audit every client project now and bill the migration as maintenance work.
The Copilot migration flow: 5 steps before Nov 16
1
AUDIT
Find every pinned model
2
ENABLE
Unblock alternatives in model policies
3
TEST
Run agent flows on new models
4
MIGRATE
Swap pins, docs, CI defaults
5
HEDGE
Keep Opus 5 via vendor API if needed
Order matters: enable before you test, test before you migrate.
How to profit from the GitHub Copilot shake-up
Every deprecation wave is a consulting opportunity:
- Sell a “Copilot migration audit” as a fixed-price service. Scan a client’s repos, IDE configs, prompts, and CLI scripts for pinned retiring-model references; deliver exact swap instructions.
- Productize the admin enablement check. Verify model policies auto-enable the alternatives for Business and Enterprise orgs — a one-hour checklist sold to IT leads.
- Offer Opus 5 continuity packages. Teams whose prompts are tuned to Claude Opus 5 face re-tuning costs. Sell them the API-escape-hatch setup (below) so critical flows keep running unchanged.
- Publish the benchmark yourself. Benchmark the replacements on your standard tasks before the cutoff and publish — pre-deadline content earns the links.
The escape hatch: Opus 5 isn’t dying everywhere
The deprecation applies to Copilot only — the models live on in vendor APIs. A DEV Community analysis notes Anthropic lists claude-opus-5 as active until at least July 24, 2027, and claude-opus-4-8 until at least May 28, 2027. So:
- Claude Opus 5 stays on Anthropic’s API until at least July 2027 — eight months of runway after Copilot drops it
- Claude Opus 4.8 likewise stays on Anthropic’s API until at least May 2027 — plus the Copilot annual-plan exception
If a workflow is genuinely Opus-5-specific — tuned prompts, calibrated evals — route just that one through Anthropic’s API directly. Copilot for everything else. That’s the professional hedge.
Frequently asked questions
Which GitHub Copilot models are being deprecated?
Claude Opus 4.8, Claude Opus 5, and GPT-5.6 Terra — across Copilot Chat, inline edits, ask/agent modes, and completions, per GitHub’s Oct 15, 2026 changelog.
When does the Copilot model deprecation take effect?
November 16, 2026 — 32 days after GitHub’s October 15 announcement.
What should I switch to instead?
Claude Opus 5.5 replaces both Opus models; GPT-6.1 Sol or GPT-6 Luna replaces GPT-5.6 Terra — GitHub’s suggested alternatives.
Am I affected if I use Claude Opus 4.8 on an annual individual plan?
No — individual subscribers on annual plans keep Opus 4.8. Business and Enterprise seats lose it on November 16.
Do I need to manually remove the deprecated models?
No — GitHub handles removal automatically. But you must point your pinned configs at the alternatives yourself.
Will the replacement models be enabled automatically?
Under default model enablement, yes for Business and Enterprise — unless an admin turned off the global default. Admins must re-enable alternatives via model policies in Copilot settings.
Can I still use Claude Opus 5 after November 16?
Not inside Copilot. Anthropic’s API lists claude-opus-5 as active until at least July 24, 2027 — route critical workflows through it.