--allowed-tools does not work in non-interactive mode

[mistergarrison]

What happened?

--allowed-tools only applies to interactive mode, but is ignored if the prompt is supplied on the command-line. The following command should work, but doesn't:

gemini --allowed-tools="ShellTool(wc)" \
    --prompt="use wc to tell me how many lines there are in /proc/meminfo"

What did you expect to happen?

$ gemini --allowed-tools="ShellTool(wc)" \
    --prompt="use wc to tell me how many lines there are in /proc/meminfo"
There are 55 lines in /proc/meminfo.
$ 

Client information

Client Information

Run gemini to enter the interactive CLI, then run the /about command.

> /about
╭─────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                             │
│ About Gemini CLI                                                                            │
│                                                                                             │
│ CLI Version                     0.7.0-nightly.20250918.2722473a-git.fa8cea17                │
│ Git Commit                      fa8cea17                                                    │
│ Model                           gemini-2.5-pro                                              │
│ Sandbox                         no sandbox                                                  │
│ OS                              linux                                                       │
│ Auth Method                     gemini-api-key                                              │
│                                                                                             │
╰─────────────────────────────────────────────────────────────────────────────────────────────╯

Login information

n/a

Anything else we need to know?

It would be good if this was also fixed for tools.allowed in settings.json as well.

[gemini-cli]

This is a bug report where a core feature, using allowed tools in non-interactive mode, is not working as expected. The report is well-documented with version information and clear steps to reproduce.

[prajwxlk]

/assign

[gemini-cli]

👋 @prajwxlk, you've been assigned to this issue! Thank you for taking the time to contribute. Make sure to check out our contributing guidelines.

[mistergarrison]

Hey Prajwal,

I wasn't sure about the norms (and haven't submitted a PR in github before) - I had planned to do this: should I assign the issue to myself, or do you want to take it?

[prajwxlk]

Hello @mistergarrison, I understand your situation. I would be perfectly fine if you wanted to proceed ahead with this issue although I don't know how to reassign the issue as well. As far, I understand using /assign works only when the issue hasn't been assigned to someone else. Also, the PR I've made fixes this issue. The reason I've made a draft PR is because I want to know how mapping of the ToolClass and actual tool_calls works in this codebase and if at all it has already been implemented. This will allow for the fix to work for all types of tools and not just only ShellTool().

[gemini-cli]

@prajwxlk Thanks for taking interest but this issue is already assigned. We'd still love to have you contribute. Check out our Help Wanted list for issues where we need some extra attention.