Safety
Gemini CLI 0.65.0 blocks settings edits in untrusted folders
Gemini CLI 0.65.0 makes a folder's own settings read-only until you trust it, so gemini mcp add fails there unless you use --scope user.
- Date
- Works with
- Gemini CLI
What’s new
Gemini CLI 0.65.0 became the stable release on 20 October 2026. Its release notes list "Enforced read-only workspace settings in untrusted folders".
In the code change behind it, gemini mcp add and gemini mcp remove stop with an error when they would change the settings of a folder that Gemini CLI does not trust. The error starts: "Cannot modify settings in an untrusted workspace". Adding a connector with --scope user still works, because that saves it in your own settings file.
The release also keeps your history when you resume a session and quit quickly.
Why it matters
A folder you have not trusted cannot have its Gemini settings changed by accident. If gemini mcp add now fails with this error, add the connector with --scope user, or open Gemini CLI in the folder and trust it first.
How to try it
Run this command: see the command below. Then run gemini --version. It should show 0.65.0 or later.
npm install -g @google/gemini-cliRelated
Source
Checked against the source on 21 Oct 2026