Product Signal
GitHub Copilot retires two Gemini models
GitHub has deprecated Gemini 2.5 Pro and Gemini 3 Flash across Copilot experiences, narrowing model availability in chat, completions, inline edits, and agent workflows.
GitHub says Gemini 2.5 Pro and Gemini 3 Flash were deprecated across GitHub Copilot on July 31, covering chat, code completion, inline edits, ask workflows, and agent mode. This is not a change to one experimental surface: it removes two model choices from the main workflows through which developers and enterprise teams use Copilot.
Availability narrowed across core workflows
GitHub’s notice explicitly covers all GitHub Copilot experiences, including Copilot Chat, inline edits, ask and agent modes, and code completions. The change therefore affects the model menu used in routine coding, question-answering, and agentic work rather than a limited feature entry point. For organizations that embedded either model in defaults, quality evaluations, or internal usage policies, the update is a concrete change in platform state.
Distribution determines practical access
A foundation model’s technical capability does not automatically become a capability developers can use. In an integrated product such as Copilot, continued hosting, routing, and exposure by the platform determine whether a model reaches a production workflow. The retirement shows that competition among models is not only about benchmark results, parameters, or API prices; it is also about inclusion in developer-tool distribution. Enterprise preferences still depend on the replacement choices the platform makes available.
Replacement quality will set migration costs
The near-term effect depends on which alternatives GitHub offers and whether they match the retired models in code quality, context handling, speed, and governance controls. The strongest countercase is that disruption may be modest if few users selected these models by default and substitutes are close on quality and price. Teams that intentionally assigned work by model, however, may still need to revalidate prompts, evaluation suites, and permission policies.
What to watch next
Watch for GitHub disclosures on replacement models, migration windows, affected subscription tiers, and administrator guidance. Default-routing changes or new enterprise controls tied to the retirement would strengthen the case that Copilot is productizing management of its model portfolio. Evidence that either model remains available through another Copilot surface or compatibility layer would weaken the conclusion that distribution has broadly narrowed.