Data through 2026-08-23
Codex Reset
Reset gaps vary. We chart the cadence so you know when to look.
Live signal · cadence math · 30-day history.
Current reset signal
Yes — a reset was just tracked.
Next window ≈ 2026-08-24 04:48 UTC
Live countdown ·
Checking live reset signal…
Sources: /status + community announcements. Community rows stay labeled.
Cadence — the last 30 days
Last tracked resets
The latest tracked reset was a banked window (bonus/goodwill) — the weekly cadence clock may not have moved with it.
- 2026-08-22 · 00:50 UTC — previous +9.0d banked
- 2026-08-13 · 01:01 UTC — previous +2.0d banked
- 2026-08-11 · 00:27 UTC — previous +2.2d
- 2026-08-08 · 20:29 UTC — previous +3.2d
- 2026-08-05 · 14:32 UTC — previous +2.5d
Methodology, sources & history
Transparent model. Stats and probabilities come from this reset list (captured 2026-08-23): past longest → 70/90, past median → 50/75, typical cadence → 30/50.
Live feed. We poll dracon.uk/api/v1/studio/codex-reset-feed roughly every ten minutes for author-gated X and community landing evidence, then merge
fresh entries without overwriting attributed notes. If unreachable, the snapshot stays
the source of numbers.
What’s tracked. Rows mix Dracon /status observations with
attributed community reports. Banked goodwill windows stay labeled and out of cadence
stats. These gaps are history, not a schedule.
Source. Reset events are confirmed via OpenAI Codex /status output + community reset reports (attributed); community entries remain attributed.
Tool history
- 2026-08-08 — Reset confirmed via /status; the verified list continues to grow below it.
- 2026-08-09 — First tracker build (Dracon style).
- 2026-08-10 — Tool apex relaunch; tool moves under /tools/codex-reset.
- 2026-08-13 — Premium upgrade: forecast hero, /status clock, banked resets, alerts bridge, rhythm chart.
- 2026-08-15 — Competitor audit: community-verified reset list (08-13 event attributed), cadence + forecast now computed from the list, live OpenAI status row, working 15-minute countdown alert, Dracon funnel links.
- 2026-08-16 — Answer-first redesign: one question up top, alerts row second, cadence third; personal tools and methodology collapsed.
- 2026-08-22 — Feed source codex-reset.com went dark; self-hosted studio-api proxy became the durable Tier-1 (forum + oembed discovery, author-gated). Aug-8 pair merged into one attributed entry.
- 2026-08-23 — Missed 2026-08-22 banked reset (20M milestone) ingested from the revived codex-reset.com feed; cadence chart rebuilt as a real 30-day timeline with amber banked dots; prediction alert replaced by a reset-landing watcher.
- 2026-08-23 — Source-validation pass: inserted missing 2026-08-11 reset, enriched banked classifications with direct quotes from @thsottiaux
FAQ
- What is a Codex reset?
- A Codex reset starts a fresh usage window for the coding tool. This tracker records when resets happen so you can plan around the cadence.
- How often does Codex reset?
- Tracked gaps vary. The chart and forecast recalculate from the current reset list rather than assuming a schedule.
- Where does the reset data come from?
- We combine Dracon /status observations with attributed X and community announcements. Community rows stay labeled; the tracked list powers the forecast.
- Does the tracker work without a Codex account?
- Yes. No Codex login or API key is needed. Public data powers the tracker; preferences stay in your browser.
- How is the next-window time computed?
- The next window projects the median gap across the last five tracked resets from the latest timestamp. Forecast tiers show how far the wait has stretched.