GitHub Copilot retires Gemini, Kimi and Claude models on 2 October, and one replacement costs three times as much

The numbers, and where each one comes from

• 2 October 2026 is the retirement date for every model on that list, across every Copilot surface, from the GitHub changelog of 3 September 2026.
• Gemini 3.5 Flash at $1.50 and Gemini 3.8 Flash at $0.75 per million input tokens, output at $9.00 against $3.75, from our API price table, both rows checked against ai.google.dev on 5 September 2026.
• Kimi K2.7 Code at $0.95 and Kimi K3 at $3.00 per million input tokens, output at $4.00 against $15.00, same table, both rows checked against platform.kimi.ai on 5 September 2026.
• Claude Opus 5 at $5.00 per million input tokens and $25.00 output, checked against platform.claude.com on 5 September 2026. We hold no row for Claude Opus 4.7, so this site cannot say which way that fourth swap moves.
• A nearer deadline the changelog does not mention: 10 September 2026, the retirement date GitHub’s own reference table gives for MAI-Code-1-Flash.

The reference page and the changelog do not agree yet

Read on 6 September 2026, three days after the announcement, the supported-models reference still carried Gemini 3.5 Flash, Gemini 3.6 Flash, Kimi K2.7 Code and Claude Opus 4.7 in its list of generally available models, and its retirement-history table, which exists precisely to list models scheduled for retirement, had no row for any of the four. The most recent entry in it was the MAI-Code-1-Flash retirement due on 10 September.

That gap matters because of which page a person checks. An administrator auditing model policy goes to the reference, not to a changelog post from earlier in the week. On the day we looked, the reference would have told them nothing was ending. We are recording the state of both pages with the date we read them, and if the reference catches up we will say so here rather than quietly editing this paragraph away.

What to do before 2 October

If your team uses Copilot through a Business or Enterprise plan, the replacement models are not necessarily switched on. GitHub’s own instruction is that an administrator may need to enable them in model policy before anyone can select them, which means the failure mode on 2 October is not an error message, it is a model that has gone from the picker with nothing turned on to take its place.

If you call any of these models outside Copilot as well, treat the retirement as a prompt to look at your own rate rather than as an instruction. Nothing about a model leaving one product retires it from its vendor’s API, and on our table these replacements move the price in opposite directions.