GitHub announced it will retire six models from its GitHub Copilot development assistance service on December 14, 2026. It advised developers using them to switch to replacements before the deadline. Certain models will remain available to individual annual plan subscribers.
1. Retirement schedule and replacement paths for six models
The November 13 notice says the change covers all GitHub Copilot experiences. These include Copilot Chat, inline edits that modify code in place, ask and agent modes for questions or delegated tasks, and code completions. Models used to write and modify code need review, not just those selected in chat.
GitHub suggested Claude Fable 5.2 as a replacement for Claude Fable 5.
The recommended replacement for Claude Haiku 4.5 is Claude Haiku 5.5.
Users of Gemini 3.8 Flash were offered Gemini 4 Hydrogen as a replacement.
The recommended replacement for Gemini 4 Argon is Gemini 4 Carbon.
Grok 4.7 was suggested as a replacement for Grok 4.6.
A replacement for Kimi K3 will be announced later. Teams using this model need to check subsequent guidance to select a replacement.
2. Individual annual subscribers retain access to certain models
Claude Haiku 4.5 will remain available to individual GitHub Copilot annual plan subscribers. Its December 14 retirement does not apply to these subscribers, so they can keep using it.
Checking both the model name and subscription type is the starting point for deciding what to migrate. Even for the same model, whether migration is required on this schedule depends on eligibility for the individual annual plan exception.
3. Organizations automatically enable replacements based on default settings
For Copilot Enterprise and Copilot Business, recommended replacements are enabled automatically if default model enablement remains on. This excludes cases where administrators disabled the overall default or the specific model.
Organizations that turned off the overall default can enable replacement access through model policies in Copilot settings, which govern models available to the organization. Enabled models appear in the Copilot Chat model picker in supported Copilot experiences. Checking that replacements appear after migration confirms whether users can select them.
4. Check both access settings and migration of actual usage
GitHub advised updating workflows and integrations to supported models before December 14. Administrators can prepare by configuring replacement access, followed by users switching the models used in their existing work.
Automatic enablement saves organizations retaining default settings from having to grant replacement access separately. Users still need to migrate workflows and integrations. Organizations that turned off defaults or disabled models also need to review their policies.
The notice did not compare replacement performance or costs. The recommended list is a starting point for choosing a migration path, while organizations must assess suitability for their actual work.
No separate action is needed to remove existing models after retirement.
GitHub Enterprise customers can contact their account team for help with questions or concerns.
The key is to address both replacement access settings and migration of actual work, starting by checking the retention exception for individual annual subscribers.
