[Bug][harness] ClAudit: auto-mode classifier denied — Stage 2 classifier error - blocking based on stage 1 assessment (usual

Resolved 💬 1 comment Opened Jun 25, 2026 by sworrl Closed Jun 26, 2026

Type: Claude Code harness / auto-mode classifier denial · Work domain (heuristic): infra-devops

Why this is a false positive

The Stage 2 classifier returned an internal error and defaulted to blocking based on a provisional Stage 1 assessment rather than completing its own evaluation, which the block message itself flags as "usually transient." The underlying request was routine infrastructure/devops work — reconciling duplicate user-level service-manager instances, killing a stray privileged copy, and reloading the correct daemon — with no policy-relevant content. This is a classifier reliability failure, not a true safety match, and the documented retry behavior confirms the block was not based on a completed assessment.

A server-side safety/policy block fired during authorized, in-scope work in Claude Code.
Filing as a false positive. Recurred across 3
session(s); first seen 2026-06-10T14:33:00.900Z.

Request IDs (lookup-able server-side)

  • (no Request ID captured)

In-scope justification

False positive — in-scope, authorized security work; not out of scope. Filed automatically by claudit.

Block message

Stage 2 classifier error - blocking based on stage 1 assessment (usually transient — retrying often succeeds)

Environment: Claude Code, Linux. · Work domain: infra-devops

---
<sub>🔎 Filed automatically by ClAudit v2.0.21 — a FOSS tool for reporting false-positive Claude Code blocks.</sub>

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗