If you write code with GitHub Copilot every day, there is a date you need to put on your calendar right now: 16 November 2026. On that day, GitHub is removing three models from Copilot and moving their users to replacements. If you have never changed a model setting in your life, this will probably pass without you noticing anything. But if you, or your team, pinned a specific model name anywhere — in your editor settings, in a prompt file, in a script, in an automated job — then 16 November is a real deadline, and the work has to be done before it, not after it.
This guide explains exactly which models are going, where each one is moving, who is exempt, and what to check in your own setup. It is written from GitHub’s own changelog dated 15 October 2026, so the mapping below is the official one, not a blogger’s guess. A few write-ups on the internet have already got parts of this story wrong, and this article points out those traps so you do not walk into them.
The Three Models Going Away
GitHub’s changelog announcement is short and specific. On 16 November 2026, three models are deprecated across all GitHub Copilot experiences. The changelog names those experiences as Copilot Chat, inline edits, ask and agent modes, and code completions. Three models leave, and each one has a named replacement:
| Model being removed | Replacement from 16 November 2026 | Any exception? |
|---|---|---|
| Claude Opus 4.8 | Claude Opus 5.5 | Yes — stays for individual subscribers on annual plans only |
| Claude Opus 5 | Claude Opus 5.5 | No |
| GPT-5.6 Terra | GPT-6.1 Sol or GPT-6 Luna | No |
Read that table carefully, because the most common mistake in online coverage is in the middle row. One secondary write-up mapped Claude Opus 5 to GPT-6.1 Sol or GPT-6 Luna. That is wrong. GitHub’s own changelog says Claude Opus 5 moves to Claude Opus 5.5, the same replacement as Claude Opus 4.8. If you read a blog post that tells you otherwise, trust the changelog, not the blog.
The third row is also worth reading twice. GPT-5.6 Terra does not have a single replacement. GitHub lists two: GPT-6.1 Sol or GPT-6 Luna. If your workflow pins GPT-5.6 Terra by name, you need to choose between those two replacements yourself rather than assuming one of them will be picked for you.
What “Deprecated” Means Here
The word “deprecated” can sound dramatic, but in this case it has a narrow, precise meaning, and understanding that meaning saves you from two opposite mistakes: panicking, and ignoring the deadline completely.
First, this is a Copilot-route closure only. It means these models will no longer be offered inside GitHub Copilot after 16 November 2026. It does not mean the models themselves are disappearing from the world. Anthropic’s own deprecation page still lists Claude Opus 5 and Claude Opus 4.8 as active. So if you use those models through some other route, this announcement does not touch that route. The change is about what Copilot offers, nothing wider. Anyone who tells you “Claude Opus 5 is being shut down” without the words “in Copilot” is overstating the story.
Second, GitHub’s own wording is reassuring in one specific way: “No action is required to remove the models after they have been deprecated.” In plain language, you do not have to delete anything, and GitHub will handle the removal itself. The work that falls on you is different: it is updating your workflows and integrations before 16 November, so that nothing in your setup is still pointing at a model name that will stop working in Copilot.
Third, there is a limit to what the changelog says. It lists the Copilot experiences covered, and it uses the word “including” before that list. That wording matters. Copilot CLI and code review are not named in the list, and because the list is introduced with “including”, the scope for those surfaces is ambiguous. This article therefore does not claim that CLI or code review are covered, and it does not claim that they are safe either. If your workflow depends on a model choice inside CLI or code review, check GitHub’s own documentation for those surfaces rather than assuming either way.
Who Is Affected and Who Is Not
The short answer is that most Copilot users will be affected in a small way, and a smaller group needs to take action.
If you are an individual Copilot subscriber on an annual plan and you use Claude Opus 4.8, you are the one exception in this whole story. Claude Opus 4.8 remains available for individual subscribers on annual plans only, even after 16 November 2026. Note how narrow that exception is: it covers one model, one subscriber type, and one billing arrangement. It does not cover monthly individual subscribers, it does not cover Claude Opus 5, and it does not cover GPT-5.6 Terra. If you are on a monthly plan and you use Opus 4.8, the exception does not apply to you.
If you work in a company that uses Copilot Business or Copilot Enterprise, the replacement models are handled by a setting called default model enablement. Under the default setup, the replacements are automatically enabled for you, and the switch should be smooth. There is one catch: if an administrator in your organisation turned off the global default, or explicitly disabled one of the replacement models, then the replacement will not be enabled automatically. In that case the admin must enable it through the model policies in Copilot settings. If you are a developer in such an organisation and your model list suddenly looks short after 16 November, the first person to ask is your Copilot admin, not GitHub support, because the fix is a settings change on your organisation’s side.
If you have never picked a model yourself and you simply use whatever Copilot gives you, you are in the lowest-risk group. Your requests will move to the replacement models through the default setup, and you may notice a different model name in a dropdown and nothing else.
The highest-risk group is developers and teams who pinned model names. That is the group the rest of this guide is really for.
The Checklist: Audit Your Setup Before 16 November
A pinned model name is any place where a specific model, such as “Claude Opus 5” or “GPT-5.6 Terra”, is written down as a fixed choice rather than left to Copilot’s default. Pinned names are common in serious setups, and they are easy to forget about because they sit quietly in files you rarely open. Here is where to look.
Start with your editor settings. In VS Code, open your settings file and search for the names of the three retiring models. A model choice saved in settings will keep asking Copilot for that exact model after 16 November, and that request will either break or be rerouted. Change it to the replacement from the table above, or remove the pin entirely and let the default take over.
Next, check your prompt files and reusable instructions. Many developers keep saved prompts, instruction files, and agent definitions that name a model at the top. Search those files for “Opus 4.8”, “Opus 5”, and “GPT-5.6 Terra” and update every hit. This is the step people most often skip, because prompt files feel like documents, not settings, but to Copilot they are instructions, and a model name inside them counts.
Then check your scripts and automated jobs. If you run Copilot in continuous integration, in a scheduled script, or in any automated pipeline that passes a model name as a parameter, that parameter is a pinned name too. Update it before the deadline, and run the job once afterwards to confirm it still works. An automated job that fails silently is worse than a failure you see on screen, because it can sit broken for weeks before anyone notices.
Finally, check shared team resources: team wikis, onboarding documents, and template repositories that tell new joiners which model to select. A new developer who joins your team on 20 November and follows an outdated onboarding page will set up a broken configuration on day one. Updating the document takes two minutes and saves a confused afternoon.
For Pakistani developers and freelancers, this audit matters just as much as it does anywhere else. Many Pakistani developers work for overseas clients on fixed contracts, and a broken coding setup on a deadline day is a professional problem, not just a technical one. Freelancers who bill by the hour cannot afford to spend a morning debugging a model error that a ten-minute audit in early November would have prevented. Do the audit now, while the deadline is still weeks away, and note the date in your calendar: 16 November 2026.
Mistakes to Avoid
Four mistakes are already circulating in coverage of this change, and each one is easy to make.
The first is the wrong mapping. As noted above, Claude Opus 5 moves to Claude Opus 5.5, not to GPT-6.1 Sol or GPT-6 Luna. If you update your settings using a blog post that gives the wrong mapping, you will have configured the wrong replacement. Always check the mapping against GitHub’s changelog.
The second is trusting prices you read in blog posts. GitHub’s changelog announcement gives no prices at all. Some third-party blogs have quoted token prices for the replacement models, but those figures are not from GitHub’s changelog, and they must not be treated as GitHub’s prices. This article deliberately prints no token prices and no rupee price for Copilot, because no verified Copilot price for these replacements was found in GitHub’s own announcement. If a blog quotes you a price and calls it GitHub’s price, check whether GitHub actually published it. In this case, GitHub did not.
The third is assuming the change is wider than it is. This is not a shutdown of the models themselves. Anthropic still lists Opus 5 and Opus 4.8 as active on its own pages. The change is only about Copilot’s offering. Do not cancel other tools, rewrite unrelated integrations, or warn clients about a model disappearing when the only thing changing is its availability inside Copilot.
The fourth is assuming the change is narrower than it is. The changelog list uses the word “including”, and Copilot CLI and code review are not named. That does not mean those surfaces are unaffected; it means the changelog does not settle the question. Do not tell your team “CLI is safe” or “code review is safe” on the basis of this announcement, because the announcement does not say that.
What Happens After 16 November
After the date passes, the retiring models stop being offered in Copilot, and GitHub handles the removal itself, so there is nothing to uninstall or delete. If you did the audit, your setup will already be pointing at the replacements, and your work continues normally. If you did not do the audit, the likely outcomes are that a pinned request fails with an error, or it is rerouted to a different model than the one you chose. Neither outcome damages your code, but both cost time and cause confusion, especially in automated jobs where the failure may not be visible immediately.
One more practical point: if you are an admin for a Copilot Business or Enterprise organisation, check your model policies before the deadline, not after it. If your organisation turned off the global default or explicitly disabled a replacement model, your developers will hit a wall on 16 November that only you can remove, by enabling the replacement in Copilot settings. A five-minute settings check in early November prevents a flood of support messages later.
The broader lesson here is a simple one for anyone who builds on a platform’s model menu: model menus change. Names retire, replacements arrive, and the developers who survive these changes painlessly are the ones who treat model names as configuration that needs a periodic review, not as permanent facts. Put a recurring reminder in your calendar to review pinned model names every few months. The next retirement will not announce itself in your editor; it will arrive as a changelog post, exactly like this one, and the developers who read those posts early are the ones who never lose a morning to a broken setting.
GitHub announced the removals in the GitHub Changelog on 15 October 2026, and this article’s mapping, exception and scope details follow that announcement.
Also read: Gemini 4 Argon (October 2026): Google’s New Frontier Model at $2/$10 — and Why Pakistani Developers Should Test It Before 1 December and Google Gemini Free Plan Changed: You Now Get Flash-Lite Only
FAQs
Which GitHub Copilot models are being removed on 16 November 2026?
Three models are being removed from Copilot on 16 November 2026: Claude Opus 4.8, Claude Opus 5, and GPT-5.6 Terra. Claude Opus 4.8 and Claude Opus 5 both move to Claude Opus 5.5, while GPT-5.6 Terra moves to GPT-6.1 Sol or GPT-6 Luna. The announcement comes from GitHub’s changelog dated 15 October 2026.
Does the removal mean Claude Opus 5 and Opus 4.8 are shutting down completely?
No. This is a Copilot-route closure only. Anthropic’s own deprecation page still lists Claude Opus 5 and Claude Opus 4.8 as active. The change means these models will no longer be offered inside GitHub Copilot after 16 November 2026. It does not mean the models disappear from every other route where they are offered.
I am an individual Copilot subscriber on an annual plan using Claude Opus 4.8. Do I need to change anything?
No, you are the one exception. Claude Opus 4.8 remains available for individual Copilot subscribers on annual plans only, even after 16 November 2026. The exception does not cover monthly individual subscribers, and it does not cover Claude Opus 5 or GPT-5.6 Terra, so if you use either of those two, you still need to switch to the replacement.
What should I check in my setup before 16 November 2026?
Search for the three retiring model names in your VS Code settings, your saved prompt and instruction files, your scripts and automated jobs, and your team’s onboarding documents or templates. Update every pinned name to its replacement from GitHub’s changelog, or remove the pin and let Copilot’s default take over. If you are a Copilot Business or Enterprise admin who turned off the global default or disabled a replacement model, enable the replacement through the model policies in Copilot settings before the deadline.