TL;DREvery launch thread circles back to one question: what actually changed under the hood? This piece strings the official product-line anchors from April 2025 to July 2026 into a single timeline, so the release rhythm reads at a glance — and you can decide whether to chase the new drop or sit tight.
Sources SOURCES
Distilled from public community discussions. This page only breaks them down and verifies — it never reposts the original; opinions belong to their authors.
Facts FACTS
Check these claims against the listed sources. For allowance mechanics, first-party account displays outrank community summaries.
- Official product-line anchors: Codex CLI opened up 2025-04, the cloud research preview arrived 2025-05, GPT-5-Codex shipped 2025-09, 5.1-Codex-Max landed 2025-11, and 5.2 followed 2025-12.
- 2026 visibly sped up: the desktop app and GPT-5.3 landed in the same month, 2026-02 (alongside the spin-off tier 5.3-Codex-Spark), a 90+ plugin ecosystem emerged 2026-04, and Sites, Goal mode, the Chrome extension and 5.5 dropped together in 2026-06.
- 2026-07: GPT-5.6 Sol Ultra was announced into Codex, with mobile landing the same month; that same month the 5-hour limit was also temporarily removed — whether that state changed later is defined by the current official word.
- New-model and new-feature launches are a high-frequency trigger for all-user resets: this site's archive counts 53 of them (since 2025-09-17), averaging about 6.9 days apart.
Concepts CONCEPTS
Not everything said in a community thread is a fact — each concept carries its nature label. Read the label first.
The version-numbered evolution of Codex's underlying models: GPT-5-Codex → 5.1-Codex-Max → 5.2 → 5.3 → 5.5 → 5.6 Sol Ultra, with spin-off tiers like Spark wedged in between. Drop the scattered launch news back onto this line and the rhythm finally comes into view.
Model launches are a common trigger for all-user resets — that is the factual footing under the community's 'camp a launch, wait for a reset' play. But resets don't follow every launch, so the arrow doesn't run backwards.
Read straight off the anchors: 2025 moved roughly once every two to three months, while 2026's first half delivered a major move almost every two months. That's a trend the timeline shows, not a precise law — the pace can shift again.
A hot launch is not automatically an upgrade for your workflow. Whether to switch your default model rides on your task mix and tier needs — that call stays personal.
Takeaways TAKEAWAYS
Two things get obvious once the line is straight. First, the 2026-02 desktop app is a watershed: before it, Codex mostly lived in terminals and the web; after it the product surface widened fast, and the model line went from 'the CLI's engine' to the shared foundation of an entire product family. Second, the 5.3 generation towers over the source archive in heat (1530 pts) — community attention to the models themselves peaked right around that window.
For a regular user, the timeline's payoff isn't memorizing version numbers — it's calibrating expectations. At this pace, every 'best model' has a short shelf life. Rather than chasing each release, fix your own validation loop: when a new model drops, run your most typical task as a head-to-head, switch if the delta is real, and stay put otherwise.
One parallel track is easy to miss: in 2026-07 the 5-hour limit was temporarily removed. Policy and models are two separate axes, and both states can change — exactly why this piece avoids absolutes. For the community reaction and the event trail, see the 2026-07-09 reset entry in the full reset history.
Keep reading NEXT
Want today's verdict? Back to the live radar.