[BUG] Claude Repeatedly asks for permission to run commands, even when I've already granted it

[f1sherman]

Environment

• Platform (select one):
  • Anthropic API
  • AWS Bedrock
  • Google Vertex AI
  • Other:
• Claude CLI version: 0.2.73 (Claude Code)
• Operating System: MacOS 15.4.1
• Terminal: iTerm2/tmux

Bug Description

In my project directory, I have a script (bin/rspec) to run tests. For some reason, even though I always choose Yes, and don't ask again for rspec commands in <path>, it keeps asking for permission. One strange thing is that Claude Code omits the bin/ in the message. I wonder if that's related?

Steps to Reproduce

1. Ask Claude to run tests with bin/rspec <path>
2. Answer Yes, and don't ask again for rspec commands in <path>
3. Ask Claude to run tests again
4. Claude prompts again on whether it can run the command

Expected Behavior

After step 3 I should not be prompted again

Actual Behavior

After step 3 I am prompted again

[leonaburime-ucla]

So damn frustrating. I want to leave it running while I do something else and it just freezes asking for permission when I just granted it. Awful!

[ZivBA]

Not sure in which of the many identical issues to put this, so I'm hoping someone catches it here:
I believe the issue stems from inconsistent expansion of the ~ sign (home folder).
Sometimes Claude will try to read from the relative path (~/someFolder), and when you approve the action, the actual permission written to the settings will be "Read(/home//someFolder/**)"
But when Claude tries again to read from ~/someFolder, it will not match the rule in the settings JSON.
Manually adding the relative path (as ~/someFolder) to permissions (from Claude /permissions or directly to settings json) will resolve the issue.

I believe a proper solution would be for claude to identify home-folder paths, and add both the relative and absolute paths to the 'allowed' list, so both versions will work (or for Claude to always expand homefolder paths behind the scenes?)

[dluc]

@claude please fix this, it's super annoying, high priority. node: v24.9.0

#819
#2560
#7104
#7662

[cruftyoldsysadmin]

@claude Do better. Take 2 days and stop building new broken features, just fix the old broken features.

[adriand]

This happens with me all the time, and it seems to be with just certain commands. Right now the problematic command is jq. Local settings for Claude:

{
  "permissions": {
    "allow": [
      "Bash(bundle exec rake:*)",
      "Bash(find:*)",
      "Bash(bundle exec rails runner:*)",
      "WebFetch(domain:github.com)",
      "Bash(xargs sed:*)",
      "Bash(npm run typecheck:*)",
      "Bash(bundle exec rspec:*)",
      "Bash(git log:*)",
      "Bash(npm run:*)",
      "Bash(npx eslint:*)",
      "Bash(bundle info:*)",
      "Bash(bundle exec rails console:*)",
      "Bash(git diff:*)",
      "Bash(rails generate model:*)",
      "Bash(rails generate migration:*)",
      "Bash(rake:*)",
      "Bash(bundle install:*)",
      "Bash(bundle exec rails generate:*)",
      "Read(//tmp/**)",
      "Bash(bin/rails generate:*)",
      "Bash(bin/rails db:migrate:*)",
      "Bash(psql:*)",
      "Bash(tee:*)",
      "Bash(test:*)",
      "Bash(bin/rails runner:*)",
      "Bash(cat:*)",
      "Bash(jq:*)",
      "WebFetch(domain:kamal-deploy.org)"
    ],
    "deny": [],
    "ask": []
  }
}

Despite that:

 Bash command

   jq '.elements | length' /PATH_REDACTED
   Count total elements in scaffold

 Do you want to proceed?
 ❯ 1. Yes
   2. Type here to tell Claude what to do differently

It's quite irritating. I also notice that it doesn't give me the option to allow these requests going forward. It's like it "knows" I've already told it that it can use the tool, but feels the need to ask me each time anyway.

[github-actions]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

[exFalso]

Fellow frustrated user here. From what I can tell there are actually two issues here

1. Claude Code asking for a permission even after it's been given (@f1sherman)
2. Claude Code not even offering "Yes, and don't ask again" (@adriand)

I'm experiencing 2, for which I found a strange workaround: Create a runnable script that wraps the call, and instruct claude to prefix the commands with this script. It will still re-ask a couple of times, but to me it seems to work better.