Skepra / Web recovery & resilience

Your Copilot Model Migration Needs a Rehearsal, Not a New Dropdown

A client-facing Copilot workflow points to a model that is no longer generally available.

Discuss the next maintenance decision

GitHub announced that Claude Opus 4.8, Claude Opus 5 and GPT-5.6 Terra were deprecated across most Copilot experiences on November 16, 2026. GitHub lists Claude Opus 5.5, GPT-6.1 Sol and GPT-6 Luna as suggested alternatives. Individual annual subscribers retain a stated Claude Opus 4.8 exception, and enterprise policies can change which alternatives are enabled. This is a workflow migration event, not proof that a particular repository has failed.

Inventory the real dependency

An agency should record where a client workflow selects a model: Copilot Chat, inline edits, ask mode, agent mode, code completions, repository instructions, organization policy or a human runbook. Capture the old model name, the intended task, the data sensitivity and the person who can approve a change.

Do not search only the repository. A model selection can live in an organization policy or user preference and can therefore affect several repositories at once. Separate the Copilot app, IDE extension and CLI where the client uses more than one surface.

Test the replacement against the work that matters

Create a small comparison set using sanitized tasks from the client workflow:

  • explain a known frontend regression;
  • propose a bounded change to a component;
  • update a test without changing public behavior;
  • review a dependency or security diff;
  • produce a handoff summary with explicit uncertainty.

Record the model, plan or organization policy, prompt class, tool permissions, output review and resulting diff. The goal is not to rank models in the abstract. The goal is to decide whether the replacement preserves the client workflow's review boundary and acceptable output quality.

Decide between migration, policy change and handoff

If the replacement is enabled and passes the acceptance set, update the approved workflow record and communicate the new model boundary. If the model is unavailable because an administrator disabled the default or alternative policy, the next step is an owner decision, not a silent personal override. If results differ materially, keep the old workflow only where GitHub still authorizes it and create a bounded manual review path.

Keep secrets, private source and customer data out of comparison prompts. A model migration should not become an unreviewed data-sharing change.

Applicability and limits

The notice applies to the named Copilot experiences and plan or policy conditions. It does not establish an outage, degraded repository quality or a required model for every user. The handoff artifact is a model inventory, replacement decision, sanitized acceptance results and named rollback or review owner.

Primary source: GitHub Copilot models deprecated on November 16, 2026.