FULL STORY

Inside Xiaomi MiMo's RL Scaling Playbook

Xiaomi MiMo's RL training details sparked debate as possibly the first million-token-context RL run, and the MiMo v2.6 release centered on explicitly scaling the three core RL factors, alongside a stability paper on MoE reinforcement learning.

2026-09-22 ~ 2026-09-23 · 3 episodes · 27 posts

Episode 1 · Xiaomi MiMo RL Training Details Spark Debate: Suspected 1M-Context RL, Big Gains in Just 30 Steps (2026-09-22, 15 posts)

Xiaomi MiMo-V2.6's RL training details triggered intense discussion in overseas technical communities. stochasticchasm suspects this is the industry's first RL training on a 1M-token context, with dramatic gains in only 30 steps and no plateau on the training curve; tokenbender and nrehiew offered systematic breakdowns of the algorithmic modifications, training efficiency, and infra practices. The converging takeaway: large-batch, stabilized standard GRPO may deliver far higher sample efficiency than previously expected.

Confirmed

  • MiMo uses a classic architecture, described by stochasticchasm as "simple and strong".
  • Extremely large per-step batches: 1568 tasks × 16 rollouts per task, consuming enormous token counts per run.
  • stochasticchasm noted the model improved dramatically in only 30 RL steps, far fewer than expected, with no plateau; he and commenter nrehiew questioned why training was not continued.
  • Training uses a very standard GRPO form without a critic model. stochasticchasm guesses the large batch already suffices to reduce gradient noise, even without larger group sizes.
  • tokenbender catalogued targeted GRPO modifications: prompt-mean loss over token-mean loss (DAPO) to avoid overweighting long answers; separate clipping bounds for positive/negative advantages. The philosophy: keep the algorithm simple, modify for stability and scale.
  • tokenbender argued that high throughput, heterogeneous environments, and only 13% policy drift staleness imply most environments run or improve directly on base weights, without curriculum learning.
  • nrehiew summarized the report's most distinctive infra practices: masking infra failures (e.g., unavailable tools) from trajectories; using the same harness within a group for normalization despite multiple harnesses; estimating HBM usage from rollout length.
  • The setup forgoes PipelineRL-style KV-cache reuse in favor of re-prefilling after policy updates; stochasticchasm speculates that with only 30 steps and large per-step policy changes, re-prefilling may be worth it.
  • stochasticchasm observed that the grader consumed substantial compute and wondered which model served as grader; agent judging may become a new scaling axis.
  • On MOPD2 (report point 6), tokenbender speculates it was likely completed earlier, not part of this RL replay/live run, and considers expert-teacher design more effective than large-scale mixed RL.

Unconfirmed

  • The "1M-context RL training" claim is stochasticchasm's inference from the technical material, phrased as suspected.
  • Critics note the absence of batch-size ablations, so whether large batches substitute for larger group sizes or a critic remains conjecture; MOPD2's timing is also tokenbender's speculation.

Why it matters

  • If 1M-context RL training is confirmed, it marks a new breakthrough on the scaling axis, potentially benefiting long-context agent tasks.
  • Approaching frontier performance in 30 steps, plus 13% policy drift and no need for curriculum learning, suggests large-batch RL sample efficiency may far exceed prior assumptions.
  • The GRPO stabilization checklist, trajectory cleaning and harness normalization tricks, high grader compute share, and re-prefill tradeoffs offer a rare first-hand reference for understanding the cost structure and infrastructure design of large-scale RL.

Episode 2 · Xiaomi's MiMo-V2.6 Bets on Reinforcement Learning Scaling Across 1000+ TPUs (2026-09-22, 10 posts)

Xiaomi released MiMo-V2.6, its largest reinforcement learning scaling effort to date, spanning coding, general reasoning, vision, automation and cybersecurity. The team completed full-parameter RL training on the 310B model across 1000+ TPUs, stably running 1000+ steps and processing 2.7-3.7 billion tokens per step. Luo Fuli's retrospective frames the core question: after years of pretraining scaling laws, can RL scale capability the same way—Xiaomi has been betting on this for the past half year.

Confirmed

  • The paper explicitly scales three RL factors: batch size and throughput, environment diversity, and grader compute. Per @DrSingularity, each RL step processes about 1568 samples and 2.7-3.7 billion tokens, with context lengths up to 1 million tokens.
  • The MiMo team disclosed JAX+TPU-based large-scale RL: full-parameter RL training of the 310B MiMo-V2.6 on 1000+ TPUs, stably running 1000+ steps; scaling up mainly requires config changes rather than code rewrites.
  • @tokenbender's thread notes the large-batch justification stays at throughput and GPU-scaling convenience. Environment synthesis follows standard good practices—clear specs, sampling from rich real-world scenario pools, curating quality seed tasks with grounding. Section 4.2.5's multi-harness training earned his approval, as open-source users often build their own harnesses.
  • The paper discusses CodeMidas's source-driven synthesis. Luo Fuli's retrospective mentioned RL scale details such as generating 25,000 agent trajectories per step.

Unconfirmed

  • Long-horizon tasks appear to rely mainly on agent-driven synthesis; tokenbender is skeptical of their effectiveness and plans to follow up.

Why it matters

  • tokenbender observes MiMo's tasks are grounded from diverse sources rather than built from scratch—pure self-play is not a substitute; since the tasks resemble daily workflows, he expects MiMo v2.6 could replace Sol for daily work.
  • Running 310B full-parameter RL on JAX+TPU with config-only scaling offers the open-source community an engineering reference for large-scale RL training.

Episode 3 · Xiaomi's MoE RL stability paper: router-aware GRPO tweaks explained (2026-09-22, 2 posts)

tokenbender breaks down Xiaomi's arXiv paper on stable MoE RL: rather than replacing GRPO, the team adds targeted fixes such as router-aware importance-sampling rescaling and prompt-mean loss for stability and scale.