This was classified as a routine reset event. The original announcement determines which plans were covered and whether it applied automatically.
The announcement: “Old news actually from a bunch of days ago, but crossed that 15M. Enjoy a nice r…”
Reading the announcement: gratitude and celebration set the tone of these 27 words, posted in the morning — wrapping a reset as community goodwill is the team's consistent register.
Quick factsTHE SNAPSHOT
| Item | Data |
|---|---|
| Announced | 2026-08-13 01:01 UTC (Beijing 2026-08-13 09:01, Thursday) |
| Type | Global Usage Reset (reset_type: regular) |
| Sequence | #43 of 70 tracked resets |
| Gap before | 2 days |
| Gap after | 8 days (next reset: 2026-08-21) |
| Running average at that time | 7.9 days (mean of the prior 41 gaps) |
| Where this gap sits in history | longer than 19% of historical gaps (ranked #26 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2026-08-13 01:01 UTCThe Codex team posted a reset-related announcement; scope follows the source.
-
Original announcement
“Old news actually from a bunch of days ago, but crossed that 15M. Enjoy a nice reset everyone. Landing in the next hour or so, go /fast. https://t.co/TFRN2SrpCi”— @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 #4 of 4 in the "Sol era"; 8 days later, the next reset landed on schedule on 2026-08-21. Announced on a Thursday, 2 days after its predecessor — those numbers together are this event's coordinates on the timeline.
What it means for youTAKEAWAY
Routine resets historically average about 6.9 days apart, but the spread is wide — back-to-back days to two-week gaps. Watching the radar beats counting days.With a very short gap, this sits squarely in a streak — burning quota in such periods had the highest odds of being refilled in the whole archive.
FAQCOMMON QUESTIONS
What was the Codex global reset on August 13, 2026 (Thursday)?
On August 13, 2026 (Thursday), the Codex team posted a global usage reset announcement — event #43 of 70 in the archive, 2 days after the previous one, part of the "Sol era". detected source scope: all_paid; eligibility and required action follow the linked source and Usage Dashboard.
Only 2 days after the previous one — are back-to-back resets normal?
Yes. The archive shows several such streaks (this event's era, the "Sol era", alone holds 4 events), typically tied to milestones, launch weeks or incident wrap-ups. Streak periods are also when the radar's SEND-IT advice appears most often.
When was the next global reset after this one?
The archive has the historical answer: the next record landed on 2026-08-21, 8 days later. That is hindsight, not a forecast that was available at the time.