Model lifecycle

Claude Opus 5

Released 2026-07-24 · Back to Claude

Exact-version signals observed 2026-07-25–2026-07-25 · n=440

Collecting a stable baseline A verdict appears after the first 14-day window reaches n=30 across at least 7 active days.

Lifecycle updated daily · latest complete UTC day 2026-07-25

Fixed 14-day baseline
Latest 28 days
n=437
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.

Collecting first complete window

1 of 14 calendar days collected · first possible point 2026-08-07 · current signals n=440

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 → 56
Image / vision not enough datan=0 → 0
Local deploy not enough datan=0 → 0
Reasoning not enough datan=0 → 118
Roleplay / creative not enough datan=0 → 5
Safety & refusals not enough datan=0 → 12
Speed & latency not enough datan=0 → 82
General text not enough datan=0 → 165

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.