[DOCS]
Documentation Type
Incorrect/outdated documentation
Documentation Location
https://code.claude.com/docs/en/settings
Section/Topic
Other configuration
Current Documentation
Bug Report: Documentation shows incorrect Bash permissions syntax
Summary
Official Claude Code documentation shows Bash(command:*) syntax for wildcard permissions, but the actual JSON schema validation rejects this syntax and only accepts "Bash" without parentheses.
Documentation Claims
Multiple official sources show this syntax:
"Bash(git:*)"- allow all git commands"Bash(npm:*)"- allow all npm commands"Bash(npm run test:*)"- allow npm run test with any arguments
Sources:
- https://code.claude.com/docs/en/settings
- https://www.petefreitag.com/blog/claude-code-permissions/
- https://gizin.co.jp/en/tips/claude-code-permissions-settings
Actual Behavior
When attempting to use "Bash(*)" or "Bash(command:*)" in .claude/settings.json, schema validation fails with:
Settings validation failed:
- permissions.allow.X: Use "Bash" without parentheses to allow all commands.
Remove the parentheses or specify a command pattern.
Examples: Bash, Bash(npm:*), Bash(npm install)
The error message itself is contradictory - it says to "Remove the parentheses" but then shows examples WITH parentheses like Bash(npm:*).
What's Wrong or Missing?
Actual Working Syntax
Only this works:
{
"permissions": {
"allow": ["Bash"]
}
}
This allows ALL bash commands, with no way to create wildcards for specific command patterns.
Suggested Improvement
Expected Behavior
Either:
- The documentation should be corrected to show
"Bash"as the only valid syntax, OR - The schema validation should be updated to accept
Bash(command:*)wildcard patterns
Steps to Reproduce
- Create
.claude/settings.jsonwith:
``json``
{
"permissions": {
"allow": ["Bash(git:*)"]
}
}
- Try to use Claude Code
- See validation error rejecting the syntax shown in documentation
Environment
- Claude Code version: VSCode Extension (latest as of 2026-01-07)
- Platform: Linux
Impact
High - Prevents users from using a feature
Additional Context
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗