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-refuses-project-settings-writes-in-untrusted-workspaces

Stable refuses project-settings writes in untrusted workspaces. Stable now represents unloaded workspace settings as empty and read-only. The general settings writer rejects that object; project-scoped MCP add/remove also reject an untrusted or read-only workspace. Deliberately trusting the folder swaps in its real settings. This prevents the previously documented route from an empty in-memory object to overwriting existing .gemini/settings.json keys. It is a settings-persistence guard, not a read-only filesystem.

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

Operator consequence: Upgrade stable installations to 0.65.0 before project-scoped MCP configuration. A preview is no longer required for this fix. In an untrusted folder, choose user scope or make an explicit trust decision; do not treat the refusal as permission to silently enable trust. The agent can now reject the dangerous operation itself, removing the manual backup-and-inspect workaround for this specific defect while leaving repository trust with the operator.

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-refuses-project-settings-writes-in-untrusted-workspaces

Profile citations

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact