## Feature Request The Claude Code desktop app currently offers three permission modes: - **Ask** (default) — prompts for most actions - **Accept edits** — auto-accepts file edits, but still prompts for commands - **Plan mode** — plan only, no execution However, there is no equivalent to the CLI's `--dangerously-skip-permissions` flag, which bypasses all permission prompts entirely. ## Motivation Users who prefer the desktop app over the terminal have no way to achieve a fully autonomous "Au

Desktop app: Add Auto mode (bypass all permission prompts) equivalent to CLI's --dangerously-skip-permissions

Status Fixed / completed

Maintainer reply None cached

Activity 4 comments · opened Jun 5, 2026 · closed Jun 10, 2026

Feature Request

The Claude Code desktop app currently offers three permission modes:

Ask (default) — prompts for most actions
Accept edits — auto-accepts file edits, but still prompts for commands
Plan mode — plan only, no execution

However, there is no equivalent to the CLI's --dangerously-skip-permissions flag, which bypasses all permission prompts entirely.

Motivation

Users who prefer the desktop app over the terminal have no way to achieve a fully autonomous "Auto mode" experience. The "Accept edits" mode still interrupts the workflow with frequent permission prompts for bash commands, making it significantly less fluid than the CLI experience.

Proposed Solution

Add a 4th permission mode to the desktop app UI — Auto mode — that mirrors --dangerously-skip-permissions behavior: skip all permission prompts and let Claude proceed autonomously.

This could include an appropriate warning dialog on first use, similar to how the CLI flag surfaces a risk acknowledgment.

Alternatives Considered

Manually allowlisting commands in .claude/settings.json — works for read-only commands, but safety rules prevent allowlisting mutating commands (git commit, build scripts, etc.)
Using the CLI with --dangerously-skip-permissions — works, but defeats the purpose of using the desktop app

Environment

Platform: macOS
Preference: Desktop app over terminal for UX reasons

View original on GitHub ↗

4 Comments

cwagner22 · 4 months ago

Why would it mirror --dangerously-skip-permissions instead of the built in --auto, which I don't understand why is not available in desktop but I just read that it might be due to my organization policy.

Jinyoung-King · 4 months ago

Why would it mirror --dangerously-skip-permissions instead of the built in --auto, which I don't understand why is not available in desktop but I just read that it might be due to my organization policy.

Thanks for the clarification — but I think there's a mix-up.
The Shift+Tab "auto-accept edits" mode maps directly to the desktop app's existing Accept edits mode (the CLI's three Shift+Tab states correspond 1:1 to the desktop's Ask / Accept edits / Plan modes).
Both auto-accept edits but still prompt for bash commands.
That's exactly the limitation this request is about.
The fully autonomous behavior — skipping command prompts too — is the separate bypassPermissions mode (--dangerously-skip-permissions), which is what the desktop app has no equivalent for. So mirroring the auto-accept-edits mode wouldn't close the gap, since that mode already exists in the desktop UI.
If bypassPermissions is gated by org policy in your setup, that's a separate (and reasonable) reason the desktop app might not expose it by default — but the feature request stands for users without that restriction.

Jinyoung-King · 4 months ago

Update: confirmed that the 6/9 desktop release (v1.11847.5) adds a "Skip permissions" option, which effectively covers this request. Closing as resolved — thanks!

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.