GitHub Copilot deprecates four models on 2 October 2026: update pinned workflows and Enterprise model policies

GitHub Copilot deprecates four models on 2 October 2026: update pinned workflows and Enterprise model policies

2 October 2026 — GitHub announced on 2 October 2026 that it has deprecated four models in GitHub Copilot, with the deprecation taking effect the same day. The change applies across all Copilot experiences: Copilot Chat, inline edits, ask and agent modes, and code completions. Teams that chose one of these models by name, in an editor setting, an automation or an integration, need to move to a supported model, and Copilot Enterprise administrators may need to switch the replacements on before users can see them.

Not yet independently verified. Only GitHub's own changelog has been read; no independent report of these deprecations had been found at 2026-10-04. We will update this when it can be confirmed, and remove this note.

Which models are affected

GitHub's changelog lists each deprecated model with a suggested alternative:

Deprecated model	Deprecation date	Suggested alternative
Gemini 3.5 Flash	2026-10-02	Gemini 3.8 Flash
Gemini 3.6 Flash	2026-10-02	Gemini 3.8 Flash
Kimi K2.7 Code	2026-10-02	Kimi K3
Claude Opus 4.7	2026-10-02	Claude Opus 5.5

Because the deprecation date is the same as the announcement date, there was no notice period. Anything still pointing at one of these models should be treated as already broken or about to break.

What GitHub asks customers to do

GitHub asks customers to update their workflows and integrations to use supported models. For organisations on Copilot Enterprise, it adds that administrators may need to enable access to the alternative models through the model policies in Copilot settings. Until a replacement is enabled there, it will not appear in the model picker in editors or on github.com, so a developer whose old model disappears may find no direct replacement offered.

What to do

1. Administrators: open the Copilot settings for your enterprise or organisation, check the model policies, and enable the suggested alternatives you are willing to allow. Review whether the replacement models are covered by the same data-handling terms your organisation approved for the old ones, since several come from different model providers.
2. Platform and DevOps teams: search repository configuration, editor settings files and automation scripts for the deprecated model names, and replace them.
3. Developers: if a model you used has vanished from the picker, pick a supported one and tell your administrator if the suggested alternative is missing.
4. Procurement and security: note the absence of a notice period. If model choice matters to your compliance case, ask how much warning GitHub gives before retiring a model and whether that is written into your agreement.

Why it matters for buyers

AI coding assistants now let customers choose among many models, and the list changes often. Each change can affect output quality, cost under usage-based plans, and which third-party provider processes your code. When evaluating an assistant, check how deprecations are announced, whether there is a notice period, and whether administrators control which replacement models are switched on, rather than finding out when a model disappears.

Sources

• GitHub changelog: Selected models in GitHub Copilot deprecated — 2 October 2026