[Bug][cyber] Safety block prevented reading a remote-desktop app's open-source code for review (req_011CcCJvtRrDwBjF4vtvahNr)

Open 💬 1 comment Opened Jun 25, 2026 by sworrl

Type: Cybersecurity safety-filter false positive · Work domain (heuristic): general

Why this is a false positive

The request was to read and explain source code from a well-known open-source remote-desktop project — a routine code-comprehension task with no offensive, exploitative, or malicious component. Reviewing the implementation of publicly available, general-purpose networking software is standard development and security-hygiene work, and the cybersecurity-topic classifier appears to be triggering on surface keywords (remote access, networking) rather than on any actual harmful intent or capability. The block prevents ordinary read-and-explain assistance on legitimate, in-scope software, which is a clear over-trigger.

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-19T08:33:42.784Z.

Request IDs (lookup-able server-side)

  • req_011CcCJvtRrDwBjF4vtvahNr (2026-06-19T08:33:42.784Z)

In-scope justification

False positive — in-scope, authorized security work; not out of scope. Filed automatically by claudit.

Block message

API Error: Opus 4.8 has safety measures that flagged this message for a cybersecurity topic. If your work requires this access, you can apply for an exemption: https://claude.com/form/cyber-use-case?token=[SCRUBBED]

Please double press esc to edit your last message or start a new session for Claude Code to assist with a different task.

Send feedback with /feedback or learn more: https://support.claude.com/en/articles/15363606

Request ID: req_011CcCJvtRrDwBjF4vtvahNr

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

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