Preflight Checklist
Problem Statement
When Claude Code asks to run a bash command, the permission dialog only offers 3 options: allow once, skip, or always allow for this session. There is no way to permanently whitelist a command for the current project without manually editing .claude/settings.json. This breaks workflow during active development sessions where the same commands are repeatedly executed.
Proposed Solution
Add a 4th button "Always allow for this project" to the bash permission dialog. Clicking it would automatically append the command pattern to .claude/settings.json under permissions.allow.
Example: running git status → adds "Bash(git *)" to settings.
Optionally offer a sub-choice: allow this exact command vs. allow the command family (e.g., all git commands).
Alternative Solutions
No response
Priority
Medium - Would be very helpful
Feature Category
CLI commands and flags
Use Case Example
No response
Additional Context
No response
Preflight Checklist
Problem Statement
When Claude Code asks to run a bash command, the permission dialog only offers 3 options: allow once, skip, or always allow for this session. There is no way to permanently whitelist a command for the current project without manually editing
.claude/settings.json. This breaks workflow during active development sessions where the same commands are repeatedly executed.Proposed Solution
Add a 4th button "Always allow for this project" to the bash permission dialog. Clicking it would automatically append the command pattern to
.claude/settings.jsonunderpermissions.allow.Example: running
git status→ adds"Bash(git *)"to settings.Optionally offer a sub-choice: allow this exact command vs. allow the command family (e.g., all git commands).
Alternative Solutions
No response
Priority
Medium - Would be very helpful
Feature Category
CLI commands and flags
Use Case Example
No response
Additional Context
No response