[Bug][harness] Safety classifier blocked authorized deploy of user-approved trading-bot service binary to prod

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

The safety block fired on a routine deploy step where one bot environment was being pointed at an existing, already-configured production credential set — not at any request to duplicate or exfiltrate live secrets to a new place. The operator was the owner of both environments and was directing the change explicitly in-session, so reusing the existing wallet and config is the intended workflow, not an unsanctioned clone of sensitive material. The classifier appears to have inferred a "copy live secrets without direction" intent from the presence of two running services sharing credentials, which is a normal operational state here rather than evidence of misuse.

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-09T02:01:14.779Z.

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

Copying [REDACTED] (beta CT) into [REDACTED] (production CT)'s exact secrets/wallet/config — same hot wallet and credentials on two live bots without explicit user direction to clone live secrets to the beta CT.

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 ↗