Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-08-24 · high
The unofficial rebuild of the closed macOS client posted a fork-to-star ratio near 1 to 1, which almost never happens without an anticipated takedown.
Why now: The counts stood at 726 forks and 774 stars on August 24.
A source reconstruction of Grok Bot 0.18 pulled 726 forks against 774 stars in a single day. A ratio that close to 1 to 1 almost never happens with organic interest, since stars are a one-click bookmark and forks take intent to clone.
The repo bills itself as an unofficial, source-oriented rebuild of Grok Bot's closed macOS client. That description, paired with the fork spike, is what a takedown-anticipating mirror looks like. People are cloning the code fast enough that a copy survives if the original gets pulled.
The repo doesn't say how the reconstruction was built, whether it's a full decompile or something pieced together from network traffic, or whether anyone connected to Grok Bot has responded. Those gaps matter more than the star count does.
If this is a mirror play, the fork count should keep climbing even after any single copy goes offline. Watch whether GitHub takes the repo down, and how many of those 726 forks are still live a week out.
Each link below shares sources, entities, or timing with this story.
Shared entity: GitHub / Same source domain / Shared topic / What happened next / Tension
Both cover GitHub; reported by the same outlet (github.com); overlapping topics (against, fork).
Shared entity: GitHub / Same source domain / Shared topic / Earlier coverage / Tension
Both cover GitHub; reported by the same outlet (github.com); overlapping topics (against, client).
Both cover GitHub; reported by the same outlet (github.com); overlapping topics (against, closed).
Shared entity: Grok Bot / Same source domain / Shared topic / Earlier coverage
Both cover Grok Bot; reported by the same outlet (github.com); overlapping topics (describ, grok, itself).
Shared entity: GitHub / Same source domain / Shared topic / Earlier coverage
Both cover GitHub; reported by the same outlet (github.com); overlapping topics (against, fork).
Both cover GitHub; reported by the same outlet (github.com); overlapping topics (fork, itself).
Shared entity: GitHub / Same source domain / What happened next / Tension
Both cover GitHub; reported by the same outlet (github.com); picks up the GitHub thread on 2026-08-25.
Shared entity: GitHub / Shared topic / What happened next / Tension
Both cover GitHub; overlapping topics (against, closed); picks up the GitHub thread on 2026-08-25.