Skip to content
NewsProduct launch

GitHub Copilot drops Gemini 2.5 Pro and Gemini 3 Flash effective July 31

· by Pondero Newsdesk

The short version

GitHub retired Gemini 2.5 Pro and Gemini 3 Flash from every Copilot experience on July 31, 2026. Teams moving to the recommended Gemini 3.1 Pro face a second forced migration: that model hits its own deprecation date on September 1.

GitHub Copilot drops Gemini 2.5 Pro and Gemini 3 Flash effective July 31

GitHub retired Gemini 2.5 Pro and Gemini 3 Flash from every Copilot surface on July 31, 2026. Any agent workflow or configured Copilot session that references those model names now breaks silently. The harder detail: one of GitHub's two recommended replacements is already on the next deprecation list.

What changed

The removal covers all Copilot experiences, per the GitHub Changelog: Copilot Chat, inline edits, ask and agent modes, and code completions. GitHub listed two replacements: Gemini 3.1 Pro (Preview) for users on Gemini 2.5 Pro, and Gemini 3.6 Flash for users on Gemini 3 Flash. Gemini 3.6 Flash was itself added to Copilot on July 21, ten days before the older Flash model was pulled.

GitHub posted the advance notice on July 2, giving teams 29 days. That announcement listed Gemini 3.5 Flash as the Flash replacement. By the time the deprecation executed, the recommended path had been updated to Gemini 3.6 Flash, since a newer model had launched in the interim.

Copilot Enterprise administrators face one additional step. Replacement models do not auto-enable. Administrators must open Copilot settings, locate the model policy for the target model, and confirm it appears in the model selector in VS Code or on github.com. No action is required to remove the deprecated models.

The trap in the Gemini 3.1 Pro upgrade path

Teams planning to move from Gemini 2.5 Pro to Gemini 3.1 Pro should not treat that as a stable landing point. GitHub published a second deprecation notice on July 31 covering the next removal wave, scheduled for September 1. Gemini 3.1 Pro is on that list, with Gemini 3.6 Flash as the recommended alternative.

Teams that migrate to 3.1 Pro now will need a second migration before September 1. The direct path is Gemini 3.6 Flash for both Pro and Flash users.

The September 1 wave reaches beyond the Google model tier. Claude Opus 4.5, Claude Opus 4.6, Claude Sonnet 4.5, and Claude Sonnet 4.6 are all scheduled for removal, with Claude Sonnet 5 as the recommended replacement for Sonnet users and Claude Opus 4.7, 4.8, or 5 for Opus users. GitHub noted that Claude Sonnet 4.6 will remain available to individual Copilot subscribers on annual plans.

Why this matters for AI-tool operators

GitHub maintained a fast model-rotation pace throughout the first half of 2026: GPT-4.1 exited in early June, followed by GPT-5.2 and GPT-5.2-Codex days later. The July 31 Gemini removal and the September 1 Claude sweep complete a full generational reset of the Copilot roster in under three months.

The operational risk is concrete. Any Copilot agent session, VS Code config, or CI/CD integration referencing "Gemini 2.5 Pro" or "Gemini 3 Flash" by model name is now broken. The same problem arrives again in 28 days for teams on the affected Claude models. Auditing those references before September 1 is the next action.

Teams reviewing their GitHub Copilot plan options can see current model availability in the Copilot documentation.

What to watch next

The current trajectory consolidates the Google track on Gemini 3.6 Flash for both chat and completions work. Watch whether GitHub adds a Pro-tier Google model successor before September 1. A new Pro-tier entry would change the calculus for teams that need higher reasoning capacity than a Flash model delivers. The September wave also marks the first time GitHub has pulled multiple Claude Sonnet and Opus generations simultaneously.

Sources