Allowing `Bash(*)` or `Bash(*:*)` doesn't seem to work

Hey thanks for the report! Renamed /approved-tools -> /allowed-tools in the latest version. @rboyce-ant is going to follow up with a fix for permission syntax.

To unblock, use Bash(ls:*) or Bash. Support for Bash(*) and Bash(ls) landing soon.

Thank @bcherny !

FWIW I still can't get it to avoid asking for permissions for lots of things. I've got this:

 claude config get allowedTools
[
  'Bash',
  'Bash(find:*)',
  'Bash(grep:*)',
  'FileEdit',
  'FileRead',
  'FileWrite',
  'Grep',
  'Update',
  'Write'
]

But still get:

│ Do you want to make this edit to foo.py?                                                                                                                                      │
│ ❯ Yes                                                                                                                                                                          │
│   Yes, and don't ask again this session                                                                                                                                        │
│   No, and tell Claude what to do differently (esc)

Possibly updates are landing soon, no stress if so

Seems like this is still not working? Using bash in the CI action (Bash(*)) leads to:

🔧 Bash

Parameters:

{
"command": "npm test",
"description": "Run Jest tests to verify powerOf function works"
}
❌ Error: Claude requested permissions to use Bash, but you haven't granted it yet.

Token usage: 10 input, 7 output

Still can't use Bash(*) or similar - still in the pipeline? (I guess it's a bit about lowering API calls rate)?
Would be good to have it! Annoying to have to go manually on every new command/format...

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.