[FEATURE] Add 'Allow globally' option to permission prompt

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 prompts for permission to run a command, users currently see two persistent options:

• Allow (one-time)
• Allow in project scope (saves to .claude/settings.json in the current project)

However, many commands are safe to run across ALL projects (e.g., git status, npm install, ls, curl, etc.). Currently, users must either:

1. Click "Allow in project scope" in every new project they work with
2. Manually edit ~/.claude/settings.local.json to add the command

This creates unnecessary friction for power users who work across many projects.

Proposed Solution

Add a third option to the permission prompt:

┌─────────────────────────────────────────────────┐
│ Allow this command?                             │
│                                                 │
│   npm install                                   │
│                                                 │
│ [Allow]  [Allow in project]  [Allow globally]  │
│                                                 │
│ [Deny]                                          │
└─────────────────────────────────────────────────┘

"Allow globally" would:

1. Add the command pattern to ~/.claude/settings.local.json under permissions.allow
2. Apply to ALL projects going forward
3. Work the same as manually adding to the global settings file

Alternative Solutions

Currently, users can:

1. Manually edit ~/.claude/settings.local.json to add patterns - but this requires knowing the exact pattern format and interrupts workflow
2. Use the /permissions command - but this doesn't offer a quick "make it global" action during the permission prompt

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

1. I'm working on a new React project and Claude wants to run npm install
2. I click "Allow in project scope"
3. Next week, I start a new Vue project
4. Claude asks permission for npm install again
5. I have to allow it again in this project
6. This repeats for every new project

With this feature:

1. First time Claude asks for npm install, I click "Allow globally"
2. Never prompted for npm install again in any project

Additional Context

The infrastructure already exists:

• ~/.claude/settings.local.json already stores global permissions in permissions.allow array
• The permission prompt already saves to project-scoped settings
• This would just add a third destination option

Example of existing global permissions structure in ~/.claude/settings.local.json:

{
  "permissions": {
    "allow": [
      "Bash(npm install:*)",
      "Bash(git status:*)",
      "WebSearch"
    ]
  }
}