[BUG] Bash safety classifier intermittently unavailable on claude-opus-4-7, blocks tool calls

Resolved 💬 3 comments Opened May 25, 2026 by karthik0899 Closed Jun 26, 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?

The Bash safety classifier (claude-opus-4-7) intermittently returns "temporarily unavailable" and blocks Bash tool calls in auto mode.

The error message reads:

▎ claude-opus-4-7 is temporarily unavailable, so auto mode cannot determine the safety of Bash right now. Wait briefly and then try this action again. If it keeps failing, continue with other tasks that don't require this action and come back to it later.

Same command retried seconds later sometimes succeeds, sometimes fails again with the same message. Some commands in the same session pass through (e.g. echo "test") while others fail (e.g. node /tmp/script.mjs) with
no obvious safety difference between them. This has been happening intermittently over the past ~hour.

What Should Happen?

The safety classifier should respond within a reasonable timeout. If it's truly unavailable, the harness should either:

  • queue/retry transparently, or
  • fail fast on tool calls but surface a clearer "service degraded" indicator instead of blocking individual Bash calls.

Trivial commands (echo, ls, node /tmp/foo.mjs) shouldn't repeatedly fail safety checks when no policy is being violated.

Error Messages/Logs

claude-opus-4-7 is temporarily unavailable, so auto mode cannot determine the safety of Bash right now. Wait briefly and then try this action again. If it keeps failing, continue with other tasks that don't require
  this action and come back to it later. Note: reading files, searching code, and other read-only operations do not require the classifier and can still be used.

Steps to Reproduce

  1. Start a Claude Code session in auto mode using model claude-opus-4-7.
  2. Run any benign Bash command via the Bash tool (e.g. node /tmp/test.mjs where the file exists and is harmless).
  3. Intermittently — not every call — the classifier returns "temporarily unavailable" and the tool call is blocked before execution.
  4. Retrying the same command works sometimes; other times it fails again with the identical message.

Cannot reliably reproduce — appears tied to classifier service availability rather than command content.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.150 (Claude Code)

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Warp

Additional Information

  • The classifier's failure mode blocks individual Bash tool calls but does not crash the session. Read-only tools (Read, Grep, Edit) continue working normally.
  • The error message itself is helpful — it explicitly says read-only ops are unaffected. The issue is just the intermittent unavailability of the classifier service for Bash.
  • No reproduction available involving file permissions / EACCES — that text from the form template doesn't apply to this bug.

---
A few fields you'll need to fill yourself from your machine:

  • Claude Code Version → run claude --version
  • Platform → which API platform you're on (Anthropic / Bedrock / Vertex)
  • The "What's Wrong?" template they pre-populated mentions EACCES on Python files — that's an example template; replace it entirely with the content above (your actual issue is different).

View original on GitHub ↗

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