Gemini CLI fix: explicit gemini-3-pro-preview IDs no longer silently rewritten to 3.1
FanouZeng-TT · ghdev · 2026-09-20
A community PR (#29420) fixes a routing bug in google-gemini/gemini-cli where an explicit --model gemini-3-pro-preview was silently rewritten to gemini-3.1-pro-preview whenever the 3.1 rollout flag was enabled. Only auto/pro aliases should follow the rollout; pinned versions must stay pinned.
Key changes:
- The legacy resolveModel grouped the explicit ID with the auto case in one switch branch; it now has its own pinning case.
- Dynamic defaultModelConfigs no longer remaps the explicit key through rollout contexts, and the pro classifier tier gets a requestedModels anchor.
- Two call sites that used the explicit ID as a placeholder for the rollout target (availability catalog, preview chains) now derive it inline or use aliases.
Includes targeted regression tests; fixes issue #29417.
More from coding & agent
- Three coding habits that may never come back in the AI-agent era — BLUECOW009 · 2026-09-20
- mcp-proxmox lets you manage Proxmox VE clusters with natural language — modelcontextprotocol · 2026-09-20
- Tronsave MCP Testnet lets agents buy and sell TRON resources via one interface — modelcontextprotocol · 2026-09-20
- Open questions on JEV: model size, calibration reliability, and a future fine-tuning API — vykthur · 2026-09-20
- One astra general directs 7 jev agents in Warcraft 3: 1,000+ LLM calls for ~20 cents — Vjeux · 2026-09-20
- Composite system1+system2 agent harness runs WC3 micro in RL env, open-sourcing soon — Vjeux · 2026-09-20