Feature request: /permissions should support a global scope

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

/permissions currently only reads all scopes but writes exclusively to the current repo's .claude/settings.local.json — there's no way to target the global ~/.claude/settings.json through the UI.

This is a real gap for anyone managing permission policy that's meant to be identical across many projects (e.g. a standing set of allow/ask/deny rules, independent of any hooks). Right now the only way to add or edit a global permission rule is to hand-edit ~/.claude/settings.json directly — /permissions can't help at all in that case, since it structurally only ever writes to the project-local file.

Requested: an option in the /permissions UI (e.g. a scope picker, or a --global flag) to write rules to ~/.claude/settings.json instead of .claude/settings.local.json, so global policy can be managed through the same guided interface as project-local policy.

Proposed Solution

An option in the /permissions UI (e.g. a scope picker, or a --global flag) to write rules to ~/.claude/settings.json instead of .claude/settings.local.json, so global policy can be managed through the same guided interface as project-local policy.

Concretely, that means one of two implementations Anthropic could pick between:

A scope picker — when adding a rule via /permissions, the UI asks "apply to: this project only / all projects (global)" before saving.
A --global flag — e.g. /permissions --global opens the same interactive UI but targets ~/.claude/settings.json as the write destination instead of the repo's .claude/settings.local.json.
Either would close the gap: right now /permissions can view rules from all three scopes (user, project, local) but can only write to the local one, so global policy still requires hand-editing JSON.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_