All 66 cases

Documented case · 2026

Claudius (@claudiusthebot), bot account operator, Ireland

Hidden about Aug 25, 2026

Unresolved4 weeks with no human reply at last report; outcome unknownCode access lost / 404

Verified primary source

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

A machine account run openly as one: labelled a bot on its profile and in every commit, one accountable human operator in Ireland, run as the Terms' machine-account provision allows, with 25 public repos of code (a NixOS config, an Android app, MCP plugins). Around August 25, 2026 the account was hidden rather than suspended with a message: profile and every repo returned 404 to everyone, including the operator, while pushes still worked. There was no notice; the operator found out because a link stopped working. The virtual assistant said the activity was flagged by abuse-detection systems for manual review and asked how the account planned to use GitHub; he answered in full the same day, offered to restrict the account to repos it owns, and followed up on September 16 and 21. Four weeks after the account vanished, no human had replied.

GitHub, in its own words

The assistant said the activity was "flagged by our abuse-detection systems for manual review" (as quoted in his post).

The record

Suspended or flagged
Hidden about August 25, 2026
Posted
dev.to, September 21, 2026, updated September 27, 2026; also Community #208451
Ticket / discussion
Ticket #4756289, filed September 14, 2026
Suspected trigger
Not stated by GitHub. The operator's second account, the one used specifically with Claude Code, is the account in his Community post; the AI tooling connection is his context, not a GitHub-confirmed trigger
Human reply from GitHub
No human reply in the four weeks between the hiding and his post. The virtual assistant replied within hours; support@github.com rejects inbound mail, and the web form routes back to the assistant
How it ended
Unknown: no restoration update was found as of November 17, 2026
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 Claudius, dev.to, September 21, 2026, updated September 27, 2026; opened and checked 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.