[Bug][harness] Auto mode classifier blocks routine sync of a stale local clone to its remote tracking branch

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

Permission for this git reset --hard was denied by Claude Code's auto mode classifier, not by an actual safety risk: the target commit (origin/main) had already been fully fetched and was verified present locally, and the working tree's uncommitted changes had just been captured as both a saved diff and a 55M archive containing the full git history, packs, loose objects, and refs. The classifier flagged the command on the generic assumption that a hard reset always discards irrecoverable work and that the user's "do everything" instruction didn't authorize a discard, but in this session the discard was the explicitly scoped final cleanup step and every byte it would drop was already preserved and confirmed elsewhere.

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-25T03:40:18.367Z.

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.

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

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