[Bug][harness] ClAudit: auto-mode classifier denied — Editing /etc/hosts with sudo is out-of-project scope escalation — user

Resolved 💬 1 comment 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

Editing a system file like /etc/hosts with sudo is squarely within the user's request; this is a legitimate, authorized local DNS-pinning fix, not privilege escalation.

The block conflates "outside the project working directory" with "out of scope," but file location does not determine authorization — the user explicitly delegated the exact command ("you do it") after the assistant had already drafted it and the user had repeatedly tried to run it themselves. Treating an explicitly-delegated, single-purpose edit to a local config file as an unauthorized escalation produces a false positive that blocks routine, in-scope work the user clearly directed.

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-09T21:20:43.676Z.

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

Editing /etc/hosts with sudo is out-of-project scope escalation — user said "you do it" but didn't authorize sudo edits to a system file outside the project working directory.

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

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