Fetching from the wire…
Top 5 · 2026-06-10 · source-backed
Cohere launched North Mini Code on June 9 under Apache 2.0, its first developer-focused model. The shape is the pitch: 30B parameters, mixture-of-experts, only ~3B active, and it runs on a single H100. It scores 33.4 on the Artificial Analysis Coding Index, competes on SWE-Bench Verified, SWE-Bench Pro, and Terminal-Bench 2.0, and claims up to 2.8x higher throughput with ~30% lower inter-token latency than Devstral Small 2. Cohere says it beats open models up to 4x its size.
Why this matters more than another benchmark post: this is a genuinely deployable local coding agent. Apache 2.0 means no usage restrictions, single-H100 means you can self-host it without a datacenter, and the throughput numbers mean it's fast enough to sit in an actual agent loop rather than a toy demo. Put it next to the NVIDIA RTX Spark Superchip hitting availability with 128GB unified memory and 120B-param local inference, and the "you need frontier infra for agentic coding" assumption is eroding fast.
I haven't run North Mini Code yet, so treat the throughput claims as vendor numbers until you A/B them on your own repo. But the use case writes itself. The work where you don't want to pay $50/M to Fable or ship proprietary code to an API: tight inner-loop edits, test generation, the high-volume agentic grunt work. Run a local 30B for the cheap 80% and reserve frontier calls for the hard 20%. That two-tier split, local model for volume, frontier for the genuinely hard problems, is starting to feel like the default architecture rather than a cost hack. Pull the weights, wire it into your harness, and measure it against whatever you're currently overpaying for.
Each link below shares sources, entities, or timing with this story.
Anthropic released Fable / Shared entities / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Anthropic released Fable); both cover Bench, Bench Pro, Bench Verified, SWE; overlapping topics (agent, agentic, coding, frontier, model).
Anthropic released Fable / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Anthropic released Fable); both cover Apache, Bench, Bench Pro, Terminal; reported by the same outlet (huggingface.co).
Anthropic released Fable / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Anthropic released Fable); both cover Bench, Bench Pro, SWE, Terminal; overlapping topics (code, coding, frontier, model).
Simon Willison uses Fable / Shared entity: SWE / Same source domain / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Simon Willison uses Fable); both cover SWE; reported by the same outlet (huggingface.co).
Cursor uses Fable / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Cursor uses Fable); both cover Bench, Bench Pro, Fable, SWE; overlapping topics (agent, coding, model).
Kimi K3 benchmarked against Fable / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Kimi K3 benchmarked against Fable); both cover Fable, SWE; overlapping topics (agentic, coding, model).
Anthropic released Fable / Shared entity: Fable / Shared topic / What happened next / Tension
Linked by a graph relationship (Anthropic released Fable); both cover Fable; overlapping topics (agentic, coding, model).
Anthropic released Fable / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Anthropic released Fable); both cover Bench, Fable, Terminal; overlapping topics (frontier, model).