Model lifecycle
Grok 4.5
Released 2026-07-08 · Back to Grok
Exact-version signals observed 2026-07-08–2026-07-20 · n=207
Lifecycle updated daily · latest complete UTC day 2026-07-20
- Fixed 14-day baseline
- – –
- Latest 28 days
- 77.3 n=204
- Change vs baseline
- –
- 90-day slope
- – pts / 30 days
14-day rolling experience
Each daily point summarizes the previous 14 complete UTC days. The dashed line is the fixed release baseline; the verdict still uses independent non-overlapping 14-day segments.
13 of 14 calendar days collected · first possible point 2026-07-22 · current signals n=207
What explains the change
Experience change and discussion-mix change are separated. These are observational contributions, not proof of cause.
No category has enough samples in both windows for a contribution conclusion.
| Category | Baseline → current | Category change | Weight share | Experience contribution | Discussion-mix contribution |
|---|---|---|---|---|---|
| Coding | not enough datan=0 → 32 | – | – | – | – |
| Image / vision | not enough datan=0 → 1 | – | – | – | – |
| Local deploy | not enough datan=0 → 0 | – | – | – | – |
| Reasoning | not enough datan=0 → 33 | – | – | – | – |
| Roleplay / creative | not enough datan=0 → 3 | – | – | – | – |
| Safety & refusals | not enough datan=0 → 8 | – | – | – | – |
| Speed & latency | not enough datan=0 → 63 | – | – | – | – |
| General text | not enough datan=0 → 65 | – | – | – | – |
Lifecycle scores use the same experience-signal weights as the main index, without sample shrinkage after n=30. They measure public user perception, not model capability or backend causes.