GitHub Copilot retires three model options in November update

GitHub retired Claude Opus 5 and GPT-5.6 Terra from Copilot and limited Opus 4.8 to eligible annual plans. Here’s what developers should check.

Hands typing on a laptop keyboard
Hands on a laptop keyboard. Representative photo. Shixart1985 / Wikimedia Commons, CC BY 2.0. Cropped and resized.

GitHub has retired three model options in Copilot as part of a scheduled November update. The change announced for Nov. 16 affects Claude Opus 4.8, Claude Opus 5 and GPT-5.6 Terra. GitHub made one exception. Individual Copilot subscribers on annual plans can continue using Claude Opus 4.8, according to the company’s retirement notice, which is now marked retired.

The change reaches across Copilot experiences, including chat, inline edits and completions, and ask and agent modes. The fastest way to work out what applies to you is to check where your choice is made. A person picking a model in an editor has a different job from an administrator approving models for a team or a developer maintaining a workflow that names one directly.

Which models changed and what GitHub suggests

  • Claude Opus 4.8 → Claude Opus 5.5. The retirement has an exception for individual annual-plan subscribers, who retain access to Opus 4.8.
  • Claude Opus 5 → Claude Opus 5.5. GitHub lists Opus 5.5 as its suggested successor for this option too.
  • GPT-5.6 Terra → GPT-6.1 Sol or GPT-6 Luna. GitHub lists two alternatives and leaves the choice to the user or team.

These are Copilot model names and suggested alternatives. For a team, the choice also depends on whether the recommended model is enabled on the account and supported in the Copilot experience people use. Check GitHub’s supported model list for the current plan and feature details. A published product recommendation tells you where to look first. Your own small test tells you how the replacement behaves on the work you actually need done.

Where to check if your model disappeared

If you chose a model in Copilot Chat, start in the model selector in the editor or other Copilot experience where you noticed the change. Confirm which Copilot account you are signed in with. That matters if you use both an individual subscription and a seat provided by an organization. GitHub’s annual-plan exception is specific to eligible individual subscribers and Opus 4.8.

For Copilot Business and Enterprise, GitHub says the suggested alternatives are automatically enabled when the default enablement policy applies. If an administrator turned off the global default or explicitly disabled a model, access may require a policy change. Start by checking the effective organization or enterprise policy. Then confirm that a teammate with an ordinary seat can select the intended replacement in the experience the team uses.

Teams that keep a model name in a configuration or integration should search those settings for the retired names. A model may appear in one editor’s picker and be unavailable to a separate workflow under different permissions. Run a representative request from the place where it normally runs and check the result. GitHub’s notice tells administrators to update integrations. The behavior of any stale reference depends on the integration and should be checked in context.

GitHub’s organization documentation distinguishes a model’s own policy from the default it can inherit. For example, a model delegated to the default policy follows the organization’s broader setting unless a more specific policy applies. Checking both settings can explain why a published replacement is absent from a teammate’s selector. If the team uses more than one Copilot experience, repeat the access check in each one where a specific model matters.

How to compare replacements on a real task

Pick a small task with a known expected result, such as updating a test after a documented interface change. Keep the repository revision and prompt the same. Then check whether the suggested edits compile, whether the tests pass, and whether the scope of the patch matches the request. An internal code review can catch a difference in reasoning that a model’s name or a general benchmark would miss.

For the two alternatives GitHub suggests for Terra, repeat the same exercise for each one. Use the results to choose a default for that workflow and record where a different model is needed. For a managed team, the useful handoff includes the old model, the approved replacement, the policy that grants access and one checked example of the task. Follow Newsmerica’s Tech & AI desk for product changes that affect developer workflows.

Trust & transparency

How we handled this story

Verified

Verified GitHub’s dated retirement notice, its marked Retired state, replacement suggestions, scope and individual annual-plan exception against GitHub Docs.

Grounded in this reporting

Ask Newsmerica

Ask about this article. Answers quote the closest published passages and link back to their sources.

This tool retrieves article passages; it does not add outside facts.

Keep exploring

More from Newsmerica

Leave a Reply

Your email address will not be published. Required fields are marked *