Upcoming deprecation of MAI-Code-1-Flash
GitHub will deprecate the MAI-Code-1-Flash model across all GitHub Copilot experiences on September 10, 2026, with MAI-Code-1.1-Flash as the suggested alternative. Users should update their workflows accordingly.
With the launch of MAI-Code-1.1-Flash, we will deprecate MAI-Code-1-Flash across all GitHub Copilot experiences on September 10, 2026:
| Model | Deprecation date | Suggested alternative |
|---|---|---|
| MAI-Code-1-Flash | 9-10-2026 | MAI-Code-1.1-Flash |
Please update your workflows and integrations to use the new model before September 10. Copilot Enterprise administrators may need to enable access to the alternative model through their model policies in Copilot settings. As an administrator, you can verify availability by checking your individual Copilot settings and confirming that the policy is enabled for the specific model. Once enabled, you’ll see the model in the Copilot Chat model selector in VS Code and on github.com. No action is required to remove the older model once it has been deprecated.
GitHub Enterprise customers with questions or concerns are encouraged to reach out to their account manager for further assistance.
Share your feedback
To learn more about the models available in Copilot, see our documentation on models and get started with Copilot today.
Join the GitHub Community to share your feedback.
The post Upcoming deprecation of MAI-Code-1-Flash appeared first on The GitHub Blog.
Source: original entry ↗
More from GitHub
Follow GitHub to get its new changes in your feed and email digest.
Copilot model policy API for enterprise, orgs, and teams
REST API endpoints now available to retrieve and update Copilot model policies for enterprises, teams, apps, and organizations, enabling centralized policy management at scale.
GitHub Copilot models deprecated
GitHub has deprecated certain models across GitHub Copilot experiences including Chat, inline edits, and code completions, effective October 19, 2026. Users may need to migrate to supported models.
Some Git over HTTPS may temporarily require authentication
GitHub may temporarily require authentication for clones and fetches of public repositories over HTTPS during periods of unusual traffic to protect service availability.