LLaDA2.2 targets the real bottleneck in multi-turn agents: decode speed

Direct_Band896 · reddit · 2026-07-25

Decode speed is the hidden tax in agent loops

A Reddit post argues that the real bottleneck in multi-turn agent systems is not tool calls or retries, but raw token-by-token decoding. In agent workflows, the model has to decode repeatedly across planning and tool-use turns, so serial generation compounds both latency and serving cost.

LLaDA2.2 aims at that bottleneck

The post highlights LLaDA2.2, a 100B-class MoE diffusion model built for multi-turn tool use. Instead of locking tokens in place one by one, it decodes blocks and can keep, substitute, delete, or insert tokens mid-decode.

Reported numbers

Caveats

It is not a general reasoning upgrade: the post says it trails the AR sibling on SWE-style benchmarks and general knowledge tasks. It also notes practical deployment limits today: 205.8 GB weights, Apache 2.0, no llama.cpp path, and SGLang support only coming soon.

The core takeaway is that if agent latency is dominated by serial decoding, block-level diffusion decoding is pointed directly at the tax teams are actually paying.

Related event: inclusionAI Launches LLaDA2.2-flash Diffusion LLM(5 posts)→

Original post →

More from coding & agent

coding & agent channel →