Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] "Enable auto mode?" appears even with `--dangerously-skip-permissions`

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

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…

Error Message

Error Messages/Logs

Code Example

Enable auto mode?

[warning]

> 1. Yes, and make it my default mode
  2. Yes, enable auto mode
  3. No, go back
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

When changing modes, auto mode asks for confirmation.

What Should Happen?

With --dangerously-skip-permissions enabled, it does not make sense to ask for permission for more restrictive permissions.

Error Messages/Logs

Enable auto mode?

[warning]

> 1. Yes, and make it my default mode
  2. Yes, enable auto mode
  3. No, go back

Steps to Reproduce

Run with --dangerously-skip-permissions flag then change modes with Shift+Tab.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.114

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

No response

extent analysis

TL;DR

The issue can be potentially fixed by modifying the confirmation prompt logic to account for the --dangerously-skip-permissions flag when changing modes.

Guidance

  • Review the code responsible for handling mode changes and confirmation prompts to ensure it correctly interprets the --dangerously-skip-permissions flag.
  • Verify that the flag is properly passed and recognized when the user attempts to change modes with Shift+Tab.
  • Check the version history to identify when this regression occurred and what changes might have caused it.
  • Consider temporarily disabling the confirmation prompt for auto mode when the --dangerously-skip-permissions flag is enabled as a workaround.

Example

No code snippet can be provided without more context about the codebase, but the fix would involve modifying the conditional logic around the confirmation prompt to consider the --dangerously-skip-permissions flag.

Notes

The solution may require changes to the application's logic for handling permissions and mode changes. Without access to the codebase or more detailed information about the version history, it's challenging to provide a precise fix.

Recommendation

Apply workaround: Temporarily disable the confirmation prompt for auto mode when the --dangerously-skip-permissions flag is enabled, as this aligns with the expected behavior described in the issue.

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…
#api#embedding generation#cache error#pipeline error#runtime error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] "Enable auto mode?" appears even with `--dangerously-skip-permissions`