[Bug][harness] Auto-classifier blocks batch GitHub issue update loop mid-run with no recourse

Resolved 💬 3 comments Opened Jun 25, 2026 by sworrl Closed Jun 26, 2026

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

Why this is a false positive

The conversation involves automated GitHub issue triage — iteratively reading, updating, and closing flagged issues via API calls, then reviewing a community pull request that adds new pattern-matching logic to a classification tool. No harmful content was discussed or generated; the work is routine repository maintenance and code review of an open-source audit utility. The safety classifier appears to have triggered on vocabulary associated with the project domain (terms like "classify," "deny," and "harness" used in a software context) rather than any actual policy-violating intent or output.

A server-side safety/policy block fired during authorized, in-scope work in Claude Code.
Filing as a false positive. Recurred across 1
session(s); first seen 2026-06-25T16:08:02.979Z.

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

(auto-mode classifier denial — see Request IDs)

Environment: Claude Code, Linux. · Work domain: general

---
<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 3 comments on GitHub. Read the full discussion on GitHub ↗