Move Copilot workflows off Gemini 2.5 Pro and Gemini 3 Flash before July 31
GitHub will remove Gemini 2.5 Pro and Gemini 3 Flash from Copilot experiences on July 31, 2026, so teams should check model policies, pinned workflows, and fallback choices now.
Confirmed: GitHub says Gemini 2.5 Pro and Gemini 3 Flash will be deprecated across GitHub Copilot on July 31, 2026. The removal affects Copilot Chat, inline edits, ask mode, agent mode, and code completions, so teams that pinned either model need a short migration pass before the end of the month.
What changed
GitHub posted the deprecation notice on July 2, 2026. The affected models are Gemini 2.5 Pro and Gemini 3 Flash inside GitHub Copilot experiences, not Gemini access everywhere on the web or through Google APIs.
GitHub tells users to move workflows and integrations to supported Copilot models before July 31. Its notice suggests Gemini 3.1 Pro as the replacement for Gemini 2.5 Pro and Gemini 3.5 Flash as the replacement for Gemini 3 Flash. Enterprise administrators may also need to enable replacement models through Copilot model policies before users can select them in VS Code or on github.com.
| Area to check | What changes | Practical action | Caveat |
|---|---|---|---|
| Copilot Chat | Gemini 2.5 Pro and Gemini 3 Flash leave the selector | Test Gemini 3.1 Pro or Gemini 3.5 Flash where available | Available models depend on plan and policy |
| Inline edits | Gemini-backed edit flows need a replacement | Test common edit prompts before July 31 | Behavior may differ on large files |
| Agent mode | Agent workflows should not assume Gemini availability | Run a migration smoke test | Tool use and cost can shift by model |
| Enterprise policy | Admins may need to enable alternatives | Review model policy settings | Users may not see a model until policy allows it |
Why this is early
This is an official GitHub Changelog item, not a social rumor. The useful early window is the deadline: July 31 gives teams time to find pinned model choices, update internal instructions, and test replacements before developers hit a missing-model surprise.
GitHub's notice also points administrators toward Copilot model policies and the Copilot model selector as the places to verify replacement access. Those operational details do not replace the changelog notice; they explain where teams should check whether the replacement models are visible.
Key takeaways
- Gemini 2.5 Pro and Gemini 3 Flash are leaving Copilot experiences on July 31, 2026.
- GitHub suggests Gemini 3.1 Pro and Gemini 3.5 Flash as replacement paths.
- The change covers Chat, inline edits, ask mode, agent mode, and code completions.
- Individual users should check the Copilot model selector and migrate saved habits.
- Enterprise admins should verify model policies so replacement models are visible to licensed users.
- No manual cleanup is required to remove the old models after deprecation, according to GitHub.
Availability and access
The deprecation is scheduled, not immediate. Users can use the affected models until GitHub removes them, assuming the models are still available in their Copilot plan and policy configuration.
Replacement access depends on GitHub's supported Copilot model list and the organization's settings. Admins should not assume that every user can see the same replacement model in VS Code and github.com until policy and plan constraints are checked.
Practical LinkLoot angle
Treat this as a workflow migration, not just a model-picker cleanup. Copilot model changes can affect prompt behavior, edit style, latency, cost controls, and agent reliability.
A practical migration is small: list team workflows that mention Gemini, choose one supported default for quick edits and one for harder agent tasks, then run the same sample issue or refactor across both. Keep the result in your internal AI workflow notes. For broader agent setup, pair this with LinkLoot's AI agent tools guide.
What to verify before you act
- Check GitHub's model comparison page for the currently supported Copilot models.
- Confirm organization model policies allow the replacement model.
- Test VS Code and github.com separately; model visibility can differ by surface and policy.
- Review any internal docs, saved prompts, MCP workflows, or onboarding guides that name Gemini 2.5 Pro or Gemini 3 Flash.
- Watch for follow-up GitHub changelog entries before July 31 in case the supported model list changes again.
Source check
Confirmed by:
- GitHub Changelog: Gemini 2.5 Pro and Gemini 3 Flash are scheduled for Copilot deprecation on July 31, 2026.
- Changes.Watch independently tracks the GitHub changelog item and flags the July 31 removal as a deprecation that may affect integrations.
Context:
- This is a Copilot availability change, not a claim about Gemini's standalone availability from Google.
- LinkLoot will treat a revised GitHub deadline, replacement-model list, or policy change as an update trigger.
GitHub says both models will be deprecated across Copilot experiences on July 31, 2026.