This was a milestone-celebration reset: Codex hit a new growth marker and the team thanked the community with a global refill, announced together with the milestone.
The announcement: “That's right, GPT-5.6 Sol is awesome and can be used pretty much anywhere, inclu…”
Reading the announcement: gratitude and celebration set the tone of these 48 words, posted in the late night — wrapping a reset as community goodwill is the team's consistent register.
Quick factsTHE SNAPSHOT
| Item | Data |
|---|---|
| Announced | 2026-08-08 20:29 UTC (Beijing 2026-08-09 04:29, Sunday) |
| Type | Milestone Celebration Reset (reset_type: regular) |
| Sequence | #41 of 70 tracked resets |
| Gap before | 8 days |
| Gap after | 2 days (next reset: 2026-08-11) |
| Running average at that time | 8.2 days (mean of the prior 39 gaps) |
| Where this gap sits in history | longer than 70% of historical gaps (ranked #11 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2026-08-08 20:29 UTCThe Codex team posted a reset-related announcement; scope follows the source.
-
Original announcement
“That's right, GPT-5.6 Sol is awesome and can be used pretty much anywhere, including in the CC harness. To celebrate this, together with the fact that I'm not going anywhere... I have reset usage limits for all paid users of ChatGPT Work and Codex. Have fun out there! https://t.co/2rtjtOxFt0”— @thsottiaux on X ↗
-
EffectThe event applied to the scope named by the announcement; verify it in your Usage Dashboard.
The era: Sol eraCONTEXT
Announcements around GPT-5.6 Sol included celebratory contexts such as an efficiency week. Gaps in this short sample clustered around 6–9 days, but the published backtest shows that historical mean gaps do not reliably predict the next event.
In the full sequence, this is event #2 of 4 in the "Sol era"; 2 days later, the next reset landed on schedule on 2026-08-11. Announced on a Saturday, 8 days after its predecessor — those numbers together are this event's coordinates on the timeline.
What it means for youTAKEAWAY
Milestone resets are pure perks with no trigger conditions. Historically nearly every user-count milestone (3M → 25M) came with one.At 8 days, the gap was close to the historical norm — a routine move inside the rhythm.
FAQCOMMON QUESTIONS
What was the Codex global reset on August 8, 2026 (Saturday)?
On August 8, 2026 (Saturday), the Codex team posted a milestone celebration reset announcement — event #41 of 70 in the archive, 8 days after the previous one, part of the "Sol era". detected source scope: all_paid / work; eligibility and required action follow the linked source and Usage Dashboard.
Do I need to do anything for this event?
Read the linked announcement and your Usage Dashboard. Automatic resets and redeemable banked resets are different; this event's source determines the required action.
When was the next global reset after this one?
The archive has the historical answer: the next record landed on 2026-08-11, 2 days later. That is hindsight, not a forecast that was available at the time.