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 signals and issues that cite it, below.

Gemini 3.5 Flash GA Model Transition with Experiment Flag

What Changed

Implemented conditional model selection to transition users to Gemini 3.5 Flash GA model when experiment flag GEMINI_3_5_FLASH_GA_LAUNCHED (ID: 45780819) is enabled. Added hasGemini35FlashGAAccess() method in Config class, registered new experiment flag, created routing contexts, and added model configurations for gemini-3.5-flash with flash tier classification.

Operator Implication

Enables gradual rollout of Gemini 3.5 Flash GA to flagged users. Allows backend control of model availability per user cohort without requiring client updates. Updates auto-routing logic to use Flash GA when flag is enabled.

Receipt

Commit title: ‘Transition to flash GA model when experiment flag is present. (#27570)’ with 25 files modified across configurations, model hierarchies, and test

Finding metadata

Confidence: high
Actionability: test
Accessibility impact: none

Run: 2026-06-03-weekly-digest-2026-05-28_2026-06-03-frontier-v0

Finding ID: 2026-06-03-gemini-cli-flash-ga-transition

Accepted signals

Gemini 3.5 Flash GA routes to flagged users via backend experiment flag, no client update / 2026-06-03

Source links

Primary links, including exact changelog lines when available.

Gemini CLI
commitCommit title: 'Transition to flash GA model when experiment flag is present. (#27570)' with 25 files modified across configurations, model hierarchies, and test coverage for new Flash GA access evaluagithub.com/google-gemini/gemini-cli/commit/665228e983c611007c4e2d36550e67b34f75055e

Versioned source: run artifact