Support glob patterns in additionalDirectories configuration for consistency with other permission rules
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
The additionalDirectories field in Claude Code settings requires specifying each directory path explicitly, creating unnecessary friction. This is especially problematic in monorepos, working across multiple repos, dynamic directory structures, and git worktree workflows. Additionally, this limitation creates inconsistency with how glob patterns work elsewhere in Claude Code's permission system.
Other related issues
Issue #3146: Configure Additional Directories via Settings Files (now implemented but doesn't cover glob patterns)
Issue #23109: Trusted workspace patterns to skip trust prompt for git worktrees
Issue #51286: Concurrent subagent dispatch: additionalDirectories glob doesn't propagate from parent to child
Issue #33268: additionalDirectories glob patterns don't match non-existent paths for create operations
Proposed Solution
Support glob patterns (wildcards like and *) in additionalDirectories, consistent with how they work in allow, deny, and ask permission rules:
Alternative Solutions
_No response_
Priority
Medium - Would be very helpful
Feature Category
Configuration and settings
Use Case Example
_No response_
Additional Context
_No response_