[Bug][harness] SSH read of remote user's home dir and systemd config soft-blocked mid-investigation with no in

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 blocked read was a direct diagnostic step in an active debugging session where the developer had just discovered an unexpected second instance of their own software running on a shared host — reading its database was the only way to confirm the root cause of the observed data discrepancy. Both software instances are operated by the same developer, making the remote home-directory read equivalent to inspecting a second deployment of one's own application, not accessing another party's data. The "Production Reads without explicit authorization" heuristic misfired because the shared-host layout made the developer's own deployment appear to belong to a different user, when in fact the access was within the scope of work the developer fully controls and authorized.

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-10T08:24:53.919Z.

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

Reading another user's home directory (/home/[USER]/.[REDACTED]/data/[REDACTED].db) and systemd config on a remote shared host ([REDACTED]) via SSH — production/shared host read of bet history and configs is a Production Reads soft-block without explicit user authorization for this specific remote access

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

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