[BUG] Auto mode denies 'Git Destructive' commands with no approval path; the non-auto prompt then recommends switching back to auto mode

What's Wrong?

In auto mode, the classifier denies a command it labels "Git Destructive" outright, with no way for the user to approve it in session. The user says "yes, do it" in chat and the same denial repeats. Leaving auto mode makes the same command show a normal approval prompt. That prompt's tip then says "auto mode handles these prompts for you - choose 'switch to auto mode' below". So the one mode that cannot ask for approval is recommended as the fix for being asked.

Related: #95370 and #97654 (no in-session override for classifier denials), #85588 (add a user-facing allow prompt). This report adds the contradictory tip on the non-auto prompt.

What Should Happen?

Either auto mode falls back to an approval prompt for classifier denials when the user is present, or the tip on the non-auto prompt does not point at auto mode for commands auto mode will refuse.

Error Messages/Logs

Auto mode, both attempts:

Permission for this action was denied by the Claude Code auto mode classifier. Reason: [Git Destructive]. If you have other tasks that don't depend on this action, continue working on those. ... If you believe this capability is essential to complete the user's request, first try a safer method. Get as much of the rest of the task done as you can, then STOP and explain to the user what you were trying to do and why you need this permission. Let the user decide how to proceed. ... To allow this type of action in the future, the user can add a Bash permission rule to their settings.

Default mode, same command, the prompt header:

Bash command
Tip: auto mode handles these prompts for you - choose "switch to auto mode" below
...
This command requires approval
Do you want to proceed?
  1. Yes
  2. Yes, and don't ask again for git push and git ls-remote commands in <repo>
  3. Yes, and switch to auto mode · auto mode handles these prompts for you
  4. No

Steps to Reproduce

1. Work in auto mode.
2. Have Claude run a local-only history rewrite, for example to change the author email on unpushed commits:

``
git rebase <base> --exec 'git commit --amend --no-edit --reset-author -q'
``

1. The classifier denies it (log above). Claude stops and asks the user to decide. The user says yes in chat. Claude retries, the same denial repeats.
2. Switch out of auto mode (shift+tab) and have Claude run the same command.
3. A normal "Do you want to proceed?" prompt appears, with the tip pointing back at auto mode.

Context: the rewrite touched eight commits that had never been pushed. It was needed because GitHub's "Block command line pushes that expose my email" setting rejected the push.

Claude Model

Fable 5.1 (claude-fable-5-1)

Is this a regression?

Unknown. First time this user hit it.

Claude Code Version

2.1.286

Platform

Anthropic API (Claude Max subscription)

Operating System

macOS 26.6.2

Terminal/Shell

ghostty, zsh