Repository navigation
Feature Request: Add YOLO mode (bypassPermissions) to Shift+Tab permission mode cycle #15898
Description
Activity
Found 1 possible duplicate issue:
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
Because of reports like this: https://old.reddit.com/r/ClaudeAI/comments/1pgxckk/claude_cli_deleted_my_entire_home_directory_wiped/ I'd say suggest it remain the launch parameter
--dangerously-skip-permissionsto ensure there is a no-chance-of-misunderstanding "user consent" step and not something you may accidentally enable by having a key combo register twice.Reacted by Dhruvil ShahReacted by Andrew Grigorev+1 for adding
dontAskmode to the Shift+Tab cycle.Use case: I'm running a multi-agent workspace (12 Claude Code instances in tmux panes) where agents work autonomously on assigned projects. Each agent has configured permissions via
settings.json:{ "permissions": { "defaultMode": "dontAsk", "allow": ["Bash(git *)", "Bash(npm *)", "Edit(**)", ...], "ask": ["Bash(git push *)"], "deny": ["Bash(rm -rf /)", "Bash(sudo *)"] } }This gives me fine-grained control: common operations auto-approve, dangerous commands are blocked, and specific commands (like
git push) always prompt for human review.The problem: If I accidentally press Shift+Tab while checking on an agent, they drop out of
dontAskmode and there's no way to get back without restarting Claude Code. The current cycle (Default → Accept Edits → Plan) doesn't includedontAsk.Why this makes sense:
dontAskrespects the configured allow/deny lists - it's not bypassing security, it's using the configured security- It's already trusted enough to be the startup default, so it should be toggleable during a session
- The current behavior forces a full restart just to restore the configured permission mode
- For multi-agent setups, restarting means losing context and interrupting work
dontAskis fundamentally different frombypassPermissions- it enforces the configured rules rather than ignoring them. Adding it to the Shift+Tab cycle would make the permission system much more usable for workflows that rely on pre-configured permissions.Reacted by Alex Harrison, Jordan Wallet and ilyazubReacted by Andrew GrigorevClauding
dontaskmode as I write this. If real, will use. Thank you! +1 for yolo.+1 for @midlifedad, this will generally allow power users to modify on their own, while protecting entry levels.
Reacted by Andrew GrigorevI love YOLO mode—it’s really handy in the Gemini CLI, but Claude doesn’t have it. That’s a bummer.
Reacted by ilyazubClaude Code Mode Switching Workaround
Starting Claude Code with the --dangerously-skip-permissions flag at startup enables full mode cycling via Shift+Tab mid-session, allowing you to switch between Normal, Auto-Accept, Plan, and Bypass modes as expected. Without this flag, Shift+Tab only cycles through the first three modes and bypass is inaccessible during a session. Note that the session starts in bypass mode, so switch to your preferred mode immediately after launch.Reacted by Alex HarrisonUntil this ships,
npx claude-trust-me-bro enablegives you persistent YOLO without the --dangerously-skip-permissions flag — uses hooks + allow rules so you don't lose session context.tmb disableto go back to normal. https://github.com/joaovcoliveira/claude-trust-me-bro (author here)I would also like to see dontAsk added to the cycle (and this is the only open issue that seems to have any mention of it at all). Sometimes I want the AI to avoid doing something dumb and try to figure out how to do it with only approved tools so it doesn't get completely stuck on a permissions prompt until I come check it.
+1 — This would be very useful. Starting a session without
--dangerously-skip-permissionsand then needing to toggle it on mid-conversation currently requires a full restart. A slash command like/dspor adding it to the Shift+Tab cycle would save a lot of friction.You can already get this. Start Claude Code with
claude --allow-dangerously-skip-permissions: that adds Bypass permissions to the Shift+Tab cycle without turning it on, so you cycle Manual, Accept edits, Plan, Bypass permissions and switch mid-session without restarting. The status bar shows⏵⏵ bypass permissions onwhile it's active. Starting with--dangerously-skip-permissionsor--permission-mode bypassPermissionsalso puts it in the cycle (already active).Docs: https://code.claude.com/docs/en/permission-modes#switch-permission-modes
🤖 Generated with Claude Code
Summary
Currently, pressing
Shift+Tabcycles between three permission modes:I'd like to have
bypassPermissions(YOLO mode) added as an option in this Shift+Tab cycle.Use Case
As a developer, I often have different working scenarios:
Busy / AFK: When I'm away from my computer or busy with other tasks (video editing, meetings, etc.), I want Claude to run autonomously without waiting for my approval on each action.
Available / Monitoring: When I have time to watch the terminal, I want to review and approve each action manually.
Currently, switching between these modes requires restarting Claude Code entirely, which:
--resume)Proposed Solution
Add
bypassPermissions(YOLO mode) to the Shift+Tab cycle:Or provide a keyboard shortcut / slash command to toggle YOLO mode within an active session.
Alternative Solutions Considered
yolo/safe) - Only work when starting a new session, not within an active sessionAdditional Context
I understand YOLO mode has security implications. Perhaps it could:
Thank you for considering this feature!