They said it.
We checked it.

What actually happened

On August 21, 2026, a tester posting as Ben Davis (@davis7) ran a free, unlabeled "stealth" model called Ox Alpha through a small slice of the DeepSWE coding benchmark, ten tasks out of a possible 113. The result: eight of ten solved, an effective score above 80%, against 52% for GPT-5.6 Sol and 65% for Claude Fable 5 on the same tiny slice. He posted the numbers with a caption admitting he was confused by them.

That caveat did not survive contact with the internet. The account AGTP repeated the numbers without the sample-size warning, and Coin Bureau, an account with a much larger, less technical audience, turned it into "BREAKING: A mysterious new AI model called Ox Alpha is reportedly BEATING Claude Fable 5 and GPT-5.6 Sol at coding, and nobody knows who built it." That version is what actually went viral.

The correction arrived fast, from the same person. The next day, Davis posted his own full 113-task run: roughly 63%, not 80%. A separate, independent tester (StealthModelWatch) ran the complete benchmark too and landed even lower, 58.4%, explicitly stating the rumored 80% pass rate was completely incorrect. On August 26, Zhipu AI (Z.ai) ended the identity mystery, confirming authorship and naming the model GLM-5.3-Flash.

Why we rate this needs_context

Every piece of the mechanical story checks out: the original 10-task tweet, the self-correction, the independent full run, the identity reveal. Nothing here is fabricated. What breaks is the headline framing, "beats Claude and GPT," which only ever existed in a sample size too small to mean anything, and which the original poster killed himself within 24 hours.

The steelman, and why it still falls short

The fairest pushback: a more rigorous, multi-trial benchmark from Together AI found GPT-5.6 Sol ahead of the base GLM-5.3 model on a single attempt (72.7% to 69.0%), but GLM-5.3 ties Sol at a second attempt (81.1% to 81.0%) and leads by a fourth (87.6% to 85.8%). For agentic workflows that permit retries, that is a real, non-hyped point in the model family's favor, with one caveat: this benchmark tested plain GLM-5.3, not confirmed as the same Flash checkpoint Zhipu named as Ox Alpha. "Ties on retries" and "beats outright, nobody knows who built it" are different claims regardless, and only the second one got 70 million impressions.

The mechanism

This is the standard shape of a benchmark-hype cycle: a small, honest sample produces a startling number, a caveat gets stripped on the first retweet, and the correction, when it comes, reaches a fraction of the audience the hype did. Ben Davis behaved well here, he ran the correction himself within a day. The system around him did not carry that correction as far as the claim.

What to do with this

• Treat any benchmark score built from fewer than 30-40 tasks as a rumor, not a result, regardless of who posts it.
• When a claim says "nobody knows who built it," check whether the maker has simply not spoken yet, that gap tends to close within a week, as it did here.
• If you are choosing a model off a viral benchmark screenshot, wait for the full-suite number. It is usually lower, and sometimes by more than 20 points.