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-stable-bounds-authentication-retries-and-isolates-extension-loading-failures

Stable bounds authentication retries and isolates extension loading failures. Stable bounds verification retry attempts, preserves the retry count across credential refresh and clears cached Google credentials on the relevant authentication change. Loading extensions now warns and skips an invalid allowlist pattern, missing install metadata or a disallowed installed extension instead of preventing unrelated extensions from loading. Installation-time allowlist validation remains strict; this is not permission to install outside the allowlist.

Channel: tagged-release. Half: both. Date: 2026-10-20.

Operator consequence: On 0.65.0, investigate the named authentication or extension failure instead of assuming all integrations failed. Successful loading of other extensions no longer proves that every configured extension loaded, so deployment checks should inspect the warnings and effective extension list. The improvement reduces repeated login prompts and global startup failure, while retaining an operator decision about the failed component.

Receipt

Finding metadata

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

Finding ID: 2026-10-24-gemini-cli-stable-bounds-authentication-retries-and-isolates-extension-loading-failures

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact