GitHub will retire six AI models from Copilot on 14 December 2026, including Gemini 3.8 Flash and Grok 4.6. The change applies across chat, inline edits, ask and agent modes, and code completions.

The company set out the schedule in a GitHub Changelog post published on 13 November 2026. Each of the six models carries the same deprecation date, listed in the changelog table as 2026-12-14.

Six models leave every Copilot surface on the same day

GitHub said it will deprecate the models “across all GitHub Copilot experiences (including Copilot Chat, inline edits, ask and agent modes, and code completions) on December 14, 2026.”

That phrasing matters for teams that use Copilot in more than one place. A model removed from the chat selector is also removed from inline edits and from code completions on the same date. Copilot Chat, ask mode and agent mode are covered by the same line.

The affected models are Claude Fable 5, Claude Haiku 4.5, Gemini 3.8 Flash, Gemini 4 Argon, Grok 4.6, and Kimi K3. The changelog does not give a reason for selecting these six.

GitHub said users should “update your workflows and integrations to use the supported models before this date.” Scripts, agents, extensions, and automation that name a retiring model by string fall under that instruction.

Because the deprecation covers code completions as well as chat, the same instruction reaches editor configurations and any tooling that pins a model for inline edits or agent runs.

Nothing in the post indicates a change to pricing, seat counts, or plan structure. It is a model list change, announced about a month ahead of the cutoff.

The replacement table, with one exception and one entry still to be announced

GitHub published a suggested alternative for five of the six models. The sixth, Kimi K3, is listed as “To be announced.”

ModelDeprecation dateSuggested alternative
Claude Fable 52026-12-14Claude Fable 5.2
Claude Haiku 4.5*2026-12-14Claude Haiku 5.5
Gemini 3.8 Flash2026-12-14Gemini 4 Hydrogen
Gemini 4 Argon2026-12-14Gemini 4 Carbon
Grok 4.62026-12-14Grok 4.7
Kimi K32026-12-14To be announced
*Claude Haiku 4.5 will remain available to individual GitHub Copilot subscribers on annual plans.

The asterisk on Claude Haiku 4.5 points to a carve-out. GitHub said the model “will remain available to individual GitHub Copilot subscribers on annual plans. The deprecation of Claude Haiku 4.5 does not apply to these customers.”

So Haiku 4.5 is not disappearing for everyone on 14 December. Individual subscribers on annual billing keep access, while other customers are pointed toward Claude Haiku 5.5 as the suggested alternative.

The exception is specific to that one model. The other five entries in the changelog table carry no footnote of that kind, and all six share the 2026-12-14 date.

Teams standardized on Kimi K3 have no named successor in the table. The changelog does not say when a replacement will be named, and the entry reads “To be announced.” The deprecation date for Kimi K3 is unaffected by that gap.

The other four pairings are the alternatives GitHub suggests: Fable 5 to Fable 5.2, Gemini 3.8 Flash to Gemini 4 Hydrogen, Gemini 4 Argon to Gemini 4 Carbon, and Grok 4.6 to Grok 4.7.

What administrators and individual users need to check

For organizations, the key detail sits under default model enablement. GitHub said the suggested alternatives are automatically enabled for Copilot Enterprise and Copilot Business customers, with two conditions attached.

The automatic enablement does not apply if an administrator has turned off the global default or has explicitly disabled the model in question. In those cases, the replacement will not appear on its own.

GitHub said that if the global default is off, administrators “can enable access to the alternative models through their model policies in Copilot settings.” That path runs through model policies inside Copilot settings rather than a single global switch, and it is applied per model.

Once a model is enabled, GitHub said, “users will see the model in the Copilot Chat model selector in supported GitHub Copilot experiences.” The selector is where a developer can confirm what an account currently has available.

Individual users do not set that policy themselves. Where an organization manages Copilot, access to the suggested alternatives follows the model policies administrators configure in Copilot settings.

There is no cleanup task on the user side. GitHub said that “no action is required to remove the models after they have been deprecated.”

The work before 14 December, as set out in the changelog, is to update workflows and integrations to supported models, confirm policy settings for the five named alternatives, and plan around the Kimi K3 entry that has yet to be filled in.

GitHub Enterprise customers with questions or concerns are encouraged to contact their account team for assistance, according to the changelog. The post also points readers to GitHub’s documentation on supported models and invites feedback in the GitHub Community.

For related reading on another assistant, Make Tech Easier’s earlier coverage looks at Cursor as an AI coding assistant, and at a separate roundup of ChatGPT alternative chatbots.

Until GitHub names a successor, Kimi K3 is the one entry on the list with no path forward published. Every other retiring model has a replacement already identified in the table.