Feature request
Today the permission popup offers three choices:
- Yes
- Yes, always
- No
"Yes, always" writes the allow rule to project scope (`.claude/settings.local.json`). There's no way to approve an action globally for all projects from the popup itself — the only workaround is to manually cut the rule from the project's settings file and paste it into `~/.claude/settings.json`.
Proposed change
Split option 2 into two:
- Yes
- Yes, always in this project
- Yes, always for this user (all projects)
- No
This lets users pick the correct scope at approval time instead of hand-editing settings files afterward.
Feature request
Today the permission popup offers three choices:
"Yes, always" writes the allow rule to project scope (`.claude/settings.local.json`). There's no way to approve an action globally for all projects from the popup itself — the only workaround is to manually cut the rule from the project's settings file and paste it into `~/.claude/settings.json`.
Proposed change
Split option 2 into two:
This lets users pick the correct scope at approval time instead of hand-editing settings files afterward.