This was classified as a routine reset event. The original announcement determines which plans were covered and whether it applied automatically.
The announcement: “Never slept better and feeling reseted. Brand new me and brand new usage for all…”
Reading the announcement: gratitude and celebration set the tone of these 31 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-27 16:35 UTC (Beijing 2026-08-28 00:35, Friday) |
| Type | Global Usage Reset (reset_type: regular) |
| Sequence | #47 of 70 tracked resets |
| Gap before | 2 days |
| Gap after | 2 days (next reset: 2026-08-29) |
| Running average at that time | 7.5 days (mean of the prior 45 gaps) |
| Where this gap sits in history | longer than 17% of historical gaps (ranked #28 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2026-08-27 16:35 UTCThe Codex team posted a reset-related announcement; scope follows the source.
-
Original announcement
“Never slept better and feeling reseted. Brand new me and brand new usage for all ChatGPT Work and Codex users. Regaining my youth one button press at a time. Happy Thursday”— @thsottiaux on X ↗
-
EffectThe event applied to the scope named by the announcement; verify it in your Usage Dashboard.
The era: Milestones & banked creditsCONTEXT
This segment records the 20M and 25M user milestones, an August 21 banked-reset grant and several celebration events near month-end. The record alone does not establish a future launch cadence or an unstated official intention.
In the full sequence, this is event #4 of 6 in the "Milestones & banked credits"; 2 days later, the next reset landed on schedule on 2026-08-29. 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 27, 2026 (Thursday)?
On August 27, 2026 (Thursday), the Codex team posted a global usage reset announcement — event #47 of 70 in the archive, 2 days after the previous one, part of the "Milestones & banked credits". detected source scope: all_paid / work; 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 "Milestones & banked credits", alone holds 6 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-29, 2 days later. That is hindsight, not a forecast that was available at the time.