Bug: Claude CLI non-interactive mode doesn't respect configured tool permissions

$ claude -p "echo 'Hello World' > test.txt && cat test.txt"
I'll need permission to use the Bash tool to execute that command. Once granted, I'll create the test.txt file with "Hello World" and display its contents.

I ran into the same issue a couple of days ago (see #563 )
As it turns out, Claude Code does not use the allowed tools as defined in the configs when running in non-interactive mode. You have to pass the allowed tools to the command with the --allowedTools flag followed by a comma separated list of your required tools - like so:
claude -p "npm run build and git commit and git push" --allowedTools "Bash(git:*),Edit"

Legend @TomDigitalDavid that gets me going :) I always just did

claude config set hasCompletedProjectOnboarding true
claude config set hasTrustDialogAccepted true

claude config add allowedTools Bash
claude config add allowedTools Read
claude config add allowedTools Write
claude config add allowedTools Edit
claude config add allowedTools Create

I cannot get this to work. Trying to get a global config that will remove the endless interruptions.

Hi all, I've verified that permission rules .claude/settings.json are respected when running claude -p. Please ensure that your settings are configured properly: https://docs.anthropic.com/en/docs/claude-code/settings#settings-files

@rboyce-ant This isn't working when not running in -p - claude keeps asking me for permission on every curl command it wants to run. I just want to let it cook!

@rboyce-ant I'm still seeing this exactly as described by the OP. The issue is as described in https://github.com/anthropics/claude-code/issues/1188. Although .claude/settings.json is being read, permissions are ignored where patterns are used.

So this works:

{
  "permissions": {
    "allow": [
      "Bash"
    ]
  }
}

But this doesn't:

{
  "permissions": {
    "allow": [
      "Bash(*)"
    ]
  }
}

$ claude --version
1.0.40 (Claude Code)

@rboyce-ant I am finding similar results to the other reporters. Claude Code works fine for me in interactive mode, but in non-interactive mode:

 Bash(npm link)
  ⎿  Error: Claude requested permissions to use Bash, but you haven't granted it yet.
 Update(demos/hello/package.json)
  ⎿  Error: Claude requested permissions to use Edit, but you haven't granted it yet.
 Write(demos/hello/hello.md)
  ⎿  Error: Claude requested permissions to use Write, but you haven't granted it yet.
Update(demos/hello/package.json)
  ⎿  Error: Claude requested permissions to use MultiEdit, but you haven't granted it yet.

.claude\settings.local.json has:

{
  "permissions": {
    "allow": [
      "Read(*)",
      "Search(*)",
      "Edit(*)",
      "Write(*)",
      "MultiEdit(*)",
      ...
    ],
    "deny": []
  }
}

I am still seeing the same issue as OP. In non-interactive mode:

This works
claude -p "create a file called add.py that adds two numbers" --output-format json --allowedTools Write

This doesn't work
claude -p "create a file called add.py that adds two numbers" --output-format json --allowedTools Write(/**)

@rboyce-ant can you please reopen this issue? There have been multiple independent reproductions of the issue since you closed it.

I am still seeing the same issue as OP. In non-interactive mode: This works claude -p "create a file called add.py that adds two numbers" --output-format json --allowedTools Write This doesn't work claude -p "create a file called add.py that adds two numbers" --output-format json --allowedTools Write(/**)

I am having the exact same issue, which prevents me from restricting where Claude Code can write. Just allowing Write seems a bit risky to me.

Definitely not fixed. But this specific case with path patterns is covered in #1188

MCP settings are also not respected. It picks up the global settings, but does not allow passing in mcpSettings.

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.