The table, read closely

The useful detail in GitHub's short post is not the date. It is the unevenness of the exits.

Kimi K3 leaves with no successor named. A team routing work to Kimi K3 through Copilot has a deadline but, as of the November 13 announcement, no suggested alternative named in it. Every other model on the list at least tells its users where GitHub expects them to land.

The Haiku 4.5 line carries the only footnote in the table, and it changes who the deadline applies to. Individual subscribers on annual plans keep Haiku 4.5; everyone else loses it on December 14. Two users on the same product can therefore see different model pickers after the same date.

The replacements also deserve a skeptical read. A suggested alternative is GitHub's mapping, not a promise of equivalent behavior. Fable 5 users are pointed at Fable 5.2, Argon users at Carbon, Flash users at Hydrogen. Whether those swaps hold up on a team's own prompts, completion acceptance or agent traces is a test each team has to run itself, and December 14 does not move while they run it.

What admins actually have to do

GitHub's wording is reassuring in one direction and conditional in the other. Nothing needs to be done to remove the old models; they simply stop being selectable. The replacements are the conditional part. For Copilot Business and Enterprise, the suggested alternatives are enabled automatically only under default model enablement. An administrator who turned off the global default, or disabled a specific model earlier, has to enable the replacements through model policies in Copilot settings, as GitHub's post describes.

GitHub directs Enterprise customers with questions to their account team. It does not, in this post, discuss pricing differences between retiring models and their replacements, so any cost claim about the swaps would need GitHub's separate pricing documentation before it belongs in print.

The practical move

Treat the model name as a dependency with an expiration date, because that is what it now is. Search internal docs, extension settings and agent configurations for the six names. Move the pinned ones to the suggested alternatives early enough to compare outputs on real work, and give Kimi K3 workflows a contingency, since GitHub has not yet said what replaces them. The announcement provides about a month for preparation, but only for teams that start before the picker changes on its own.

Sources

  1. [1] GitHub Changelog, "Upcoming deprecation of selected GitHub Copilot models in December" (November 13, 2026)Read source