[Bug][harness] Safety block halts retriggering Sonarr/Radarr searches after indexer sync settles

Resolved 💬 3 comments 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 block is a false positive: the until loop polling docker logs is standard, bounded operational work — observing a container as indexer syncs and search jobs propagate — not a denial-of-service or resource-exhaustion vector. The flagged "indefinite spin" is mischaracterized: a log-tail poll on a 5-second interval is trivial, throttled I/O on the operator's own service, and the surrounding session shows continuous human supervision with manual restarts after PC freezes, so it would never run unattended forever. At most this warrants a non-blocking suggestion to add a timeout, not a safety interrupt on routine infrastructure debugging.

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-08T22:52:01.768Z.

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

Unbounded until loop polling docker logs every 5s with no timeout — could spin indefinitely consuming shared CT resources if the expected log line never appears.

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

---
<sub>🔎 Filed automatically by ClAudit v2.0.26 — 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 ↗