Evidence record / gemini-cli

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-13-gemini-cli-stable-v0-61-0-rewrites-explicit-flash-model-ids

Stable v0.61.0 rewrites explicit Flash model IDs. Since v0.61.0 the client rewrites an outgoing gemini-3.5-flash or gemini-3-flash model ID to gemini-3.8-flash, and gemini-3.1-flash-lite to gemini-3.5-flash-lite, when latest-Flash access is enabled. API-key, Vertex and Gateway auth return true for that gate in client code; Google login uses experiment flags. No exposed setting opts these exact IDs out of the mapping. This establishes request rewriting, not a measured served model or improved quality/latency. Other IDs pass through this table unless the separate experimental dynamic-model configuration changes resolution. The v0.61.0 narrative changelog omitted the mapping change while highlighting versioned-model preservation.

Channel: tagged-release. Half: both. Date: 2026-09-23.

Operator consequence: Re-baseline Flash evaluations when upgrading past 0.60.0, even if the configured ID is unchanged. Record the request and returned modelVersion separately; the latter was not observed here. Retaining 0.60.0 also retains this report’s older security/reliability defects, so it is not an unqualified remedy. Read preview cherry-picks rather than assuming every stable change had a week of preview exposure.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-gemini-cli-stable-v0-61-0-rewrites-explicit-flash-model-ids

Profile citations

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact