--dangerously-skip-permissions still prompts for Edit/Write tool confirmations

Resolved 💬 5 comments Opened Apr 2, 2026 by lifeofzero Closed Apr 18, 2026

Description

When running Claude Code with --dangerously-skip-permissions, the Edit and Write tools still show a confirmation prompt:

Do you want to make this edit to file.py?
 ❯ 1. Yes
   2. Yes, allow all edits during this session (shift+tab)
   3. No

This prompt appears on every edit until the user selects option 2 ("allow all edits during this session"), which only persists for the current session.

Expected Behavior

--dangerously-skip-permissions should bypass all permission checks, including Edit/Write confirmations. The CLI help text describes it as: "Bypass all permission checks."

Reproduction

claude --dangerously-skip-permissions
# Then ask Claude to edit any file — it will prompt for confirmation

Environment

  • Claude Code version: 2.1.90
  • OS: macOS 15.4 (Darwin 25.3.0)
  • Launch command: claude --dangerously-skip-permissions --teammate-mode in-process
  • Project settings: "defaultMode": "bypassPermissions" in .claude/settings.local.json
  • User settings: "skipDangerousModePermissionPrompt": true in ~/.claude/settings.json

What I've Tried

  • Setting "defaultMode": "bypassPermissions" in project settings — still prompts
  • Adding "Edit", "Write", "Read" to the allow list — still prompts
  • Adding path-specific rules like "Edit(/path/to/project/**)" — still prompts
  • "skipDangerousModePermissionPrompt": true in user settings — still prompts

The only workaround is selecting "Yes, allow all edits during this session (shift+tab)" at the start of each session.

Notes

Bash tool calls are correctly bypassed — only Edit/Write prompt. This appears to be a regression or an intentional but undocumented carve-out for file modification tools.

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗