Back to rankings

GitHub Copilot: MAI-Code-1-Flash Deprecation Scheduled for September 10, 2026

GitHub CopilotView original changelog

GitHub has scheduled MAI-Code-1-Flash, its original in-house Copilot coding model, for deprecation across all GitHub Copilot surfaces on September 10, 2026, following the same-day launch of its successor, MAI-Code-1.1-Flash. No manual cleanup is required after the cutover — the model simply drops out of the picker — but developers with workflows pinned to it should migrate before the deadline, and Business/Enterprise admins need to enable the replacement's policy in advance.

Key Takeaways

  • MAI-Code-1-Flash retires on September 10, 2026, exactly one month after the deprecation notice was published.
  • The retirement is directly tied to MAI-Code-1.1-Flash's launch on the same day, which GitHub positions as the drop-in replacement.
  • No manual cleanup is needed — the model automatically disappears from the selector once the deadline passes.
  • Developers with workflows or automations pinned to MAI-Code-1-Flash should switch references before September 10 to avoid disruption.
  • Business and Enterprise admins must proactively enable MAI-Code-1.1-Flash's policy, since it doesn't turn on automatically for those plans.
  • The notice follows GitHub's now-well-established deprecation pattern for 2026 — advance notice, then a hard cutoff, mirroring prior retirements of Gemini, Claude, and GPT models in Copilot.

MAI-Code-1-Flash Set to Retire September 10

GitHub has scheduled MAI-Code-1-Flash — Microsoft's original in-house Copilot coding model, launched in June 2026 — for deprecation across all GitHub Copilot experiences on September 10, 2026. The move follows the same-day rollout of its successor, MAI-Code-1.1-Flash, which GitHub is positioning as the direct replacement.

What Changes

After September 10, MAI-Code-1-Flash will no longer be selectable anywhere in GitHub Copilot, including Copilot Chat, VS Code, and github.com. GitHub says no manual removal is necessary — the model simply drops out of the model picker once the deprecation takes effect — but any workflows or automations still pinned to it should be updated to MAI-Code-1.1-Flash before the cutover.

For Enterprise Administrators

Organizations that haven't already enabled MAI-Code-1.1-Flash through their Copilot model policy will need to do so before the deprecation date, or users could temporarily lose access to that model family once MAI-Code-1-Flash is retired. Enterprise customers with questions are directed to their account managers, and GitHub is inviting feedback through the GitHub Community Discussion forum in the meantime.