CODEX RESET RADAR Codex Reset Radar
中文
RESET EVENT #28/70 · July reset spree · Global Usage Reset

Codex Global Usage Reset — July 9, 2026

📅 July 9, 2026 (Thursday) 🏷️ Global Usage Reset ⏱️ 10 days after the previous ✍️ @thsottiaux source ↗

Early July 2026 opened the densest reset spree on record: multiple global resets in roughly three weeks starting July 9, as the user base climbed from 7M to 10M and the 5-hour rolling cap was temporarily removed.

Quick factsTHE SNAPSHOT

ItemData
Announced2026-07-09 21:24 UTC (Beijing 2026-07-10 05:24, Friday)
TypeGlobal Usage Reset (reset_type: regular)
Sequence#28 of 70 tracked resets
Gap before10 days
Gap after1 days (next reset: 2026-07-10)
Running average at that time11.0 days (mean of the prior 26 gaps)
Where this gap sits in historylonger than 67% of historical gaps (ranked #8 longest among the gaps recorded up to then)
Sourcepublic announcement by @thsottiaux ↗, archived by codex-resets.com

TimelineWHAT HAPPENED

  1. 2026-07-09 21:24 UTC
    The Codex team posted a reset-related announcement; scope follows the source.
  2. Original announcement
    “Enjoy a full reset of your usage limits for ChatGPT Work and Codex. Propagating in the next hour. @_rajanagarwal just joined to work on model research and push on coding capabilities. You can thank him for pressing the button today. https://t.co/vMMwKJibBI”— @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 #1 of 12 in the "July reset spree"; 1 day later, the next reset landed on schedule on 2026-07-10. Announced on a Thursday, 10 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 10-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 July 9, 2026 (Thursday)?

On July 9, 2026 (Thursday), the Codex team posted a global usage reset announcement — event #28 of 70 in the archive, 10 days after the previous one, part of the "July reset spree". detected source scope: work; eligibility and required action follow the linked source and Usage Dashboard.

Why did this reset take 10 days?

10 days was an unusually long gap at the time — longer than 67% of all gaps recorded up to then (running average: 11.0 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-07-10, 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 →