Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Copilot retires six more models on December 14

Written November 14, 2026

GitHub's December wave retires Fable 5, Haiku 4.5, Gemini 3.8 Flash, Gemini 4 Argon, Grok 4.6 and Kimi K3. The replacements named, and the one not named.

What is retiring

GitHub will deprecate six more models across all Copilot experiences on December 14, 2026. The retirement covers Copilot Chat, inline edits, ask and agent modes, and code completions. This is the next wave after the November 16 retirements, and it catches some models that were themselves recent landing spots: if you re-pinned to Gemini 3.8 Flash, Grok 4.6, or Kimi K3 during the autumn waves, those pins now have an end date too. GitHub's table, with the alternative it suggests for each model, is:

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

Five of the six rows name a replacement. One does not, and one carries a carve-out. Both deserve a closer look before you plan around the table.

The carve-out and the missing replacement

The asterisk belongs to Claude Haiku 4.5. GitHub says Haiku 4.5 will remain available to individual Copilot subscribers on annual plans, and the deprecation does not apply to those customers. Everyone else on Haiku 4.5 moves to Haiku 5.5, the suggested alternative. Kimi K3 is the open row: its suggested alternative is listed as to be announced, so a workflow pinned to Kimi K3 has no named destination yet. If that is your setup, the practical move is to pick an interim model yourself before December 14 rather than wait for GitHub's announcement to arrive close to the date.

How the replacements get enabled

Under what GitHub calls default model enablement, the suggested alternatives are automatically enabled for Copilot Business and Copilot Enterprise customers, unless an administrator has turned off the global default or explicitly disabled the model. If your organization turned the global default off, an admin can enable each alternative through its model policy in Copilot settings. Once a model is enabled, users see it in the Copilot Chat model selector in supported Copilot experiences. GitHub also says no action is required to remove the retiring models after they are deprecated; they go away on their own. Enterprise customers with questions are directed to their account team.

Where the current list lives

GitHub closes the announcement by pointing to its documentation on supported models for the models available in Copilot. That documentation, rather than any single announcement, is the list to work from once December 14 passes, because it is the page GitHub maintains as models arrive and leave. If your team keeps its own internal list of approved models, this wave is the prompt to update it in both directions: six names out, five named alternatives in, and one row, Kimi K3, left open until GitHub announces its replacement.

What to do

Work through your pins, defaults, and workflow files for the six names before December 14, and move each one to its suggested alternative, or to a model you prefer, while you can still compare behaviour side by side. GitHub's own advice in the announcement is to update workflows and integrations to use the supported models before the date. Admins who manage model policies should confirm the alternatives are enabled, especially where the global default is off. Handle the November 16 wave first if it still affects you; the re-pinning guide linked below covers that earlier date. December 14 is a month out, which is enough time to test a replacement properly and too little time to leave it to the final week.

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Re-pin Copilot models before retirements · Run Gemini 4 Hydrogen from the Copilot picker