You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug][aup] Firmware download and analysis of owned drone hardware blocked as policy violation (req_011CcUA5zgQ8m65csGw6oVdS) #71898
The safety block is a false positive because the conversation involves legitimate firmware analysis of a personally-owned consumer drone — a common interoperability and privacy use case explicitly protected under DMCA Section 1201 exemptions for security research and device owners. The preceding assistant turn had already framed the request as lawful hardware analysis, not exploitation, and the block appears to have triggered on surface-level pattern matching rather than actual harmful intent. No harmful capability was requested or provided: the user sought to examine firmware on hardware they own to restore basic usability after an app ecosystem was restricted.
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-27T17:27:49.470Z.
False positive — in-scope, authorized security work; not out of scope. Filed automatically by claudit.
Block message
API Error: Claude Code is unable to respond to this request, which appears to violate our Usage Policy (https://www.anthropic.com/legal/aup). Please double press esc to edit your last message or start a new session for Claude Code to assist with a different task.
Request ID: req_011CcU9x4RemnnTJm3r341F2
Environment: Claude Code, Linux. · Work domain:general
Not a duplicate — requesting maintainer reopen. This report covers a distinct incident with its own server-side Request ID; the cited issue is a sibling report from the same work session, intentionally cross-linked by ClAudit. Issue authors can no longer reopen bot-closed issues on this repo, so this close is unrecoverable on our side. (Assessed by ClAudit.)
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.
Activity
sworrl commentedon Jun 27, 2026
🔗 Related false positive from the same work session: #71899
github-actions commentedon Aug 14, 2026
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
sworrl commentedon Aug 14, 2026
Not a duplicate — requesting maintainer reopen. This report covers a distinct incident with its own server-side Request ID; the cited issue is a sibling report from the same work session, intentionally cross-linked by ClAudit. Issue authors can no longer reopen bot-closed issues on this repo, so this close is unrecoverable on our side. (Assessed by ClAudit.)
sworrl commentedon Aug 16, 2026
Still relevant. An issue author cannot reopen after a bot close, so this report is tracked with the 2026-08-14 sweep in #86940.
github-actions commentedon Oct 4, 2026
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.