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-24-gemini-cli-the-readme-stops-promising-obsolete-access-and-warns-about-gemini-4-optimization

The README stops promising obsolete access and warns about Gemini 4 optimization. Google’s README now says Gemini CLI is not optimized for Gemini 4 Argon and recommends Antigravity for current models. It removes obsolete free-access selling points and states that consumer Google-login access was replaced on 2026-06-18. The stable branch’s older authentication guide still recommends consumer Google sign-in. The new pinned README is a receipt for Google’s October statement; it does not establish the historical bytes of a service notice at the previous cutoff or a universal shutdown of API-key/Vertex access.

Channel: docs-only. Half: both. Date: 2026-10-16.

Operator consequence: Separate choosing a harness version from verifying an account’s service entitlement. Do not promote Gemini 4 launch benchmarks into Gemini CLI performance, or treat an installable npm package as a service guarantee. For migration planning, verify the actual authentication route and export/import requirements before allocating operator time to repairing an intentionally unavailable login path.

Receipt

Finding metadata

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Finding ID: 2026-10-24-gemini-cli-the-readme-stops-promising-obsolete-access-and-warns-about-gemini-4-optimization

Profile citations

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact