Qwen4-Coder,
explained.

Qwen4-Coder is a mixture-of-experts, the coding-specialized successor to Qwen3: roughly 32B total parameters split across many experts, with a router that activates only about 3B per token — under 10%. Every token flows through the shared layers plus a handful of routed experts; the other experts sit dormant for that token.

That's the entire trick behind "a strong coder on a laptop." A dense 32B model would need 32B of everything — memory and compute — on every token. The MoE keeps the 32B of knowledge but pays roughly 3B of compute. To see why that fits a Mac, you have to separate two costs people usually lump together.

Running a model locally has two independent bills. Storage: every weight must live in memory, because the router might pick any expert on any token — so you hold all 32B. Speed: decoding is memory-bandwidth bound, and per token the hardware only reads the weights it actually uses — the active ~3B. A dense model ties these together; an MoE cuts the knot.

You buy the RAM for a 32B model and get the throughput of a 3B one. That asymmetry is the whole product.

Storage is just arithmetic: bytes = parameters × bits ÷ 8. In 4-bit, 32B parameters weigh about 16 GB — which slides into a 24 GB Mac's unified memory with room for the KV cache and the OS. In 16-bit it would be 64 GB and wouldn't fit; quantization is what makes it a laptop model.

Fits ⟺ store ≤ VRAM/unified RAM. Speed is a separate line: bandwidth ÷ active-bytes, so it's the 3B — not the 32B — that sets tokens/sec.

SWE-Verified is the hard one: real GitHub issues where a patch counts only if it applies and turns the failing tests green without breaking the passing ones. Reaching ~82% on it is frontier-class agentic coding — and Qwen4-Coder is reported as the first open, Mac-runnable model to clear 80% there.

The significance isn't the two-point benchmark bump; it's where the capability now lives. A genuinely useful coding agent that runs offline, with open weights and an Apache-2.0 licence, changes who can build with it and under what constraints — no per-token API meter, no data leaving the machine.

Qwen4-Coder is the clearest proof yet that the sparse-MoE recipe has made local-first coding agents real. The playbook it validates is exactly the one in the local LLM stack and on-device AI handbooks: pick an MoE so RAM sizing and speed decouple, quantize to fit, and you get a capable model without a data center.

It also sharpens a mental model worth keeping: for any local model, compute the two numbers separately. Total × bits ÷ 8 tells you if it loads; active params vs your bandwidth tells you if it's usable. Dense models make those two move together; every strong on-device release from here will be an MoE precisely to pull them apart.