GitHub removes the MAI-Code-1-Flash model from all GitHub Copilot experiences and directs users to its successor, MAI-Code-1.1-Flash

GitHub is retiring one of the models you can pick inside Copilot. In an official changelog post, GitHub says that with the launch of MAI-Code-1.1-Flash it will deprecate MAI-Code-1-Flash across all GitHub Copilot experiences on 10 September 2026.

For most people this is a quiet swap. GitHub states that no action is required to remove the older model once it is deprecated, and Copilot keeps working — the menu simply offers the newer model in place of the old one. If you choose a Copilot model from the picker in VS Code or on github.com and don’t think about it beyond that, there is nothing to do.

The people who need to act are the ones who have written the model’s name down somewhere. If a workflow, a CI step, an integration, or a script selects MAI-Code-1-Flash by identifier through the Copilot API, or if an enterprise policy allow-lists specific models, that reference stops pointing at a live model after 10 September. GitHub’s guidance is to update those workflows and integrations to use MAI-Code-1.1-Flash before the date.

Enterprise administrators have one extra step: enable the replacement model through Copilot settings and verify it shows up in the model selector in VS Code and on github.com, so their users can actually pick it. Customers with concerns are pointed to their GitHub account manager. This is a model-lifecycle deprecation rather than a service shutdown — there is no data to export and no feature going away, only a named model being replaced by its successor on a fixed date.