GitHub Copilot Retires 4 Models on Oct 2, 2026: List, Replacements, Admin Fix

GitHub published a bluntly titled changelog entry on September 3, 2026: Upcoming deprecation of selected GitHub Copilot models. Four models leave Copilot on October 2, 2026.

If you habitually pin a specific model in Copilot, this one is worth two minutes — because one of the four is Claude Opus 4.7.

Last verified: 2026-09-04

1. The list and the official replacements

All four on the same date. No staggered rollout.

2. The scope is “everywhere,” not just chat

The announcement states the deprecation applies across all GitHub Copilot experiences — Copilot Chat, inline edits, ask and agent modes, and code completion.

So there is no surface you can retreat to. After October 2 these four are simply not selectable.

3. Individual users: you barely have to do anything

One line in the announcement matters most for ordinary users: no action is required to remove these models after deprecation. They disappear from the picker on their own.

Only two situations need attention:

1. Anything that hard-codes a model name — CI workflows, custom agent configs, scripts with a string like claude-opus-4.7 in them. GitHub explicitly asks you to update workflows and integrations before October 2. This is the part that actually breaks.
2. Work in flight where output consistency matters. Switching models is like switching handwriting. Better to move to Opus 5 or Kimi K3 now, on your own schedule, than to be moved on October 2.

4. Enterprise and Business admins: skip this and your team loses models

The announcement calls out administrators directly: Enterprise and Business admins must enable the replacement models through model policies in Copilot settings.

This is where it usually goes wrong. Model policies do not necessarily auto-approve newly released models, so the failure mode looks like this: the old model vanishes on October 2, the new one is blocked by policy, and developers open Copilot to find their picker noticeably emptier — then they file tickets with you.

Do this now: open Copilot settings and confirm Gemini 3.8 Flash, Kimi K3 and Claude Opus 5 are all allowed. It takes five minutes today and blocks the whole team if left until the morning of October 2.

GitHub adds that enterprise customers with questions are encouraged to contact their account team.

5. Note the timing: Gemini 3.8 Flash shipped the same day

The same day’s changelog also announced Gemini 3.8 Flash becoming available in GitHub Copilot. So this is a paired move: the replacement lands first, the older versions go a month later.

That cadence is the real story. The overlap between “new model available” and “old model gone” is about one month. If your organization has a rule that a model must be evaluated for a quarter before entering production workflows, that rule no longer fits the release cycle — in practice you follow the vendor’s replacement mapping and report problems afterward.

6. Should you switch today?

• On Gemini 3.5 / 3.6 Flash: move to 3.8 Flash, exactly as GitHub recommends. We compared whether the same-price upgrade is worth it separately.
• On Claude Opus 4.7: move to Opus 5. Premium models typically carry a higher request multiplier in Copilot, so watch your usage burn rate for a few days after switching.
• On Kimi K2.7 Code: move to Kimi K3.

Related

• Copilot model request multipliers, verified
• Gemini 3.8 Flash at the same price: worth switching?
• GitHub Copilot free vs paid
• GitHub Copilot tool page

Sources

• GitHub Changelog: Upcoming deprecation of selected GitHub Copilot models (2026-09-03)
• GitHub Changelog: Gemini 3.8 Flash is now available in GitHub Copilot (2026-09-03)

Independent reporting on an official announcement, not sponsored.