MiMo

At a glance

Release cadence

One tile per tracked release, placed in the month it shipped, so the pauses in this line are the pauses in the data. Years with nothing tracked keep their row.

1. 2025
   1. MiMo-V2-Flash, Xiaomi, December 16, 2025
   1
2. 2026
   1. MiMo-V2-Pro, Xiaomi, March 18, 2026
   2. MiMo-V2.5, Xiaomi, April 23, 2026MiMo-V2.5-Pro, Xiaomi, April 23, 2026
   3. MiMo-V2.6-Pro, Xiaomi, September 22, 2026MiMo-V2.6-Flash, Xiaomi, September 22, 2026
   5

Lineage

Ordered by announcement date, and spaced by the gap between releases, so a quiet year looks like one. Lineage is not inferred from version numbers — labs do not number consistently, so the dates decide the order.

1. December 16, 2025

   MiMo-V2-Flash

   codingagentic

2. March 18, 2026 +92 days

   MiMo-V2-Pro
3. April 23, 2026 +36 days

   2 released the same day

   MiMo-V2.5

   MiMo-V2.5-Pro

   from MiMo-V2-Pro Weights Proprietary → Open

4. September 22, 2026 +152 days

   2 released the same day

   MiMo-V2.6-Pro

   reasoning

   MiMo-V2.6-Flash

   from MiMo-V2-Flash Context window 262K → 1.05M

Context window over time

Only releases with a disclosed context window appear — 1 of 6 are not shown.

What changed

Generation to generation, from evidenced values only. A field is compared only where both releases record it — otherwise it is called out as not comparable, so a research gap never reads as a change the lab made.

Across every generation of this family, capabilities and modalities could not be compared — the values are not recorded on both sides of any step. That is a gap in this dataset, not a statement about the models. See data quality.

Compare the two most recent side by side →
All releases from Xiaomi →