[FEATURE] Control where "Always allow" permissions are persisted
Resolved 💬 3 comments Opened Feb 18, 2026 by darkweaver87 Closed Feb 19, 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
Currently, "Always allow" in the CLI permission prompt always writes to the repo-local .claude/settings.local.json. There is no way to redirect this to the global ~/.claude/settings.json.
Proposed Solution
A flag or setting (e.g. --permissions-scope=global or a config option) to control this behavior would be useful for users who want to maintain a single global permission config without repo-local state (like allowing bash read-only 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_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗