GitHub Copilot model deprecation on 16 November: what to do
GitHub will deprecate Claude Opus 4.8, Claude Opus 5 and GPT-5.6 Terra in Copilot on 16 November 2026. Who is affected, the replacements, and a checklist.
GitHub will deprecate three models across all Copilot experiences on 16 November 2026: Claude Opus 4.8, Claude Opus 5 and GPT-5.6 Terra. The announcement was posted on 15 October, which gives about a month. GitHub suggests Claude Opus 5.5 as the replacement for both Claude models and GPT-6.1 Sol or GPT-6 Luna for GPT-5.6 Terra. One exception: individual subscribers on annual plans keep Claude Opus 4.8.
Updated 21 October 2026: a separate batch of Copilot models was retired on 19 October. The details are in the section below, and the 16 November dates in this post are unchanged.
Everything here is from GitHub's changelog entry on the upcoming deprecation.
The GitHub Copilot model deprecation, model by model
Claude Opus 4.8: deprecated 16 November 2026. Suggested replacement: Claude Opus 5.5. Remains available to individual Copilot subscribers on annual plans.
Claude Opus 5: deprecated 16 November 2026. Suggested replacement: Claude Opus 5.5.
GPT-5.6 Terra: deprecated 16 November 2026. Suggested replacements: GPT-6.1 Sol or GPT-6 Luna.
The deprecation covers every Copilot surface GitHub lists: Copilot Chat, inline edits, ask and agent modes, and code completions.
What happens to you
It depends on who you are.
Individual user. If you pick one of these models from the model selector, it disappears on 16 November, and you pick another. The exception above applies only to annual-plan subscribers, and only to Claude Opus 4.8. GitHub says no action is needed to remove the models after the date.
Copilot Business or Enterprise admin. The suggested replacements are enabled automatically under default model enablement, unless you turned off the global default or explicitly disabled the model. If the global default is off, enable the replacements through model policies in Copilot settings, otherwise your users will lose a model without gaining one. Once enabled, the replacements show up in the Copilot Chat model selector in supported experiences.
Anyone with scripted or documented workflows. GitHub's instruction is to "update your workflows and integrations to use the supported models before this date." If a team wiki, a prompt file or an onboarding doc names one of the three models, now is the time to change it.
A short checklist
List where you name these models: settings, shared prompt files, internal guides.
If you are an admin, check whether default model enablement is on. If not, enable the replacements in model policies.
Pick one real task you do often and run it on the replacement before the date. A different model can behave differently on the same prompt, in length, in style and in how readily it edits files.
Tell your team the date. People who do not read changelogs find out when the model vanishes mid-task.
If a model vanishes and you did not see it coming, why an AI model disappeared from the model picker explains the usual causes, and what to do when an AI model gets deprecated is the general playbook, including how to compare outputs before switching.
Why a month still catches people out
A month sounds generous until you count who reads changelogs. Model changes tend to surface as a surprise: a shared prompt file stops working the way it did, or a teammate asks why their favourite model is missing. The fix is cheap now and annoying later, so the useful move is to put the date in your team's calendar and name one person to check the model policies.
Update: the models retired on 19 October
GitHub retired a different set of models on 19 October 2026, an event first announced on 18 September. According to GitHub's changelog entry, the retirement applies to most Copilot experiences, including Copilot Chat, inline edits, ask and agent modes, and code completions.
Retired on 19 October | Suggested replacement |
|---|---|
Gemini 3.7 Flash | Gemini 3.8 Flash |
GPT-5.5 | GPT-6.1 Sol |
GPT-5.4 | GPT-6.1 Sol |
GPT-5.4 mini | GPT-6 Luna |
GPT-5 mini | GPT-6 Luna |
Grok 4.5 | Grok 4.7 |
The admin guidance matches the November one. Copilot Enterprise administrators may need to enable the replacements through model policies in Copilot settings, and once enabled they appear in the model selector in VS Code and on github.com. GitHub says no action is required to remove the retired models. If a prompt file, script or team guide still names one of them, change it now rather than waiting for the November date.
What the announcement does not say
GitHub's page does not explain why these three models were picked, and it does not describe any change in pricing between the old and new models. It also does not say whether usage cost differs between old and new models, so check the model's entry in Copilot settings before you switch a heavy workflow. Do not assume the replacement costs the same.
If you are weighing whether Copilot is still the right tool for how you work, GitHub Copilot vs Claude Code compares them, and the AI coding tools guide is the wider overview.
How did this land?
About the author

Senior Editor, AI & Product
Cecilia leads the Swarmz editorial desk. She has spent a decade turning complex AI and product topics into writing people actually finish, and she owns the blog's quality bar.


