The team called this one "a sneaky double reset" — beyond the standard refill, extra compensation was stacked on top. Surprise bonus resets are the community's favorite kind.
Quick factsTHE SNAPSHOT
| Item | Data |
|---|---|
| Announced | 2026-06-18 00:10 UTC (Beijing 2026-06-18 08:10, Thursday) |
| Type | Global Usage Reset (reset_type: regular) |
| Sequence | #24 of 70 tracked resets |
| Gap before | 14 days |
| Gap after | 9 days (next reset: 2026-06-26) |
| Running average at that time | 11.9 days (mean of the prior 22 gaps) |
| Where this gap sits in history | longer than 70% of historical gaps (ranked #6 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2026-06-18 00:10 UTCThe Codex team posted a reset-related announcement; scope follows the source.
-
Original announcement
“Dearest gentle codexer. We did a sneaky double reset. Not only do you get a full reset on us. But you are also getting one into the reset bank to use at your own leisure. Enjoy https://t.co/eORoaKb3pL”— @thsottiaux on X ↗
-
EffectThe event applied to the scope named by the announcement; verify it in your Usage Dashboard.
The era: Spring tuning eraCONTEXT
This segment records an accounting bug that drained limits, several small incidents and announcements describing double resets. Cause and scope still need to be read event by event.
In the full sequence, this is event #5 of 8 in the "Spring tuning era"; 9 days later, the next reset landed on schedule on 2026-06-26. Announced on a Thursday, 14 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.The 14-day gap ran above the then-average, a reminder that long silences can end in either a big compensation or more silence — watching the pressure gauge beats guessing motives.
FAQCOMMON QUESTIONS
What was the Codex global reset on June 18, 2026 (Thursday)?
On June 18, 2026 (Thursday), the Codex team posted a global usage reset announcement — event #24 of 70 in the archive, 14 days after the previous one, part of the "Spring tuning era". the source does not state account scope; eligibility and required action follow the linked source and Usage Dashboard.
Why did this reset take 14 days?
14 days was an unusually long gap at the time — longer than 70% of all gaps recorded up to then (running average: 11.9 days). Long gaps usually mean no trigger event occurred; the team moves on its own calendar, which is exactly why watching the radar beats counting days.
When was the next global reset after this one?
The archive has the historical answer: the next record landed on 2026-06-26, 9 days later. That is hindsight, not a forecast that was available at the time.