Fetching from the wire…
01
02
03
04
05
06
07
08
Top 5 · 2026-06-21 · source-backed
This is the other half of the Fable 5 story, so read them together. While the best coding model in the world is uncallable, an open-weight one quietly posted frontier-adjacent numbers. Per Tom's Hardware, independent benchmarks for the MIT-licensed GLM-5.2 (744B params, 40B active MoE, 1M-token context) landed: 81.0 on Terminal-Bench 2.1, within 4 points of Claude Opus 4.8's 85.0, and 62.1 on SWE-bench Pro, ahead of GPT-5.5's 58.6.
Let me be specific about what "within 4 points" means in practice, because benchmark proximity usually lies. Four points on Terminal-Bench is the difference between a model that mostly finishes multi-step terminal tasks and one that mostly finishes them with one more retry. It's not nothing. But it's the gap between "uncallable and #1" and "callable and very good," and right now callable wins every time.
The licensing is the headline for builders. MIT, self-hostable, with day-one support for Claude Code, Cline, and Roo Code. You can run the thing on your own GPUs and nobody can revoke it. Sebastian Raschka's June 18 Ahead of AI note dissects the IndexShare mechanism that makes its 1M-token sparse attention cheap enough to self-host. That's the architectural "why" behind the pricing, and it's worth reading before you commit GPU budget, because long-context inference cost is where self-hosting projects quietly die.
On June 19-20, Z.ai co-founder Jie Tang publicly rebutted Elon Musk's claim that China is a year out from a Fable-5-class model. Tang's words: "it won't take that long." Given that Fable 5 is currently banned and GLM-5.2 is four points behind Opus 4.8 and shipping today, I'd say Tang is winning that argument by default.
What builders should do: stand up a GLM-5.2 endpoint as a fallback now, even if it's not your primary. The displaced Fable 5 demand is flowing to GLM-5.2 and GPT-5.5, and capacity is the constraint. Get your config tested while it's calm, not during the next outage. I wired a fallback route last week and the swap took an afternoon. Worth it.
Each link below shares sources, entities, or timing with this story.
Claude Code uses Opus / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Claude Code uses Opus); both cover Bench, Claude Code, Claude Opus, Fable; overlapping topics (benchmark, claude, code, model, point).
Claude Code uses Opus / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Claude Code uses Opus); both cover Bench, Claude Code, GLM, MIT; overlapping topics (benchmark, claude, code, glm-5, model).
Claude Opus built by Anthropic / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Claude Opus built by Anthropic); both cover Bench, Claude Code, Claude Opus, GLM; overlapping topics (claude, code, glm-5, model).
output uses Claude Code / Shared entities / Shared topic / What happened next
Linked by a graph relationship (output uses Claude Code); both cover Bench, Claude Opus, Fable, GLM; overlapping topics (claude, fable, glm-5, model).
Claude Opus built by Anthropic / Shared entities / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Claude Opus built by Anthropic); both cover Claude Opus, GLM, GPT, MIT; overlapping topics (benchmark, glm-5, gpt-5, model).
Linked by a graph relationship (Claude Opus built by Anthropic); both cover Bench, Claude Opus, GPT, MoE; overlapping topics (benchmark, gpt-5, model).
Claude Opus built by Anthropic / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Claude Opus built by Anthropic); both cover GLM, GPT, GPU, MIT; overlapping topics (benchmark, glm-5, gpt-5, model).
Claude Code uses Opus / Shared entities / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Claude Code uses Opus); both cover Bench, Claude Code, Fable, GPT; overlapping topics (benchmark, claude, code, fable, gpt-5).