Who runs this siteWHO
Codex Reset Radar is an independent developer's project: an open, login-free reset verdict tool and a complete history for developers stuck on Codex quota questions. Not official, not affiliated with OpenAI; verdicts are estimated from public historical patterns, for reference only.
Content is produced two ways, labeled on every page: automated compilation — event data snapshotted from the codex-resets.com public archive (times, types, announcement text); and editorial — era context, guides and FAQs written by an editor from the facts in the announcements, re-reviewed on every data refresh.
Data & methodHOW
- Event archive: periodically snapshotted from the codex-resets.com free public API (currently 53 events, averaging ~6.9 days apart), with the required attribution link kept in the footer. The archive's raw sources are public announcements by OpenAI Codex team members (@thsottiaux et al.) on X.
- Daily digest: collected automatically from four free sources — Hacker News (Algolia API), Reddit public JSON, GitHub Releases, and OpenAI's official RSS — filtered by keywords and a minimum-heat threshold. No automated rewriting: items show their original titles and link to the original sources.
- Verdict engine: pressure = days since the last global reset ÷ the historical average gap (6.9 days). Four display states: official announcement > official watch > projected window > no news; the SEND-IT badge appears only for announcements, watches, or projections ≥90% of the average.
- Analysis integrity: per-event metrics (running average, gap percentile) use only the archive that existed before each event — no future data — so the pages show what was knowable at the time.
Why it existsWHY
Because reset announcements follow no fixed schedule, and developers need one honest answer: can I burn quota today? We don't do mysticism — we do two things: turn official announcements into a searchable history, and compress the historical rhythm into one live pressure gauge. Every page serves that purpose.
The erasPERIODS
| Era | Range | Character |
|---|---|---|
| Launch era | 2025-09-01 ~ 2025-10-31 | GPT-5-Codex had just landed, and global resets were launch support: onboarding gifts timed… |
| Winter compensation era | 2025-11-01 ~ 2026-01-31 | Resets in this period were mostly compensation: the November outage recovery, usage discre… |
| March incident cluster | 2026-02-01 ~ 2026-03-20 | Early March 2026 was the densest incident window in the archive: multiple resets within ni… |
| Growth era | 2026-03-21 ~ 2026-05-10 | User milestones first became official reset reasons: 3M weekly users, the $100 plan launch… |
| Spring tuning era | 2026-05-11 ~ 2026-07-08 | The cadence slowed while the causes got finer: an accounting bug draining limits, three st… |
| July reset spree | 2026-07-09 ~ 2026-07-31 | The wildest three weeks in the archive: ten-plus resets back to back, the 5-hour cap tempo… |
| Sol era | 2026-08-01 ~ 2026-08-18 | With GPT-5.6 Sol drawing crowds, resets continued on celebratory pretexts and settled into… |
| Milestones & banked credits | 2026-08-19 ~ 2026-09-02 | The 20M and 25M milestones landed back to back, and banked resets graduated from occasiona… |
| Astra era | 2026-09-03 ~ present | GPT-6 Astra changed the shape of resets: Astra waiting days converted directly into banked… |
CorrectionsCONTACT
Spot a wrong date, type or quote? Email corrections@whendoescodexreset.com with the page and the specific error; factual corrections land within 48 hours of verification. If you authored one of the announcements and want context added or a quote corrected, reach out directly.