GitHub Copilot Model Retirements: November 16 Migration Guide

GitHub announced on October 15, 2026 that three models will leave GitHub Copilot on November 16: Claude Opus 4.8, Claude Opus 5 and GPT-5.6 Terra. The change applies across Copilot Chat, inline edits, ask and agent modes, and code completions. Teams that explicitly select these models should plan a migration now, especially where organization policies control which replacement models employees can access. This is a GitHub Copilot availability announcement, not a blanket claim that the underlying models are being retired from every provider or API.

Which Copilot models are retiring?

The annual-plan exception is narrow. GitHub explicitly says Claude Opus 4.8 remains available to individual Copilot subscribers on annual plans so they retain an Opus offering. It does not extend that exception to Claude Opus 5 or GPT-5.6 Terra. Do not assume an organization's annual billing contract qualifies: the announcement names individual subscribers. GitHub also says users do not need to manually remove retiring models after the date; removal happens through the service.

What Business and Enterprise administrators must check

For Copilot Business and Enterprise, GitHub says suggested replacement models are automatically enabled under the default model-enable policy. That default is not universal: an administrator may have turned off the global default or explicitly disabled a particular model. In that case, an organization or enterprise owner needs to review model policies and enable the intended replacement where permitted. The model then appears in the selector in supported Copilot experiences. GitHub's model-policy documentation also explains that enterprise-level enforced settings can override an organization's choices.

A migration checklist before November 16

1. Inventory explicit model selections in Copilot Chat, IDE configurations, saved prompts, internal instructions and documented agent workflows. Prioritize the three retiring names.
2. Identify account and plan types. In particular, verify whether a Claude Opus 4.8 user qualifies for the individual annual-subscription exception instead of assuming everyone loses access.
3. Ask a Copilot Business or Enterprise administrator to confirm the intended replacement is permitted under the effective enterprise and organization model policies.
4. Test representative coding tasks on the suggested replacement: multi-file edits, debugging, code review preparation and tool-driven agent steps. Compare correctness and human rework, not just response style.
5. Update internal setup guides, onboarding instructions and any workflow assumptions that depend on a specific model being present in the selector.
6. Run a short pre-deadline pilot, capture exceptions, and communicate the November 16 cutover. Afterward, confirm that team members can select an approved model in their actual Copilot client.

Will the replacement behave the same?

No compatibility guarantee is stated in the announcement. GitHub recommends alternative models, but it does not promise identical answers, tool decisions, cost, latency or output format. Teams should test their own workloads before switching important automated tasks. The announcement also does not establish a universal price or plan entitlement for each alternative. Check the current supported-model and plan documentation rather than inferring availability from the suggested-alternative table alone.

How this differs from earlier Copilot retirements

GitHub has announced other Copilot model changes with different deadlines. A November 16 migration should not be confused with the October 19 removals announced separately for older Gemini, GPT and Grok versions. Treat each dated notice as its own change event and keep a single internal model inventory with the affected surface, deadline, replacement and policy owner. That avoids scattered reminders and prevents a team from interpreting an older retirement notice as the current list.