The week of April 21-28, 2026 saw an unusual concentration of frontier-class model releases: GPT-5.5, DeepSeek V4, Xiaomi's MiMo V2.5-Pro, and Alibaba's Qwen3.6-27B all shipped within the same seven days. Two of those are open-weight and freely downloadable. Here's the practical breakdown.
GPT-5.5 (OpenAI, April 23)
Available now in ChatGPT paid plans and Codex, with API rollout staged behind a safety review. Priced at $5/$30 per million tokens (up from $2.50/$15 for GPT-5.4, though OpenAI argues the effective cost increase is roughly 20% because GPT-5.5 uses fewer output tokens per task).
Simon Willison's hands-on described it as "a fast, effective and highly capable model." Artificial Analysis independently rated it the top model globally on intelligence-per-dollar. On Terminal-Bench 2.0, GPT-5.5 scores 82.7% versus Claude Opus 4.7's 69.4%.
The benchmark gap to notice: OpenAI omitted coding comparisons against Anthropic in the release materials. Latent Space noted this isn't an oversight - it's signal about where GPT-5.5's relative weaknesses are. Practitioner consensus (Zvi): GPT-5.5 for factual and web tasks, Opus 4.7 for open-ended and interpretive work.
The API premium request multiplier on GitHub Copilot is 7.5x, which means heavy agentic use with GPT-5.5 on a Business plan can exhaust $19/month in a few hours.
DeepSeek V4 (April 24)
Two variants: V4-Pro (1.6T total / 49B active parameters, MIT license) and V4-Flash (284B/13B). Both support 1M token context. Trained on 32T tokens using FP4 precision. Huawei Ascend chip compatibility is included, which matters for China-based deployments but also signals DeepSeek's compute sovereignty strategy.
Community practitioners on r/LocalLLaMA favor Kimi K2.6 (released last month) over V4-Pro for coding specifically. DeepSeek V4 support is already in vLLM v0.20.0 if you're running self-hosted inference. Simon Willison: "almost on the frontier, a fraction of the price."
Qwen3.6-27B (Alibaba, April 22)
This is the efficiency story of the week. Qwen3.6-27B is a dense 27B model (55.6GB) that Alibaba claims surpasses the previous Qwen3.5-397B-A17B (an 807GB MoE) across major coding benchmarks. Simon Willison tested the quantized version and confirmed it works. Community results show 38.2% on Terminal-Bench 2.0.
That's a 14x efficiency gain in one release cycle. If you're constrained by VRAM or want to run a capable model locally on consumer hardware, Qwen3.6-27B is the practical pick this week.
MiMo V2.5-Pro (Xiaomi, April 24)
A 1.02T total / 42B active parameter MoE model, MIT-licensed, 1M context window. The reported benchmark numbers are strong: GPQA-Diamond 66.7 (within 3 points of Opus 4.7), SWE-Bench Pro 57.2 (above Opus 4.6's 53.4, within 0.5 of GPT-5.4 per Artificial Analysis). Long-context reasoning is notably improved over the prior MiMo version.
Xiaomi is a phone manufacturer. That's not background noise - it's context. A company that ships inference hardware at consumer scale and publishes competitive frontier model research should be on your radar.
What This Means for Model Selection
The open/closed model frontier gap has formally closed for several capability classes. The remaining differentiator for paid frontier models is trust infrastructure (safety evaluations, vendor support, enterprise SLAs) and workflow integration (Codex superapp, Claude Code IDE, GitHub Copilot).
For developers making practical choices right now:
- Coding tasks: Kimi K2.6 remains the community-preferred open-weight leader; MiMo V2.5-Pro may displace it on reasoning-heavy coding; Qwen3.6-27B if VRAM is the constraint.
- Factual/web tasks: GPT-5.5 per practitioner consensus.
- Open-ended/interpretive work: Claude Opus 4.7 per practitioner consensus.
- Cost-sensitive inference at scale: DeepSeek V4-Pro as a self-hosted frontier alternative.
One grounding data point before you cancel any subscriptions: a practitioner on r/LocalLLaMA who spent weeks trying to fully substitute local models for Claude Code in real production work reported failure. Benchmark parity and production parity are not the same thing. Hardware requirements, latency, and hosting complexity create real gaps that benchmarks don't surface. Test on your actual workloads.
This story is from Edge Briefing: AI, a weekly newsletter curating the signal from AI noise. Subscribe for free to get it every Tuesday.
Top comments (0)