Feature: Add "Always allow for this project" option to bash permission dialog

Resolved 💬 3 comments Opened Mar 20, 2026 by aaron-pengx Closed Mar 23, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

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_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗