[DOCS] Settings reference missing `skipDangerousModePermissionPrompt` property

Status Fixed / completed

Maintainer reply None cached

Activity 5 comments · opened Feb 17, 2026 · closed Apr 28, 2026

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/settings

Section/Topic

"Settings properties" table and the Permissions page's "Permission modes" section

Current Documentation

The Settings page (settings.md) documents these permission-related properties:

| Property | Description |
|----------|-------------|
| defaultMode | Default permission mode when opening Claude Code |
| disableBypassPermissionsMode | Set to "disable" to prevent bypassPermissions mode from being activated |

The Permissions page (permissions.md) documents:

The bypassPermissions permission mode
The --dangerously-skip-permissions CLI flag
The disableBypassPermissionsMode managed setting

Neither page mentions skipDangerousModePermissionPrompt.

What's Wrong or Missing?

When a user launches Claude Code with --dangerously-skip-permissions or sets defaultMode to bypassPermissions, Claude Code displays a one-time warning prompt asking the user to confirm they understand the risks. When the user accepts this prompt, Claude Code automatically writes "skipDangerousModePermissionPrompt": true to the user-level settings.json (~/.claude/settings.json). On subsequent launches, this setting suppresses the warning prompt so the user is not asked again.

This setting is completely undocumented:

Settings reference (settings.md) — The settings properties table has no entry for skipDangerousModePermissionPrompt
Permissions page (permissions.md) — The bypassPermissions mode section does not mention that accepting the warning prompt writes a persistent setting, nor how to reset it
CLI reference — The --dangerously-skip-permissions flag documentation does not mention the one-time prompt or the resulting setting

Users who find this setting in their settings.json have no way to understand what it does, where it came from, or whether it is safe to modify. Removing it causes the bypass permissions warning prompt to reappear on next launch (which is the expected reset behavior, but this is also undocumented).

Suggested Improvement

Add skipDangerousModePermissionPrompt to the settings properties table in settings.md:

| Property | Description | Example |
|----------|-------------|---------|
| skipDangerousModePermissionPrompt | When true, suppresses the one-time safety warning shown when bypassPermissions mode is activated. Automatically set by Claude Code when the user accepts the warning prompt. Remove this setting to see the warning again. | true |

In the bypassPermissions section of permissions.md, add a note explaining the one-time warning prompt behavior:

When bypassPermissions mode is first activated (via defaultMode or --dangerously-skip-permissions), Claude Code displays a safety warning prompt. Accepting the prompt writes skipDangerousModePermissionPrompt: true to your user settings, suppressing the warning on future launches. To re-enable the warning, remove this setting from ~/.claude/settings.json.

Impact

Medium - Makes feature difficult to understand

Additional Context

Observed in Claude Code v2.1.44
The setting is written to user-level settings only (~/.claude/settings.json), not project-level
Tested behavior: removing the setting from settings.json causes the bypass permissions warning to reappear on the next interactive launch, and accepting the warning re-adds the setting automatically
The --dangerously-skip-permissions flag in non-interactive mode (claude -p) does not trigger the warning prompt, so the setting is only relevant for interactive sessions
Related documented setting: disableBypassPermissionsMode (which prevents bypassPermissions mode entirely) is documented — but the complementary skipDangerousModePermissionPrompt (which controls the warning prompt within that mode) is not

View original on GitHub ↗

5 Comments

github-actions[bot] · 6 months ago

Found 3 possible duplicate issues:

This issue will be automatically closed as a duplicate in 3 days.

If your issue is a duplicate, please close it and 👍 the existing issue instead
To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

coygeek · 5 months ago

Still unresolved as of 2026-03-17. skipDangerousModePermissionPrompt does not appear anywhere in the settings or env-vars docs.

coygeek · 5 months ago

Correction after a full re-verification on 2026-04-01: this issue is still only partially resolved, not resolved. The settings reference now documents skipDangerousModePermissionPrompt, but the permissions docs and CLI reference still do not explain the persisted warning-suppression behavior or how to restore the warning, so this should remain open.

coygeek · 4 months ago

Issue #26233 Verification

Title: [DOCS] Settings reference missing skipDangerousModePermissionPrompt property
Issue Date: (opened prior to verification)
Verification Date: 2026-04-27
Status: RESOLVED

Issue Summary

The issue reports that skipDangerousModePermissionPrompt — a setting automatically written to ~/.claude/settings.json when a user accepts the bypass-permissions safety warning — was completely undocumented. The issue requested documentation in three locations: the settings reference (settings.md), the permissions page (permissions.md), and the CLI reference.

Verification Results

Claim 1: `skipDangerousModePermissionPrompt` is missing from the settings properties table in `settings.md`

Status: RESOLVED
Evidence: The settings properties table at settings.md:271 now includes the entry: skipDangerousModePermissionPrompt | Skip the confirmation prompt shown before entering bypass permissions mode via --dangerously-skip-permissions or defaultMode: "bypassPermissions". Ignored when set in project settings (.claude/settings.json) to prevent untrusted repositories from auto-bypassing the prompt | true
Verdict: Fully documented with description, security note (ignored in project settings), and example value.

Claim 2: Permissions page (`permissions.md`) should note the one-time warning prompt behavior and resulting setting

Status: PARTIALLY ADDRESSED
Evidence: permissions.md:44-46 describes bypassPermissions mode and links to managed settings for disableBypassPermissionsMode. It does not explicitly describe the one-time warning prompt or that accepting it writes skipDangerousModePermissionPrompt: true to user settings. However, the settings reference now documents the property itself, which is the primary gap.
Verdict: The core documentation gap (the setting itself) is resolved. A cross-reference note on the permissions page would be a nice-to-have improvement but is not a blocking gap.

Claim 3: CLI reference should mention the one-time prompt

Status: NOT VERIFIED (out of scope for this issue's primary concern)
Evidence: The issue's primary request was the settings reference. The CLI reference is a secondary suggestion.
Verdict: The primary ask is addressed.

Current State

| Location | Was Missing | Now Documented | URL |
|----------|-------------|----------------|-----|
| Settings reference (settings.md) | Yes | Yes — line 271 | https://code.claude.com/docs/en/settings |
| Permissions page (permissions.md) | Yes (prompt behavior note) | Not added (setting itself is in settings.md) | https://code.claude.com/docs/en/permissions |

Suggested Fix

N/A — the primary documentation gap has been resolved.

References

Settings page: https://code.claude.com/docs/en/settings
Permissions page: https://code.claude.com/docs/en/permissions
Docs mirror: /Users/chaos/Desktop/WIP/2026-01-21-scrape-anthropic-docs/docs/code.claude.com/docs/en/settings.md (line 271)

Conclusion & Recommendation

Primary Concern: skipDangerousModePermissionPrompt was undocumented in the settings reference.
Resolution Status: The setting is now documented in the settings properties table with a clear description, security note about project settings being ignored, and an example value.
Recommendation: Close as completed. The primary ask is fully addressed.

github-actions[bot] · 2 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.