Skip to content

Permission prompt: split "Yes, always" into project-scope vs user-scope (all projects) #79732

Description

@barak107

Feature request

Today the permission popup offers three choices:

  1. Yes
  2. Yes, always
  3. 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:

  1. Yes
  2. Yes, always in this project
  3. Yes, always for this user (all projects)
  4. No

This lets users pick the correct scope at approval time instead of hand-editing settings files afterward.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions