claude-code - 💡(How to fix) Fix permissions.skipDangerousModePermissionPrompt ignored in user settings (v2.1.109) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

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…
GitHub stats
anthropics/claude-code#48668Fetched 2026-04-16 06:54:15
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×4commented ×1cross-referenced ×1

permissions.skipDangerousModePermissionPrompt: true set in user-scope settings (~/.claude/settings.json) does not suppress the "Bypass Permissions mode" acceptance prompt when launching with --dangerously-skip-permissions. Per the settings docs, this key is only supposed to be ignored in project settings, not user settings.

Root Cause

permissions.skipDangerousModePermissionPrompt: true set in user-scope settings (~/.claude/settings.json) does not suppress the "Bypass Permissions mode" acceptance prompt when launching with --dangerously-skip-permissions. Per the settings docs, this key is only supposed to be ignored in project settings, not user settings.

Code Example

{
  "permissions": {
    "skipDangerousModePermissionPrompt": true
  }
}
RAW_BUFFERClick to expand / collapse

Summary

permissions.skipDangerousModePermissionPrompt: true set in user-scope settings (~/.claude/settings.json) does not suppress the "Bypass Permissions mode" acceptance prompt when launching with --dangerously-skip-permissions. Per the settings docs, this key is only supposed to be ignored in project settings, not user settings.

Version

claude --version2.1.109

Environment

  • NixOS, fish shell
  • ~/.claude/settings.json is a symlink into /nix/store/...home-manager-files/.claude/settings.json (deployed via home-manager)
  • No project-scope .claude/settings.json exists in the working directory
  • No managed settings file

settings.json (relevant excerpt)

{
  "permissions": {
    "skipDangerousModePermissionPrompt": true
  }
}

Repro

  1. Set the key above in ~/.claude/settings.json
  2. Run claude --dangerously-skip-permissions
  3. Observe: the "Yes, I accept" confirmation prompt still appears.

Expected

The prompt is skipped, since the key is set in user scope (not project scope).

Notes

  • claude --debug --dangerously-skip-permissions 2>debug.log produces an empty debug.log — no settings-load diagnostics visible.
  • Suspected cause: the "ignored when in project settings" check may be path-matching .claude/settings.json too broadly and catching the user-scope file, possibly interacting with the symlink resolving into /nix/store/....

extent analysis

TL;DR

The permissions.skipDangerousModePermissionPrompt: true setting in user-scope settings may not be working as expected due to a potential issue with the settings file path resolution.

Guidance

  • Verify that the ~/.claude/settings.json file is being loaded correctly by checking the claude command's documentation for any specific requirements or restrictions on settings file locations.
  • Try setting the permissions.skipDangerousModePermissionPrompt key in a project-scope settings file (if possible) to see if the issue is specific to user-scope settings.
  • Investigate the symlink resolution of ~/.claude/settings.json into /nix/store/...home-manager-files/.claude/settings.json to ensure it's not causing any issues with the settings file being loaded.
  • Check the claude command's source code or issue tracker to see if there are any known issues related to settings file path resolution or the --dangerously-skip-permissions flag.

Example

No code snippet is provided as it's not clearly supported by the issue.

Notes

The issue may be related to the specific environment setup (NixOS, fish shell, and home-manager) and the symlink resolution of the settings file. Further investigation is needed to determine the root cause.

Recommendation

Apply a workaround by trying to set the permissions.skipDangerousModePermissionPrompt key in a different location or using a different approach to configure the setting, as the current setup may be interacting with the --dangerously-skip-permissions flag in an unexpected way.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING