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
- 35 CVEs tied to AI coding tools this year, with no review budget to match — YvesMulkers · 2026-10-23
- Indie dev's agent tracks 519 directories, 311 submitted for SEO backlinks — fekdaoui · 2026-10-23
- ScienceClaw Hackathon at MIT Media Lab to build decentralized AI agent collectives for science — ProfBuehlerMIT · 2026-10-23
- What should a native agent harness handle beyond tool calling? — Glittering812 · 2026-10-23
- Running ~100 DeepSeek v4.1 flash agents in parallel for under $20/month — zack_overflow · 2026-10-23
- MCP's stateless 2026-07-28 spec drops session-id — how are stateful tools adapting? — Stock-Pumpkin-8859 · 2026-10-23