CODEX RESET RADAR Codex Reset Radar
中文
RESET EVENT #33/70 · July reset spree · Milestone Celebration Reset

Codex Milestone Celebration Reset — July 14, 2026

📅 July 14, 2026 (Tuesday) 🏷️ Milestone Celebration Reset ⏱️ 1 days after the previous ✍️ @thsottiaux source ↗

The user base hit 8M — one day after 7M. Resets continued and the 5-hour cap stayed removed.

Quick factsTHE SNAPSHOT

ItemData
Announced2026-07-14 19:34 UTC (Beijing 2026-07-15 03:34, Wednesday)
TypeMilestone Celebration Reset (reset_type: regular)
Sequence#33 of 70 tracked resets
Gap before1 days
Gap after1 days (next reset: 2026-07-16)
Running average at that time9.4 days (mean of the prior 31 gaps)
Where this gap sits in historylonger than 3% of historical gaps (ranked #27 longest among the gaps recorded up to then)
Sourcepublic announcement by @thsottiaux ↗, archived by codex-resets.com

TimelineWHAT HAPPENED

  1. 2026-07-14 19:34 UTC
    The Codex team posted a reset-related announcement; scope follows the source.
  2. Original announcement
    “Hello. We have reached 8M active users across Codex and ChatGPT Work. We are once again resetting the usage limits for all. And we continue to not have the 5h rate limit as well, allowing everyone to explore the boundaries of GPT-5.6 Sol and discover how ambitious you can be. https://t.co/pKunziOGRm”— @thsottiaux on X ↗
  3. Effect
    The event applied to the scope named by the announcement; verify it in your Usage Dashboard.

The era: July reset spreeCONTEXT

This is the archive's densest three-week segment: more than ten public records, a temporary removal of the five-hour limit, announced user growth from 7M to 10M, and a banked-reset grant to 500k users. That density should not be extrapolated into a future cadence.

In the full sequence, this is event #6 of 12 in the "July reset spree"; 1 day later, the next reset landed on schedule on 2026-07-16. Announced on a Tuesday, 1 day 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.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 July 14, 2026 (Tuesday)?

On July 14, 2026 (Tuesday), the Codex team posted a milestone celebration reset announcement — event #33 of 70 in the archive, 1 days after the previous one, part of the "July reset spree". detected source scope: all_paid / work; eligibility and required action follow the linked source and Usage Dashboard.

Only 1 day after the previous one — are back-to-back resets normal?

Yes. The archive shows several such streaks (this event's era, the "July reset spree", alone holds 12 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-07-16, 1 day later. That is hindsight, not a forecast that was available at the time.

ℹ️ About this page: event data (times, type, the original announcement) is snapshotted automatically from the public codex-resets.com archive; the gap, sequence and running-average analyses are computed by this site's build script from the full archive; background and FAQs are written from the facts in the announcements. Read the full methodology → (data refreshed: 2026-11-01)

🎯 Any confirmed public reset today?
Open the signal radar for sourced announcements; personal allowance and exact reset time remain in Usage.
Open the signal radar →