← Back to Library

Qwen3.8 27B, nemotron 3.5, muse, DeepSeek v4 pro: A huge week for Open-Weight AI

This week's surge in open-weight artificial intelligence models isn't just a technical update; it marks a structural shift where the barrier to entry for state-of-the-art reasoning has collapsed. The Kaitchup captures a pivotal moment where the industry's focus has pivoted from sheer parameter counts to the practical mechanics of agentic execution and inference efficiency. For busy professionals, the takeaway is stark: the models that were once the exclusive domain of massive cloud providers are now running locally, and they are becoming dangerously capable at autonomous coding tasks.

The Architecture of Sparsity

The piece centers on a massive release from Qwen, specifically the Qwen3.8 2.4T model, which the editors describe as a turning point in the open-weight landscape. "At this point, Qwen seems so far ahead that catching up is becoming difficult for everyone else," the article asserts, highlighting a competitive gap that is widening based on performance rather than just model size. The core of this advantage lies in a specific architectural choice: extreme sparsity. The Kaitchup explains that while the model boasts 2.4 trillion total parameters, only 95 billion are activated for any given token. This design mirrors the efficiency principles seen in the history of the Transformer architecture, where the goal has always been to maximize output quality while minimizing the computational cost per token.

Qwen3.8 27B, nemotron 3.5, muse, DeepSeek v4 pro: A huge week for Open-Weight AI

The editors validate their previous predictions about this hardware requirement, noting, "It is an extremely sparse MoE... Only 95B of 2.4T parameters are active for each token, or roughly 4% of the entire model." This confirmation is significant because it proves that the industry has successfully moved past the idea that bigger dense models are the only path forward. However, the piece also introduces a critical caveat regarding the new default settings. The model now enables "preserve_thinking" by default, a feature that retains reasoning traces across conversation turns. The editors warn that while this boosts accuracy, it creates a new bottleneck: "So if you preserve reasoning for each turn, the context may grow to millions of tokens." This is a double-edged sword; it allows for complex, multi-step reasoning but risks exhausting memory resources on consumer-grade hardware.

The Speed and Agent Revolution

Beyond raw intelligence, the coverage highlights a fierce battle for speed and utility in agent workloads. NVIDIA's release of the Nemotron 3.5 Lightning is framed not as a new size class, but as a strategic refinement of existing technology. The article notes that the model now integrates "Multi-Token Prediction... followed by an additional MTP-boosting phase," a technique designed to generate multiple tokens simultaneously to drastically cut latency. This is crucial for agents that need to execute thousands of small tasks in rapid succession. The Kaitchup reports that NVIDIA claims the model can complete tasks "around 30% faster than Qwen3.6 35B at comparable accuracy," though the editors rightly add, "Those are NVIDIA's numbers, so I would still like to reproduce the speed/accuracy trade-off independently."

Simultaneously, DeepSeek's update to its V4 Pro model demonstrates how quickly the performance baseline is moving. The piece details a dramatic leap in coding capabilities, noting that the DeepSWE benchmark score jumped from a meager 12.8 to a robust 62.7. "The accuracy jump is much more important," the editors argue, pointing out that the new model has overtaken previous iterations and rivals much larger competitors. This rapid iteration cycle suggests that the "preview" label on these models is becoming a misnomer; they are effectively production-ready. A counterargument worth considering is whether these benchmark gains are robust across different real-world environments or if they are optimized specifically for the test harnesses used by the developers. Independent verification remains the only way to confirm if these gains translate to actual enterprise utility.

Qwen now seems so far ahead that catching up is becoming difficult for everyone else.

The Bottom Line

The strongest argument in this coverage is the demonstration that sparsity and specialized training for agents are the new drivers of AI progress, rendering the old metric of total parameter count largely irrelevant. The piece's biggest vulnerability is its reliance on vendor-provided benchmarks, which often lack the friction of real-world deployment. Readers should watch for independent stress tests on the new "preserve_thinking" feature, as the potential for context explosion could be the limiting factor for widespread adoption of these powerful, open-weight models.

Deep Dives

Explore these related deep dives:

  • DeepSeek

    This specific benchmark is cited as the primary evidence for Qwen3.8's 'spectacular gains' in agentic coding, jumping from 13.3 to 42.2, making it essential for understanding the model's claimed superiority.

  • Cache replacement policies

    The article's warning about reasoning traces growing to millions of tokens highlights the critical bottleneck where this memory management technique determines whether long-horizon agentic runs remain computationally feasible or collapse under their own context weight.

Sources

Qwen3.8 27B, nemotron 3.5, muse, DeepSeek v4 pro: A huge week for Open-Weight AI

Hi everyone,

This week was unusually rich in open-weight releases.

Meta released Muse Glimmer. Qwen finally released the weights of Qwen3.8 2.4T. NVIDIA released Nemotron 3.5 Lightning. DeepSeek just pushed a major V4 Pro update.

And, just as I was finishing this article, Qwen3.8 27B was released. It was worth the wait. According to Qwen’s evaluations, it improves very significantly over Qwen3.6 27B essentially everywhere, with particularly spectacular gains on long-horizon agentic coding: DeepSWE jumps from 13.3 to 42.2, while QwenSWEBench goes from 49.3 to 79.0. The 27B model also beats Qwen3.7-Plus on many coding and agentic benchmarks, and even beats Opus4.6 Max on QwenSWEBench, CoWorkBench, and LiveCodeBench. At this point, Qwen seems so far ahead that catching up is becoming difficult for everyone else.

There are also a few interesting changes compared with Qwen3.6. preserve_thinking, which Qwen3.6 introduced as an option for keeping reasoning traces across turns, is now enabled by default. Qwen3.8 also introduces reasoning_effort, with low, medium, and xhigh levels to trade reasoning depth against cost. Qwen now recommends temperature=1.0 and top_p=0.95 for thinking mode generally, and, for very long agentic runs, recommends allowing up to 262K tokens for reasoning and 131K for the final answer. I’ll publish a full analysis of Qwen3.8 27B within the next few days, with a separate look at its quantized versions later.

Note: I think this “preserve_thinking” (which is a feature we can find in other models) should be carefully evaluated, especially its impact on inference cost. Qwen3.8 is a crazy thinker (they recommend allowing “up to 262K tokens for reasoning”). So if you preserve reasoning for each turn, the context may grow to millions of tokens. In practice though, for tool calls, reasoning is often much shorter and more/better reasoning may yield fewer turns, so I guess it can work. But I’m really interested to know how important it is, in terms of accuracy/efficiency, to preserve the reasoning traces. KV cache quantization will likely be very important.

Finding enough time to cover all of this properly is hard. I don’t want to publish articles that simply repeat benchmark tables and model cards. A proper analysis means testing accuracy, token efficiency, memory, speed, and then doing it again for several quantized versions.

For Glimmer, I already published an article covering the model and its architecture:

Muse Glimmer: Meta’s 30B Model Built for Efficient Inference

I also already ...