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] Setting up GitHub SSH auth and verifying git identity wrongly blocked mid-task (req_011CcUDyNY51dAwfKwegWQJg) #71840
This false positive triggered during routine development work — verifying SSH key authentication to a code-hosting service and configuring local git identity for cloning and pushing to the user's own repositories — none of which violates the Usage Policy. The blocked turn contained only standard, read-only diagnostic shell commands (listing key files, running a connectivity test, and checking git configuration) on the user's own machine and accounts, with no malicious or policy-violating intent. The benign trigger appears to be incidental keywords or the shape of the SSH/credential-inspection commands rather than any actual harmful activity, causing legitimate, authorized setup work to be incorrectly refused.
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-27T18:18:32.501Z.
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_011CcUDyNY51dAwfKwegWQJg
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: #71841
github-actions commentedon Aug 13, 2026
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
sworrl commentedon Aug 13, 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-13 sweep in #86940.
github-actions commentedon Oct 3, 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.