The News, Explained
GitHub announced on October 15, 2026 that it will retire Claude Opus 4.8, Claude Opus 5 and GPT-5.6 Terra from Copilot on November 16. A model is the AI selected to produce Copilot responses or code suggestions. The notice includes an exception keeping Opus 4.8 available to individual annual-plan subscribers. Source
The announced scope covers all Copilot experiences, including conversational Copilot Chat, inline edits that modify code in place, ask mode for questions, agent mode for carrying out tasks, and code completions. Comparing the model a feature uses with the listed names helps establish whether this transition applies. Source
GitHub provides the following model mapping. Each listed retirement date is November 16, 2026, and the alternatives are GitHub’s recommended choices. Source
| Model scheduled to retire | GitHub’s suggested alternative |
|---|---|
| Claude Opus 4.8 — individual annual-plan exception | Claude Opus 5.5 |
| Claude Opus 5 | Claude Opus 5.5 |
| GPT-5.6 Terra | GPT-6.1 Sol or GPT-6 Luna |
The exception covers individuals subscribing to GitHub Copilot on annual plans. They retain access to Claude Opus 4.8 so that they keep an Opus offering. The model and subscription type attached to this exception are specifically Opus 4.8 and an individual annual subscription. Both conditions belong together when deciding which row applies to an account. Source
Organization accounts also have an access-policy question. For Copilot Business and Enterprise, the recommended alternatives are automatically enabled under default model enablement, unless an administrator has turned off the global default or explicitly disabled the model. Organizations with the global default off can enable access through model policies in Copilot settings. A model policy is an administrator’s rule determining which models the organization can use. Once enabled, the model appears in the Chat model selector in supported Copilot experiences. Source
GitHub asks users to update workflows and integrations to supported models before the retirement date. For a workflow naming a particular model, that means considering the mapping alongside the organization’s access policy. The notice also says users need take no separate action to remove models after retirement. Source
OYOPICK’s Take
Reading the transition as two questions is useful: which model does a workflow name, and does the organization allow its alternative? Keeping default model enablement on could reduce the work of making alternatives accessible. Where an administrator has restricted access, the user planning a model change and the policy owner need a shared view of the available choice.
The Opus 4.8 exception for individual annual subscribers also deserves prominence. Emphasizing only the retirement names and date could lead those subscribers to expect their model to disappear too. We hope future notices continue to place subscription-specific exceptions and administrator conditions directly alongside model schedules. Conditions that are easy to identify should make it easier to plan when model choices change.