[FEATURE]

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

Title: Feature Request: Directory-scoped Bash permissions

Body:

Problem
The current .claude/settings.local.json permission system supports directory scoping for Read, Write, Edit, Glob, and Grep:

"Read(D:\\Development\\*)",
"Write(C:\\Projects\\myapp\\*)",
However, Bash permissions are command-pattern only — scoped to the executable name (e.g., Bash(git ), Bash(npm )), NOT to directories. This means:

You can't say "allow any bash command in D:\Development\" — only "allow specific commands everywhere."
The only way to avoid prompts for all bash commands is Bash(*) — which is global and removes safety for all commands on the entire filesystem.
Proposed Enhancement
Support directory-scoped Bash permissions:

"Bash(D:\\Development\\*)",
"Bash(Z:\\*)",
"Bash(C:\\Customers\\GM\\*)"
This would allow any bash command whose working directory or arguments fall within the specified paths, while still prompting for anything outside.

Use Case
Developers working in multiple repos across different drives (e.g., D:\Development, network drive Z:\) need fine-grained control. They want to trust Bash commands in known project directories but keep the safety prompt for potentially dangerous operations elsewhere.

Proposed Solution

I'd like to trust Bash commands in known project directories but keep the safety prompt for potentially dangerous operations elsewhere.

Alternative Solutions

I'm not aware of any alternate solution.

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

I have a long running process with /goal (hrs.) and I miss prompts when a bash command needs permission from me. I know this is my problem, but auto permission (under some circumstances) is a good thing.

Additional Context

_No response_