Claude Code · Requests and models
Auto mode is unavailable — the server returned no safety verdict
Auto mode’s safety check got no answer for ten responses in a row, so Claude Code stopped instead of acting unchecked.
Message
The exact error
Auto mode is unavailable — the server returned no safety verdict for the last 10 responses, so Claude stopped. Send a message to try again, or switch out of auto mode.Also appears as:
- For a single action
- The server-side auto mode classifier gave no verdict (timed out), so auto mode cannot determine the safety of <tool>.
Meaning
What it means
In auto mode, a classifier on Anthropic’s side reviews each action before Claude Code runs it. When the server gives no verdict, the action is denied. After ten responses in a row without a verdict, Claude Code stops the turn rather than keep trying blind. It’s a safety stop, not a crash.
Causes
Common causes
- A temporary problem with the server-side classifier
- An LLM gateway or proxy that cuts short or rewrites streaming responses, dropping the verdict
Fix
How to fix it
Send another message
Claude tries again and the count starts over.
If you use a gateway or proxy
Check that it passes streaming responses through unchanged; see Anthropic’s gateway compatibility guidance.
Use Claude Code’s own classifier requests
Set
CLAUDE_CODE_AUTO_MODE_SERVER=0before starting Claude Code.macOS / Linux export CLAUDE_CODE_AUTO_MODE_SERVER=0 claudeWindows PowerShell $env:CLAUDE_CODE_AUTO_MODE_SERVER = '0' claudeApprove actions yourself
Switch out of auto mode so Claude Code asks before each action.
Related