Codex's one-year anniversary: the team threw the community a birthday reset. Milestone-plus-reset combos recurred all year.
Quick factsTHE SNAPSHOT
| Item | Data |
|---|---|
| Announced | 2026-04-17 00:58 UTC (Beijing 2026-04-17 08:58, Friday) |
| Type | Milestone Celebration Reset (reset_type: regular) |
| Sequence | #17 of 70 tracked resets |
| Gap before | 7 days |
| Gap after | 4 days (next reset: 2026-04-20) |
| Running average at that time | 13.3 days (mean of the prior 15 gaps) |
| Where this gap sits in history | longer than 50% of historical gaps (ranked #7 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2026-04-17 00:58 UTCThe Codex team posted a reset-related announcement; scope follows the source.
-
Original announcement
“Hi! To celebrate its 1-year anniversary, I have allowed Codex to reset its own rate limits across all plans. Enjoy all the new features. https://t.co/xIGXQwMzpa”— @thsottiaux on X ↗
-
EffectThe event applied to the scope named by the announcement; verify it in your Usage Dashboard.
The era: Growth eraCONTEXT
Announcements in this period paired reset events with 3M weekly users, the $100 plan launch and Codex's first anniversary. These are documented historical contexts, not evidence that a future milestone will trigger a reset.
In the full sequence, this is event #5 of 7 in the "Growth era"; 4 days later, the next reset landed on schedule on 2026-04-20. Announced on a Friday, 7 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 7 days, the gap was close to the historical norm — a routine move inside the rhythm.
FAQCOMMON QUESTIONS
What was the Codex global reset on April 17, 2026 (Friday)?
On April 17, 2026 (Friday), the Codex team posted a milestone celebration reset announcement — event #17 of 70 in the archive, 7 days after the previous one, part of the "Growth era". detected source scope: all_paid; 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-04-20, 4 days later. That is hindsight, not a forecast that was available at the time.