A 27B Model Just Matched the 400B One. It Fits on Your Laptop.

Alibaba released Qwen3.6-27B on April 22. Dense architecture. Open weights. 77.2% on SWE-bench Verified, within 3.7 points of Claude Opus 4.6. On SkillsBench, it scores 48.2% versus its own 397B MoE predecessor's 30.0%. That's a 77% improvement with 14.8x fewer parameters.

Let those numbers sit for a second. A model you can run on a single GPU is now competing with the models that cost $15 per million tokens via API.

Simon Willison tested the Q4_K_M quantization at 16.8GB running locally via llama.cpp. It works on an RTX 4090. It works on M-series Macs. It generates functioning code. Unsloth shipped GGUF quantizations within hours of release (478 upvotes on r/LocalLLaMA), and Ollama already lists it.

I need to flag the caveat: Qwen's benchmarks use their own internal agent scaffold. Independent reproduction outside that scaffolding is still limited as of today. The SWE-bench number may not hold up in your specific environment with your specific tooling. But even if it drops 10 points, a 67% SWE-bench score from a 27B dense model running locally would still be remarkable.

The r/LocalLLaMA discussion about whether to buy a 128GB M5 Max got 76 upvotes and 113 comments, a 1.49 comment-to-score ratio that's the highest in today's entire dataset. People aren't just interested. They're doing math on whether a $4,000 hardware investment pays for itself versus monthly API bills. For a developer spending $200-400/month on API tokens, the break-even is under two years. For a team of five, it's months.

This directly challenges the flat-rate pricing story that's already crumbling. GitHub paused Copilot sign-ups and removed Opus from Pro. Anthropic briefly moved Claude Code to the $100/month Max tier. Both companies admitted that agentic workloads consume far more resources than flat-rate plans can sustain. If the alternative is a one-time hardware purchase and local inference at comparable quality, the economics shift fast.

The pattern is clear. Dense models are closing the gap on MoE for coding tasks specifically. The cost advantage of running 27B locally versus calling a 400B+ API is 10-50x per token. For production-adjacent coding work, not just experimentation, local-first is becoming viable.