Fetching from the wire…
01
02
03
04
05
06
07
08
Top 5 · 2026-06-16 · source-backed
The minute Fable 5 and Mythos 5 went dark for foreign nationals, r/LocalLLaMA found its answer. Moonshot AI's Kimi K2.7 Code is a 1T-parameter MoE (32B active, 384 experts), 256K context, shipped under a Modified MIT license. The headline number that's getting it pulled: 81.1 on MCPMark-Verified tool use, across Notion, GitHub, Filesystem, Postgres, and Playwright servers. That beats Opus 4.8's 76.4 on the same benchmark. Moonshot also claims +21.8% on Kimi Code Bench v2 with 30% fewer reasoning tokens.
Treat the vendor-claimed numbers with the skepticism story one earned them. But the tool-use score is the one that matters for agent work, and it's the one beating a frontier closed model. That's not nothing.
What's actually happening here is an adoption catalyst, not a benchmark win. Builders are downloading 340GB of weights rather than risk another off-switch. The export-control shock did more for open-weight coding model adoption than any benchmark could. When the alternative is "your model can be revoked by a government you don't vote in," 340GB of disk and a local rig starts looking cheap. I've watched this sentiment swing in real time on the subreddit, from "open weights are a fun hobby" to "open weights are my continuity plan."
I haven't run K2.7 in anger yet, so I won't tell you it matches Opus on real codebases. Benchmarks and my Tuesday afternoon are different animals, and a 1T MoE needs serious hardware to serve at usable latency. But the strategic logic doesn't depend on it being better. It depends on it being yours. A model nobody can take away from you has a floor under its value that a hosted frontier model structurally can't have right now.
What to do: if you've been treating local models as a toy, the calculus changed this week. Stand up Kimi K2.7 or another open-weight coding model as a tested fallback, not a someday project. The companion move is the local-first stack maturing underneath it (LocalAI at 46,890 stars, Microsoft's Foundry-Local), covered in Infrastructure. The off-switch is real. Plan like it.
Each link below shares sources, entities, or timing with this story.
Moonshot AI deprecates Kimi K2 / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Moonshot AI deprecates Kimi K2); both cover Code, Kimi Code Bench, Kimi K2, Modified MIT; overlapping topics (benchmark, code, coding, kimi, model).
Anthropic released Fable / Shared entities / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Anthropic released Fable); both cover Benchmarks, Kimi K2, LocalLLaMA, MoE; overlapping topics (benchmark, coding, frontier, model, moonshot).
Linked by a graph relationship (Anthropic released Fable); both cover Fable, Mythos, Opus, Plan; overlapping topics (code, frontier, model, opus).
Simon Willison uses Fable / Shared entities / Same source domain / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Simon Willison uses Fable); both cover GitHub, LocalLLaMA, MoE, Opus; reported by the same outlet (huggingface.co).
Microsoft supports MCP / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Microsoft supports MCP); both cover GitHub, Local, LocalLLaMA, MoE; overlapping topics (code, local, model).
Anthropic released Fable / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Anthropic released Fable); both cover Kimi K2, Local, Modified MIT, MoE; overlapping topics (benchmark, kimi, model, open-weight).
Cursor uses Fable / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Cursor uses Fable); both cover Kimi, Kimi K2, LocalLLaMA, Moonshot; overlapping topics (coding, kimi, model, moonshot).
Microsoft criticizes Claude Code / Shared entities / Shared topic / What happened next / Tension
Linked by a graph relationship (Microsoft criticizes Claude Code); both cover Fable, Mythos, Opus, When; overlapping topics (benchmark, code, coding, opus).