On November 16, 2026, three AI models disappear from GitHub Copilot — and if your workflows are pinned to Claude Opus 5 or GPT-5.6 Terra, they stop working overnight. The GitHub Copilot models lineup is about to shrink: GitHub’s official changelog, published October 15, names the exact models being retired, the date they go away, and the replacements you should move to.
What GitHub announced
Per the official GitHub changelog (October 15, 2026), GitHub deprecates three models across all Copilot experiences — Chat, inline edits, ask and agent modes, and completions. The schedule:
*One exception: Claude Opus 4.8 remains available to individual GitHub Copilot subscribers on annual plans, so they retain an Opus offering. The changelog states the deprecation does not apply to those customers.
The automatic replacements
Most teams barely have to lift a finger. Under default model enablement, the suggested alternatives are automatically enabled for Copilot Enterprise and Copilot Business customers — unless an administrator turned off the global default or explicitly disabled the model. In that case, admins can re-enable the alternatives through their model policies in Copilot settings.
Once enabled, users see the replacement in the Copilot Chat model selector, and GitHub notes that no action is required to remove the models after deprecation. But scripts, CI pipelines, and custom agents pinned to the old names will not repoint themselves. That part is on you.
What this really means: a Copilot decision, not a model shutdown
Read carefully and you will notice something: this is a GitHub Copilot decision, not a model shutdown. The announcement says nothing about Anthropic or OpenAI retiring these models from their own platforms. They are simply leaving the Copilot lineup — GitHub is steering users toward the newest flagships, which keeps the supported-model surface smaller and better maintained.
Two consequences: your direct API usage is unaffected — this changelog changes nothing for provider-API calls in your own apps. GitHub’s documentation on changing the AI model for Copilot Chat shows how the model selector and Manage Models option work — worth reviewing now.
Your migration checklist before November 16
A broken agent workflow on November 17 means a missed deadline and an awkward client call. Run this five-step checklist now — under an hour for most setups:
- Grep for hardcoded model names. Search repositories, CI configs, custom agent definitions, and
.vscodesettings for the retiring model names. - Switch to the official replacements: Claude Opus 5.5 for either Opus model, GPT-6.1 Sol or GPT-6 Luna for GPT-5.6 Terra.
- Retest agent workflows end-to-end. Prompts tuned for one model can behave differently on another. Verify outputs on the replacements before the deadline.
- Check admin model policies. For Copilot Business and Enterprise teams, confirm the replacements are enabled in Copilot settings — especially if the global default was ever disabled.
- Update docs and runbooks. Team wikis, onboarding guides, and client handover docs should point at the replacements now, not after someone hits an error.
How freelancers turn this into paid work
Every model retirement creates the same market: teams are busy, migrations are tedious. The playbook:
- Sell a “November 16 readiness check.” Scan a client’s repos and workflows for retiring model references, swap in the official replacements, and retest. The deadline does your selling for you.
- Retune agent-mode prompts. Opus 5 to 5.5 and Terra to GPT-6.1 Sol/Luna are upgrades, but behavior shifts happen. Clients pay for verified workflows after the switch.
- Offer ongoing policy management. For Business and Enterprise clients, managing model policies and defaults is recurring work. One migration becomes a monthly retainer.
Model lineups rotate every few months — build the process once, resell it every cycle.
The November 16 migration flow
Do steps 1-4 before November 16 and the retirement is a non-event. Skip them and you learn about it from a client’s error report.
Watch: how Copilot picks the right model for each task
In this official GitHub Checkout episode, the GitHub team breaks down Project HydraFusion — multi-model orchestration that routes prompts through single, cascade, or critique patterns, compared with Copilot’s Auto Model Select:
Frequently asked questions
Which models is GitHub removing from Copilot?
Claude Opus 4.8, Claude Opus 5, and GPT-5.6 Terra — across Chat, inline edits, ask and agent modes, and completions — on November 16, 2026.
What should I use instead?
Official alternatives: Claude Opus 5.5 for both Opus models, GPT-6.1 Sol or GPT-6 Luna for GPT-5.6 Terra. They auto-enable for Business and Enterprise under default model enablement.
I am on an individual annual plan. Do I lose Claude Opus 4.8?
No. The changelog states Claude Opus 4.8 remains available to individual Copilot subscribers on annual plans, so they retain an Opus offering.
Are Anthropic and OpenAI shutting these models down too?
This is a GitHub Copilot decision only. Nothing in the announcement indicates the providers are retiring the models from their own platforms — they are simply leaving the Copilot lineup.
What happens if I do nothing?
The models are removed automatically. But any workflow pinned to the old model names stops working, so update references before November 16.
How do admins re-enable the replacements?
Admins can enable the alternatives through the model policies in Copilot settings, per the changelog.
Keep Reading
Official sources: the GitHub changelog and GitHub Docs on changing the Copilot model. Video from the official GitHub YouTube channel.