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-mcp-add-can-erase-untrusted-project-settings-until-v0-65-0-preview

MCP add can erase untrusted project settings until v0.65.0 preview. In an untrusted or not-yet-trusted folder, stable 0.64.0 keeps an empty in-memory workspace settings object with a writable project file path. Default project-scoped gemini mcp add can write that object back and erase existing keys in .gemini/settings.json. Issue #29465 reports this on 0.60.0. Stable mcp remove instead finds an empty server map and returns before writing; the evidence does not support a destructive remove claim. Preview 0.65.0-preview.0 marks the empty workspace read-only and rejects project-scoped add/remove with a trust error.

Channel: preview-or-beta. Half: defect. Date: 2026-10-13.

Operator consequence: On stable, back up project settings and use mcp add with --scope user, or deliberately trust the folder before project-scoped add. Inspect the resulting settings file. Test 0.65.0-preview.0 if write refusal is needed now; upgrading only to 0.64.0 does not deliver this repair.

Receipt

Finding metadata

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

Finding ID: 2026-10-13-gemini-cli-mcp-add-can-erase-untrusted-project-settings-until-v0-65-0-preview

Profile citations

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact