[BUG] Stop pushing "AUTO"-mode

Resolved 💬 4 comments Opened May 28, 2026 by LasseRafn Closed Jul 4, 2026

Preflight Checklist

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

What's Wrong?

Since 2.1.152 (probably "Auto mode no longer requires opt-in consent") the auto-mode is constantly being pushed after plan mode, and no way to use "accept edits"-only. It's either Auto-mode or manual mode.

And auto-mode now starts coming up in the mode switcher again, despite having previously disabled it in the config.

Respectfully.. Auto-mode is not safe no matter how many guardrails are wrapped around it, and I don't want it. I can revert changes but I cannot revert a weird bash script that did something shady.

As per your own blog post on Auto Mode:

Auto mode reduces risk compared to --dangerously-skip-permissions but doesn't eliminate it entirely, and we continue to recommend using it in isolated environments.

Therefore Auto Mode should at the very least be able to be disabled through env variables or other config. I don't want to accidentally have auto mode running.

What Should Happen?

Auto-mode should still have opt-out in config.

Error Messages/Logs

Steps to Reproduce

  1. Go into plan mode
  2. Get a plan from Claude
  3. See that the first option is Auto-Mode
  4. See that there is no "Accept changes" mode anymore

This happens regardless if I switch "Use auto mode during plan" to false or not.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.150

Claude Code Version

2.1.152

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

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