MAI
Microsoft · 4 tracked releases · June 2, 2026 – August 12, 2026
At a glance
| Releases tracked | 4 |
|---|---|
| First tracked | June 2, 2026 — MAI-Code-1-Flash |
| Latest | August 12, 2026 — MAI-Thinking-1 |
| Span | 71 days |
| Median gap | 15 days between releases |
| Weights | Proprietary throughout |
| Record quality | 3 of 4 verified · how this is judged |
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.
- 2026
- MAI-Code-1-Flash, Microsoft, June 2, 2026
- MAI-Cyber-1-Flash, Microsoft, July 27, 2026
- MAI-Code-1.1-Flash, Microsoft, August 11, 2026MAI-Thinking-1, Microsoft, August 12, 2026
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.
-
MAI-Code-1-Flash
coding
-
+55 days
-
+15 days
-
+1 days
MAI-Thinking-1reasoningfunction calling
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, context window, parameters, 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.
MAI-Code-1-Flash → MAI-Code-1.1-Flash 70 days
No change in any field both releases record.
Compare the two most recent side by side →
All releases from Microsoft →