Documented case · 2026
Anonymous developer, work account (Claude gh case)
Oct 2026
Verified primary source
The account holder's own post, discussion or thread was opened and read in full for this entry.
His post, in full, is short: "My work GitHub account got suspended because Claude ran a bunch of gh commands in parallel. (Btw why not rate limit if it's a problem?) For days now they won't respond to my support ticket. Guess I just don't get to have a job anymore…" A work account, an AI agent's parallel CLI burst, a ticket unanswered for days, and a job on the line. Anonymous and brief, and included because it is the same AI-agent pattern as the milisp case, independently reported in the same month.
The record
- Suspended or flagged
- October 2026
- Posted
- Hacker News, October 2026
- Ticket / discussion
- Filed; no response after days
- Suspected trigger
- Claude running many gh commands in parallel (his account of it). His question in the post: why not rate-limit it, if it is a problem?
- Human reply from GitHub
- No response after days, at posting
- How it ended
- Unresolved at posting
- Duration
- Under 1 month
Suspected triggers are the account holder’s inference, never GitHub-confirmed, unless the record above says GitHub stated or confirmed it. A suspension does not by itself prove GitHub made a mistake.
Sources
First-hand post, Hacker News item 50226087, October 2026; read via search text on November 17, 2026.
Anonymous and brief; an example of the AI-agent pattern, nothing more claimed.
This entry is one of 66 in What Kind of Life Does a Flag Preserve?, a documented account of GitHub suspending a fourteen-year-old developer account and the same pattern repeating across the industry. If the same thing has happened to you, the article’s eight-step playbook is built from what actually moved these cases.