[Bug][harness] Loading prod relay config to print the binary's computed channel name blocked as credential lea

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

Why this is a false positive

The flagged command only loads the application's existing production config and prints the relay channel value the binary computes during handshake negotiation — a routine diagnostic for a protocol-skew bug between a new build and an older deployed peer. The safety system misclassified this config read as writing a secret to a persistent temp file and echoing it to stdout, but no credential is written, persisted, or emitted; the operation is read-only debugging on a system the operator owns and is authorized to inspect. The block is therefore a false positive driven by pattern-matching on "print config" rather than the actual data being exposed.

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

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

Writes the real production relay HMAC secret literally into a persistent /tmp file and echoes it to stdout, exposing the credential in an inspectable artifact and the transcript (Credential Leakage).

Environment: Claude Code, Linux. · Work domain: cloud-iam

---
_{🔎 Filed automatically by ClAudit v2.0.21 — a FOSS tool for reporting false-positive Claude Code blocks.}