Live tracker for OpenAI Codex usage-limit resets — the answer card below reflects what's actually been recorded. The odds gauges are read live from whenreset.app, the single shared source this site and its sibling trackers all display the same numbers from. This is an estimate, not a prediction — vendors never committed to a reset cadence; see how the odds are calculated. Looking for outages rather than resets? See Codex status.
“Day 28/ Banked 2/2”
Announced
Tibo's 28-day challenge ended Nov 1 · 11 resets · 3 banked — see the archive
Live from whenreset.app — an estimate, not a prediction.
Watched for context — none of them feeds the odds above, which come from whenreset.app.
Recorded resets only — the odds above look forward, this looks back.
Sponsored · synced from howtok.net
NovaAPI describes itself as a global AI token relay platform offering unified access to OpenAI, Claude, Gemini, and Chinese LLMs through low-latency, always-on routing. It advertises transparent pricing with API calls discounted up to 15% off list rates, plus a referral program with ongoing rewards.
CodeKey describes itself as an AI API relay for developers, individuals, and teams, with access to Claude, GPT, DeepSeek, GLM, Kimi, Grok, and Gemini. It provides an English-language site, accepts WeChat Pay, Alipay, and USDT, and states that ¥1 paid gives $1 in platform credit. The operator also states that ordinary invoices are available from ¥200 without a fee and that refunds are available at any time without a fee.
These are sponsored links, synced from howtok.net's pinned relay-station listings — third-party API resellers, not official OpenAI access. CodexReset has no affiliation with them; use your own judgment.
Atom feed · Calendar (.ics) · JSON API · MCP server. Updates only when a reset is actually recorded — no other notifications.
In OpenAI's Help Center wording, an automatic or global reset is applied directly to eligible usage limits and does not create a saved reset, while a banked reset is saved to your account and must be applied by you. This site records both kinds when OpenAI announces them, tagged by the announcement's own wording and kept separate from the usage windows your plan refreshes on its own.
Check the answer card at the top of this page — it's driven by the same data as everything else on this site, generated at build time from public posts.
See the “next 24h” gauge above — it's the share of past Codex global-reset gaps no longer than 24 hours, read live from whenreset.app. It's an estimate, not a prediction; OpenAI has never committed to a reset cadence.
The “next 24h”, “next 48h” and “next 7 days” gauges above cover exactly that question, read live from whenreset.app, the shared source for every tracker in this family. They are historical-frequency estimates, not an announcement from OpenAI — see /forecast-method/ for how the odds are calculated.
Recorded resets come from public posts about Codex, checked periodically and logged with a source link on every row. The 24h/48h/7d odds are read live from whenreset.app; OpenAI's status page and GitHub issue activity are shown as context only and don't feed them — see /forecast-method/ for how the odds are calculated.
It's a historical-frequency estimate (read from whenreset.app), not a schedule — OpenAI has never stated one. Its backtest scores are shown next to the gauges; see /forecast-method/ for the method and whenreset.app's walk-forward backtest.
OpenAI's Help Center defines it as a one-time Codex usage-limit reset saved to your account until you use it or it expires. It is not purchased credit and doesn't permanently increase your plan's limit. See /banked-reset/ for how to find and use one, what happens when you do, and the banked resets recorded here.
Codex reset usage is the manual kind of reset: OpenAI clearing or crediting Codex usage limits through a public announcement, separate from the usage windows your plan already has. It is also searched as codex usage reset or reset usage codex, and all three land on the same list. Every recorded reset links to the post it came from, and the answer card at the top shows the latest one. What this site cannot show is how much usage your own account has left; for that, see /usage-limits/.
The answer card at the top of this page is the Codex reset status: whether a reset was recorded today (UTC), the last one on record, and when it was announced and, if known, delivered. When OpenAI has posted a scheduled reset that hasn't landed yet, a banner above the card shows it. Whether Codex itself is up is a separate question, answered on /status/ from OpenAI's own status feed.
In this site's data, resets are announced on X by @thsottiaux (Thibault Sottiaux, “Tibo”), and every recorded row links to its source post. /tibo/ lists the ones recorded from that account. To hear about the next one without watching X, the Atom feed and calendar file under Subscribe update whenever a new reset is recorded.
This site tracks Codex usage-limit resets only. If you arrived by searching gpt reset usage, the part that matters is that OpenAI's Help Center says a one-time reset can cover Codex or ChatGPT Work usage limits, and an announcement can name more than Codex: each recorded reset shows a scope badge and links the original post, which is the place to read exactly what it covers. ChatGPT's own limits are not tracked here.