01
This site tracks
Global Codex Reset
Unscheduled resets announced for many Codex users at once, often around incidents, launches, or community milestones. The forecast below estimates whether another public reset signal may appear soon.
Current Codex Reset monitorIndependent · transparent · no account needed
Will Codex Reset Today?
Check the latest verified Codex Reset and see the forecast for another one in the next 24–48 hours — built from public signals, reset history, and a formula you can inspect.
Looking for your personal weekly reset time? Run /status in Codex. Your personal weekly cycle and global goodwill resets are separate.
Forecast window
Current / 24–48h
76%
Next 24 hours
91%
By 48 hours
Sources refreshed10 resets tracked
Direct answer
Codex Reset outlook now
As of , the Codex Reset forecast estimates a 76% chance in 24 hours and 91% by 48 hours, based on 1 elevated public signal. The last confirmed Codex Reset was .
Live Codex Reset Outlook
Public signals · Sep 13, 2026, 04:41 PM UTC
76%Codex Reset odds
Next 24 Hours
91%Codex Reset odds
Next 48 Hours
Time since last confirmed Codex Reset
50d13:24:00
Global Codex compensation reset — . Source: Tibo on X
Multiple signals are pointing the same direction: a fresh post from the Codex team plus elevated community chatter make a reset in the next day more likely than not.
Tibo / OpenAI on XQuiet
Monitoring priority55%
No fresh reset-relevant posts in the last 48h
OpenAI StatusNormal
Monitoring priority25%
Last collector snapshot reported no active platform-wide incident
openai/codex GitHub IssuesElevated
Monitoring priority20%
Elevated complaint volume about fast quota drain
Confidence: high · Historical Codex Reset average gap ≈ 5 daysSee the Codex Reset formula →
Reading the console: the 24h and 48h numbers are independent probabilities, not a countdown — a high 48h number with a low 24h number means the signals lean toward “soon, but probably not today.” Confidence reflects how much corroborating evidence is behind the current read: low means we’re mostly relying on the historical baseline, while high means recent posts and community activity agree with each other.
Know which clock you mean
Codex Reset vs. your weekly usage limit
A global Codex Reset, your weekly usage cycle, and an earned reset are separate events. This tracker forecasts public resets; Codex remains the source of truth for private account usage.
02
Check in Codex
Your weekly usage
Your personal usage ceiling follows its own seven-day cycle. There is no universal reset moment shared by every user, so /statusor Settings → Usage is the only reliable place to see when yours refreshes.
03
When available
Your earned reset
Some accounts receive a reset they can redeem manually. It is separate from the weekly cycle and from the global resets tracked here; check /usageto see whether one is available to your account.
Privacy note: this site cannot see your Codex account, quota, or personal reset time.Learn how to check /status →
Methodology, in short
How the Codex Reset forecast works: three public signals
Most Codex Reset trackers watch one feed and hope for the best. We deliberately triangulate across three sources that rarely all go quiet at once, and we show you exactly how much each one is contributing right now instead of hiding the math behind a single mystery number.
Signal 01
The Codex team on X
In this tracker’s sourced dataset, confirmed resets are linked to public evidence, including Codex team posts, status updates, and product documentation. We treat explicit reset announcements as confirmed events and vaguer posts — “feeling like a reset,” jokes about tokens, screenshots of dashboards — as precursor signals with a smaller, decaying weight.
Signal 02
OpenAI Status
A meaningful share of resets are compensation for outages or degraded performance. We poll OpenAI’s public status feed for open or recently resolved incidents touching Codex or ChatGPT, since those events have historically preceded a “we learn, we reset” announcement within a day.
Signal 03
GitHub issue pressure
The openai/codex repository is where developers complain first, often before it trends on social media. A sudden spike of new issues or comments about quota draining unusually fast is an independent, developer-sourced corroborating signal that doesn’t depend on any single account posting on X.
Each signal is scored, decayed over time so that old chatter stops mattering, and combined with a historical baseline hazard rate derived from the actual gaps between past confirmed resets. The result is two numbers — a 24-hour and a 48-hour probability — plus a plain-language explanation of why the number is what it is. The full formula, including the exact decay constants and scoring parameters, is published on the methodology page so you can judge it yourself rather than trusting a black box.
Context
Why a global Codex Reset happens
Global resets are not random generosity — they cluster around three recurring triggers, and knowing which one is in play helps you judge how likely a repeat is. Reading the announcement itself is often the fastest way to tell which bucket you're in: apologetic and specific about timing usually means an incident, celebratory and round-numbered usually means a growth milestone, and scheduled well in advance usually means a launch.
Outage compensation
When Codex or the shared ChatGPT Work infrastructure has a rough night, the team has repeatedly reset usage limits the next morning as an apology. The July 25, 2026 reset — issued after a two-hour near-global outage — is a textbook example, right down to the “we learn, we reset” phrasing.
Growth milestones
Crossing 6M, 8M, 9M, and then 10M combined weekly active users each triggered a celebratory reset in July 2026 alone. These are genuinely hard to predict in advance, but they tend to arrive in bursts once growth accelerates, which is exactly what happened across a single, unusually dense two-week stretch.
Model launches
New model rollouts, like GPT-5.6 Sol, have come bundled with a scheduled reset window to encourage adoption while the team also tunes efficiency improvements that change how fast your quota drains afterward.
What matters now
Your weekly cycle is the personal clock to watch
The website answers whether another global reset may happen soon. Your own remaining usage and reset time live inside Codex and follow the weekly cycle attached to your account.
Your routine limit
Weekly usage
Check /status or Settings → Usage for the percentage and reset time that apply to your account. Public trackers cannot see or calculate this personal cycle for you.
If you run out
Wait, redeem, or use credits
Wait for the weekly cycle, redeem an earned reset when your account has one, use purchased credits where supported, or watch this forecast for an unscheduled global reset. Each route is independent.
The record
Codex Reset history at a glance
Every confirmed event below is corroborated by a public source. Gaps between resets have ranged from under a day during the dense mid-July stretch to roughly two weeks during quieter periods.
Gap between consecutive resets
Measured in days, most recent on the right
Resets by day of week (UTC)
Where confirmed resets have historically landed
View Codex Reset chart data as tables
| Interval | Days |
|---|---|
| #1 | 17.3 |
| #2 | 10.8 |
| #3 | 0.5 |
| #4 | 0.6 |
| #5 | 2 |
| #6 | 2.1 |
| #7 | 1.4 |
| #8 | 2 |
| #9 | 7 |
| Day | Events |
|---|---|
| Sun | 1 |
| Mon | 1 |
| Tue | 1 |
| Wed | 0 |
| Thu | 3 |
| Fri | 2 |
| Sat | 2 |
Most recent activity
- Sep 13, 2026, 09:26 AM UTCOpenAI StatusPrecursor signal
OpenAI Status: Codex GitHub Review and Pull Request Failures
Incident status: resolved. Historically, incidents affecting Codex have a meaningful chance of preceding a compensation reset within 24-48 hours.
Scope: Signal derived from OpenAI StatusView source ↗ - Sep 13, 2026, 01:37 AM UTCopenai/codex IssuesPrecursor signal
GitHub issue activity spike
5 high-engagement openai/codex issue(s) currently discussing quota/reset problems.
Scope: Community-reported, corroborating signalView source ↗ - Sep 12, 2026, 01:46 AM UTCopenai/codex IssuesPrecursor signal
GitHub issue activity spike
5 high-engagement openai/codex issue(s) currently discussing quota/reset problems.
Scope: Community-reported, corroborating signalView source ↗ - Sep 11, 2026, 04:22 PM UTCOpenAI StatusPrecursor signal
OpenAI Status: 1% of ChatGPT Work (mobile/web) turns are failing for existing threads
Incident status: investigating. Historically, incidents affecting Codex have a meaningful chance of preceding a compensation reset within 24-48 hours.
Scope: Signal derived from OpenAI StatusView source ↗ - Sep 11, 2026, 07:53 AM UTCOpenAI StatusPrecursor signal
OpenAI Status: Elevated errors for ChatGPT users in Europe
Incident status: resolved. Historically, incidents affecting Codex have a meaningful chance of preceding a compensation reset within 24-48 hours.
Scope: Signal derived from OpenAI StatusView source ↗
Practical tips
Make usage last until the next Codex Reset
A forecast helps you plan, but a few habits reduce how often you need one in the first place.
Check /status before you start
Running /status in the Codex CLI at the start of a session shows exactly how much weekly quota you have left, so you can scope work accordingly instead of guessing.
Downshift models for routine work
Save your highest-capability model for genuinely hard problems and switch to a lighter one for boilerplate, formatting, or simple refactors.
Batch and scope tasks tightly
Long, open-ended agent loops burn quota fast. Breaking work into smaller, well-scoped tasks tends to use less total budget than one sprawling session.
Save banked resets for emergencies
If you're holding a banked reset, redeem it when you're mid-critical-task and blocked — not the moment it appears — since it expires 30 days after being granted.
Track your own cadence separately
Your personal weekly window is unique to your account and starts from your first call in the cycle. Jot down when it last hit 100% so you know your own timing instead of relying only on global reset news.
Watch this dashboard before big pushes
If you're about to kick off a long agentic session and the forecast above is showing elevated odds, it can be worth waiting a few hours for a possible reset rather than burning your last quota on a task you could delay.
For context
Codex Reset vs. Claude Code reset policies
If you split your work across agents, it helps to know the two systems don't reset on the same logic.
- Routine limits: Codex currently surfaces a weekly usage cycle for personal limits. Claude Code follows its own plan-specific session and weekly policies, so the two products should be checked independently rather than treated as equivalent clocks.
- Global resets: Both OpenAI and Anthropic have issued unscheduled, compensation-style resets after incidents. Neither company publishes a fixed calendar for these, which is exactly the gap tools like this one try to fill.
- Transparency: Codex’s in-app
/statusand/usagecommands are the closest thing to an authoritative personal reset clock either product offers — always check those first for your own account. - What this means for you: If you regularly run both tools, it's worth tracking each product's public communication channel separately rather than assuming a reset on one implies anything about the other — the two have historically moved on completely independent schedules, sometimes days apart.
For developers
Build with Codex Reset data
The dashboard isn't the only way to consume this data. Everything it shows is also exposed as a plain, versioned JSON endpoint and an RSS feed, so you can wire the forecast into your own tools.
GET /api/signal
Returns the current forecast, source status, and last confirmed reset as JSON. Poll it from a cron job, a Discord bot, or a Raycast script — no auth required.
GET /feed.xml
A standard RSS feed of confirmed resets and high-impact precursor signals, ready to drop into any feed reader or automation that already speaks RSS.
Questions
Codex Reset FAQ
A quick primer before you dive into the dashboard above.
The Codex Reset forecast estimates public, shared usage-limit resets announced for many users at once. It does not predict your private weekly reset time, which remains visible only in your own Codex status or usage settings.
No. Will Codex Reset Today is an independent Codex Reset tracker. It turns public status information, Codex team posts, GitHub activity, and verified reset history into a transparent forecast. We are not affiliated with, endorsed by, or operated by OpenAI.
Track the weekly quota shown in /status or Settings → Usage. Its reset time is specific to your account; this site cannot read it and instead forecasts unscheduled global goodwill resets.
The scoring pipeline is designed to refresh hourly by polling OpenAI Status and GitHub, and by checking X activity from the Codex team whenever a reliable feed is available. Every dashboard number is timestamped with the exact data cutoff it was calculated from, so you always know how fresh it is.
Yes. The same numbers behind the dashboard are available at /api/signal as JSON and at /feed.xml as RSS, so you can wire them into a Slack bot, a Raycast command, a cron job, or anything else you build.
Fine print
A Codex Reset forecast, not a guarantee
Will Codex Reset Today publishes probabilities derived from public information and a documented heuristic — it is experimental, unofficial, and can be wrong. Always confirm your own account status with /status and /usage in the Codex CLI before making decisions that matter.
Follow the next Codex Reset.
Use the public Codex Reset RSS feed or JSON endpoint—no account, email address, or private usage access required.
Codex Reset data refreshed: Sep 13, 2026, 04:41 PM UTC