Gemini CLI fix: pinned gemini-2.5-flash no longer silently rewritten to gemini-3.5-flash
HariomJangra · ghdev · 2026-09-06
A community PR fixes a model-resolution bug in Gemini CLI: explicitly pinned models like --model gemini-2.5-flash were silently rewritten to gemini-3.5-flash on backends with GA access, breaking projects without 3.5 access with a ModelNotFoundError.
The fix:
- Removes the endsWith('flash') catch-all in isFlashModel() so concrete IDs aren't treated as generic aliases;
- Drops the gemini-2.5-flash entry from dynamic model config resolutions;
- Adds regression tests verifying pinned IDs pass through untouched while the 'flash' alias still resolves to 3.5-flash.
Fixes issue #29213 (priority/p1).
More from coding & agent
- Microsoft's FrontierTour: AI governance becomes everyone's problem as agents take action — donasarkar · 2026-10-23
- Grady Booch revives Weinberg's 1971 quip: software so buggy one woodpecker could destroy civilization — Grady_Booch · 2026-10-23
- One Agent Replaces Half an SDR Team: Full Lead-Research-to-Email Workflow — tibo_maker · 2026-10-23
- Why don't coding agent harnesses ship with their own sandbox? Only amp does — Aryvyo · 2026-10-23
- Dev builds a VST synth with Codex and MCP, lets the AI jam in his studio — Yamapama · 2026-10-23
- AgentsInTheCloud update: use your Claude subscription with built-in coding agents — lucasmeijer · 2026-10-23