A person reviews AI models on a laptop, selecting approved options while rejected ones are archived and settings are managed.
GitHub retired three Copilot models on November 16, 2026. They are Claude Opus 4.8, Claude Opus 5 and GPT-5.6 Terra. Teams that hard-coded any of them into settings or workflows now need to change them. Admins who run Copilot Business or Enterprise should check that the replacement models are switched on.

A person reviews AI models on a laptop, selecting approved options while rejected ones are archived and settings are managed. What GitHub retired​

Claude Opus 4.8, Claude Opus 5, and GPT-5.6 Terra were slated for deprecation on November 16, 2026, with Opus 5.5 and GPT-6.1 Sol / GPT-6 Luna as migration targets. GitHub's October 15 notice says the deprecation applies across all Copilot experiences. Those include Copilot Chat, inline edits, ask mode, agent mode and code completions.

That wording still stands: there is no separate November 16 notice changing it to "most," and the third-party write-ups repeating the "all" framing are correct.

Retired modelDateGitHub's suggested alternative
Claude Opus 4.82026-11-16Claude Opus 5.5
Claude Opus 52026-11-16Claude Opus 5.5
GPT-5.6 Terra2026-11-16GPT-6.1 Sol or GPT-6 Luna

These are recommendations. GitHub published no benchmarks or behavior comparisons in these notices. Don't assume a replacement will answer the way the old model did.

The exceptions​

Claude Opus 4.8 and annual plans. GitHub says Opus 4.8 is still available to individual Copilot subscribers on annual plans. The October notice gave the reason: those users keep an Opus offering. The exception covers Opus 4.8 only. It does not cover Opus 5 or GPT-5.6 Terra. Independent coverage reads it as excluding Business and Enterprise customers. That exception does not apply to Copilot Business or Enterprise customers, who should switch to Claude Opus 5.5 instead.

Claude Opus 5 is gone from Copilot. GitHub removed Opus 5 from the model picker, and unlike Opus 4.8 it has no exception: it goes for everyone, including annual-plan individuals. You can't pick Opus 5 for ordinary chats anymore, so treat it as gone. Existing enterprise model policies continue to apply. (Opus 5 does live on as a fallback target inside Anthropic's own Claude Code safeguards, but that is a different product from GitHub Copilot.)

What admins should check​

Under default model enablement, the suggested alternatives are switched on automatically for Copilot Enterprise and Copilot Business. That doesn't happen if an administrator has turned off the global default or explicitly disabled the model. In that case you have to enable the replacements yourself through the model policies in Copilot settings. Once a model is enabled, users see it in the Copilot Chat model selector in supported experiences.

Think of it like retiring a printer driver. The old one disappears on schedule, but staff only keep printing if the replacement is installed and allowed.

A practical checklist:

  • Look for workflows, scripts or agent definitions that name a retired model. One third-party analysis advises updating hard-coded model names where they appear in configuration files, scripts or agent definitions. GitHub's notices don't name the specific fields or files involved, so audit your own setup.
  • Open your organization or enterprise Copilot model policies. Confirm that Claude Opus 5.5 and your chosen GPT-6.1 Sol or GPT-6 Luna are enabled.
  • If the global default is off, enable the replacements deliberately. Don't wait for developers to report a missing option.
  • Pick between Sol and Luna on purpose. GitHub offers both as Terra alternatives, and the notice doesn't say how they differ.
  • If you're an individual on an annual plan, you can keep using Opus 4.8. Monthly-plan users shouldn't assume the same.
  • Enterprise customers with questions can contact their GitHub account manager.

GitHub says no action is needed to remove the deprecated models. It also asks customers to update their workflows and integrations to supported models. Removal is automatic, but moving over is up to you.

Part of a bigger cleanup​

This isn't a one-off. One third-party tracker says GitHub has retired 10 Copilot models since October 2, 2026, with six more planned for December 14. GitHub's own changelog lists a December deprecation notice posted on November 13. That tracker's figures are secondary reporting, so check them against GitHub's changelog. The pattern still matters: model names in Copilot now change often. Teams that pin a specific model in tooling should expect to revisit it regularly.

What we don't know​

GitHub's notices don't report outages, pricing changes or performance differences tied to this retirement. They don't say how many users are affected. They don't describe forced automatic substitution of one model for another.

GitHub's guidance is simple. Move off the retired models and confirm that the replacements are permitted. If your admins have restricted model access, check the policy settings first.


Correction (November 16, 2026): An earlier version of this article said GitHub's November 16 notice had changed the retirement scope to "most" Copilot experiences, and that Claude Opus 5 remained available in Copilot for "runtime refusal fallback." Neither is correct: GitHub's October 15 changelog is the only notice, it still says the deprecation applies across all Copilot experiences, and it says nothing about an Opus 5 fallback. Opus 5 is removed from Copilot for everyone.

 

References

  1. GitHub Copilot models deprecated on November 16, 2026 GitHub Changelog 2026-11-16T20:25:20+00:00
  2. Upcoming deprecation of selected GitHub Copilot models in mid-November - GitHub Changelog github.blog
  3. Organize models ending on November 16, 2026 with GitHub Copilot and their migration destinations dev.classmethod.jp