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
- Cognition rumored to launch a new model soon, per AI insider hunch — realsohamparekh · 2026-09-06
- Redditor builds free AskSary creative studio with game engine GPT can play and patch live — Beneficial-Cow-7408 · 2026-09-06
- Do the fun terminal work yourself, let Claude handle the boring chores — 4310sy · 2026-09-06
- Heavy AI user's cost ledger: 100+ agents a day, $70 of DeepSeek in two days — simmon_charlie · 2026-09-06
- First untrained agent run on local Qwen 3.8 Flash, no skills configured — jasonkneen · 2026-09-06
- Is a schema-aware memory graph 'overfitting'? Dev asks for the cleanest leakage test — chaachans · 2026-09-06