I had to ask Gemini CLI to remind myself ;) but you can add this into settings.json:
{ "excludeTools": ["run_shell_command", "write_file"] }
but if you ask Gemini CLI to do this it'll guide you!
I also work on the product :-)
You can also extend with the Extensions feature - https://github.com/google-gemini/gemini-cli/blob/main/docs/e...
Re:Gemini CLI
by _ryanjsalva on Wednesday June 25, 2025 @10:02AM
(#44377462)
I also work on the product. You can extend the tools with MCP. https://github.com/google-gemini/gemini-cli/blob/main/docs/t...
Re:Gemini CLI
by silverlake on Wednesday June 25, 2025 @10:59AM
(#44378125)
I tried to get Gemini CLI to update itself using the MCP settings for Claude. It went off the rails. I then fed it the link you provided and it correctly updates it's settings file. You might mention the settings.json file in the README.
Feedback: A command to add MCP servers like claude code offers would be handy.
Re:Gemini CLI
by _ryanjsalva on Wednesday June 25, 2025 @03:10PM
(#44380862)
100% - It's on our list!
>gemini -p "Say hello"
Says hello, and just returns right away.
The gemini doc for -p says "Prompt. Appended to input on stdin (if any)."
So it doesn't follow the doc.gemini "Say hello"
Fails as it doesn't take any arguments.
For comparison, claude lets you pass the prompt as a positional argument, but it does append it to the prompt and then gives you a running session. That's what I'd want for my use-case.Pretty close to what I discovered is essential in https://github.com/aperoc/toolkami, 7 tools will cover majority of the use cases.
currently it seems these are the CLI tools available. Is it possible to extend or actually disable some of these tools (for various reasons)?
> Available Gemini CLI tools: