Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Add "Always allow globally" option to permission prompts

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Root Cause

MCP tools like Jira, Google Calendar, Slack, and GitHub are used across every project, not just one. Having to re-approve them per project, or maintain the global allowlist by hand, creates unnecessary friction. The project-level option makes sense for project-specific tools; a global option is the natural complement for user-level tools.

RAW_BUFFERClick to expand / collapse

When Claude Code surfaces a permission prompt for a tool (especially MCP tools), the current options are:

  • Allow once
  • Always allow in this project (writes to .claude/settings.json)
  • Deny

There's no way to allow a tool globally across all projects from this prompt. The only path today is to manually edit ~/.claude/settings.json after the fact — or open a new session and repeat the process there.

Proposed change

Add a fourth option: "Always allow globally" — which writes the permission rule to ~/.claude/settings.json instead of the project settings file.

Why this matters

MCP tools like Jira, Google Calendar, Slack, and GitHub are used across every project, not just one. Having to re-approve them per project, or maintain the global allowlist by hand, creates unnecessary friction. The project-level option makes sense for project-specific tools; a global option is the natural complement for user-level tools.

Expected behavior

Selecting "Always allow globally" writes the tool name to ~/.claude/settings.json under permissions.allow, identical to what "Always allow in this project" does for .claude/settings.json.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Selecting "Always allow globally" writes the tool name to ~/.claude/settings.json under permissions.allow, identical to what "Always allow in this project" does for .claude/settings.json.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING