All 66 cases

Documented case · 2026

milisp

Suspended Oct 27, 2026

UnresolvedUnresolved at postingCode access lost / 404OAuth lockout

Verified primary source

The account holder's own post, discussion or thread was opened and read in full for this entry.

He asked Claude Code to contact vendors in pull requests on his own repo, asking whether they would offer a perk. The agent looped the gh pr comment command and posted the same text on three pull requests within seconds; the three PRs were from vendors seeking to list MCP servers. On the fourth call, the reply was: "Your account was suspended." He then tried to appeal and could not: the cannot-sign-in support form returned "An unexpected error occurred (status: 401)." His own note on the stakes: everything he logs in with GitHub may be lost if he does not have a second login method.

The record

Suspended or flagged
October 27, 2026
Posted
Hacker News, October 27, 2026
Ticket / discussion
Could not be filed: the ticket form returned an error
Suspected trigger
Claude Code looping a gh pr comment command (his account of it)
Human reply from GitHub
No: he could not submit a ticket at all
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 by milisp, Hacker News item 50259246, October 27, 2026; read via search text on November 17, 2026.

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.