Daily⁠ · Oct 21, 2026⁠ · Gemini CLI · 🌶️🌶️Worth a look

Untrusted folders keep their Gemini CLI settings

Gemini CLI users, update now: settings in untrusted folders are now read-only. Before, gemini mcp add or gemini mcp remove in a folder you hadn’t trusted could remove all existing keys from that project’s .gemini/settings.json.

What changed

Adding an MCP server shouldn’t erase your project’s settings file. In a folder you haven’t trusted, Gemini CLI ignores the folder’s workspace settings for the session, and a project-scoped write could then wipe the file on disk.

What changed

Workspace settings in an untrusted folder are now read-only. Those commands stop with an error and leave the file alone, while --scope user keeps working. Trusting the folder makes workspace settings writable again.

What to do

Update to Gemini CLI 0.65.0 or later.

Source: Gemini CLI v0.65.0 release notes⁠ · GitHub: google-gemini/gemini-cli