Codex Usage Reset: Why It Happens and How to Check Your Next Reset (2026)

TL;DR

• Codex has 4 reset types: rolling 5-hour window, weekly cycle, manual team resets, and bankable resets (June 2026+)
• Check your reset date: Settings → Usage in Codex desktop/web, or /status in VS Code
• June 2026 incident: fraud prevention bug caused 10-20× faster drain, OpenAI set up warroom and reset all users
• Manual resets restart your timer, not just add quota — users saving quota for later lose it
• Banking feature (June 12, 2026): Plus/Pro users get 1 free bankable reset, can earn 3 more via referrals

Your Codex quota just hit zero. You check Settings — reset date was supposed to be Friday. It's Tuesday. Now the date shows next Monday.

What happened?

If you've watched your Codex usage reset without warning, seen your reset date jump forward, or had quota drain faster than it should, you're not alone. Between fraud prevention bugs, manual team resets, and a banking system rolled out mid-2026, Codex's reset behavior has confused even paying subscribers. Here's every reset type, how to check yours, and what went down during the June 2026 warroom incident that drained users' quotas 10-20 times faster than normal.

Why does my Codex usage reset without warning?

Four reasons: rolling 5-hour window refreshes continuously, weekly cycles complete every 7 days from first use, OpenAI manually resets all users during incidents or celebrations, and bankable resets you trigger yourself.

Most confusion? Manual resets. OpenAI's team performs these without in-app notification. When they happen, your displayed reset date changes and any saved quota disappears. The other three types are system-automated, but each works differently.

2026 manual reset timeline (confirmed dates):

• April 28, 2026: All paid plans reset "to celebrate a good week and allow everyone to build more with GPT-5.5" (source)
• June 4, 2026: Unexpected reset following service issues, users lost 70%+ saved quota (source)
• June 16-25, 2026: Emergency warroom reset after fraud prevention bug caused 10-20× drain rate (source)

Why no in-app warning? OpenAI's Codex team announces resets via X/Twitter, not through the dashboard. Don't follow @thsottiaux (Thibault Sottiaux, Codex engineering lead)? You'll find out after checking Settings and seeing the date changed.

How do I check when my Codex usage will reset?

Codex → Settings → Usage on desktop or web. Or type /status in the VS Code extension to see your renewal date and remaining quota.

Three ways to check:

1. Desktop/Web Dashboard

• Open Codex app or visit chatgpt.com/codex
• Profile → Settings → Usage
• Look for "Renewal date" or "Resets on"

2. VS Code Extension

• Open Codex chat panel
• Type /status and send
• Response shows: quota %, renewal date, tier

3. Status Bar (VS Code)

• Bottom-left corner, quota icon
• Hover for quick tooltip with reset date

Warning: The displayed date isn't guaranteed. Manual resets by OpenAI's team will change it without notice. Treat the date as "earliest possible reset," not a promise.

One user checked at 2pm (reset date: March 16), then again at 3pm — date had jumped to March 17, quota back at 100%. No announcement. Just a silent refresh.

What's the difference between the 5-hour limit and weekly limit?

The 5-hour rolling window prevents burst usage and refreshes continuously (messages used at 2pm free up at 7pm). The weekly limit caps total sustained usage across 7 days from your first use. Both run simultaneously. You're constrained by whichever you hit first.

Think of them as two overlapping guardrails:

5-hour rolling window:

• Limits how much you can use in any 5-hour stretch
• Refreshes continuously, not a fixed schedule
• Send 20 messages at 2pm? Those slots free up at 7pm
• Prevents burst workloads from overwhelming the system

Weekly limit:

• Caps total usage across 7 consecutive days
• Starts from your *first use*, not a calendar week
• Resets 7 days later (unless manual reset happens)
• Prevents sustained heavy usage

Real example: A ChatGPT Plus user ($20/mo) reported their weekly limit drained in 3 hours during a single large refactor. They hit the weekly cap before touching the 5-hour limit — the weekly ceiling was lower than what 5 hours of burst usage would allow. (Similar usage concerns appear across other frontier models' pricing structures as well.)

Why both? OpenAI wants to prevent two scenarios: someone burning through a week's worth in one afternoon (5-hour limit stops this), and someone running coding agents 24/7 for days straight (weekly limit stops this). You're bounded by whichever limit is more restrictive for your usage pattern.

Why did OpenAI reset everyone's Codex limits in June 2026?

OpenAI discovered a fraud prevention bug that caused legitimate users' quotas to drain 10-20 times faster than normal. They set up a warroom on June 16 and performed an emergency reset for all affected users once the issue was identified.

Timeline of the June 2026 warroom incident:

• June 16, 2026: Issue first detected, internal investigation begins
• June 25, 2026: User reports peak on social media, complaints go viral
• Sunday, June 25: Thibault Sottiaux confirms warroom setup
• Within 24 hours: Root cause identified — fraud prevention filters misclassifying legitimate usage
• Emergency fix: OpenAI reset usage limits for all affected users at no cost

What went wrong: OpenAI's automated fraud and abuse prevention systems incorrectly flagged routine Codex activity as suspicious. When an account was misclassified, it consumed credits at 10-20× the normal rate. Some paying users reported losing $40 worth of credits within hours of normal use.

The warroom response: Engineering lead Thibault Sottiaux tweeted that the team set up a "warroom" — Silicon Valley speak for an urgent, all-hands troubleshooting session — on a Sunday to investigate. OpenAI's status page logged it as "Codex Usage Limits Depleting Faster Than Expected." (For comparison, GPT-5.6's delayed release faced government scrutiny rather than technical bugs.)

Resolution: Once the fraud filter bug was confirmed, OpenAI reset all affected users' quotas to 100% immediately. No cash refunds were issued, but users got fresh allocations and the faulty filter logic was fixed.

User impact: Beyond lost credits, the incident raised trust concerns. If OpenAI's automated systems can misclassify paid subscribers' legitimate work as abuse, what stops false positives from triggering account suspensions? The company hasn't publicly addressed that broader question. (Meanwhile, other coding models like Claude Opus 4.8 offer alternative approaches to usage limits.)

How does the banked reset feature work?

Starting June 12, 2026, Plus and Pro users can save rate limit resets to trigger when needed instead of receiving automatic resets. You get 1 free banked reset at launch and could earn up to 3 more by referring friends through June 24.

Launch details:

• Rollout date: June 12, 2026
• Who gets it: Go, Plus, Pro, and Business users
• Initial allocation: 1 free banked reset for all eligible users
• Earning more: Refer friends (Plus/Pro only) — both you and your friend get a banked reset when they send their first message
• Max via referrals: 3 additional resets (total 4)
• Referral window: June 12-24, 2026

How to redeem:

1. Exhaust your current quota (hit 0%)
2. A popup modal appears: "You have 1 reset banked — use it now?"
3. Click to trigger — quota instantly jumps back to 100%
4. Your reset date shifts forward by 7 days

Alternative method: Settings → Usage should show "Banked resets: X" with a redeem button (though many users report this UI never appeared).

Where it shows up:

• Codex desktop app: Profile card in sidebar
• VS Code extension: After hitting limit, a modal pops up
• Web dashboard: Settings → Usage (inconsistent)

Known issues:

• Many paying subscribers (Plus/Pro confirmed) report never receiving the initial free reset
• The "Banked resets" counter is invisible until you hit 0% — no way to check balance beforehand
• Linux CLI users initially couldn't access the feature (later fixed via VS Code extension and desktop app)
• Platform inconsistency: works in some clients, missing in others for the same account

One user summarized: "It's account-level but only appears in some clients, after some limits, for some users." OpenAI hasn't published comprehensive documentation on how the feature works or how to troubleshoot missing resets.

What happens to my unused quota when OpenAI does a manual reset?

Manual resets replace your current quota period entirely. Had 70% remaining and saved it for weekend work? That unused quota is forfeited when the reset happens and your timer restarts from zero.

This is the most frustrating reset type for strategic users. Here's what actually occurs:

Before reset:

• You're at 30% used, 70% remaining
• Reset date shows Friday, June 7
• You plan to save quota for a weekend refactor

OpenAI performs manual reset (June 4):

• Quota jumps to 100% immediately
• Reset date changes to Friday, June 11
• Your saved 70% is gone — no rollover, no compensation

Why this hurts light users: If you use Codex occasionally and save quota for planned intensive work, manual resets penalize that behavior. You don't get bonus quota on top of what you saved — the reset *replaces* your period entirely.

Official response: Mark G. from OpenAI Support confirmed in the June 4 incident thread that "fresh allocation replaced the previous quota period entirely" and "remaining balances from the old period were not preserved or rolled forward." He acknowledged feedback about impact on users who save quota and mentioned the team is "working on improving limits and reset behaviors."

User reactions:

• agusbena: "My weekend plans are disrupted, my schedule is affected"
• andunie: "I had 95% saved with reset date in the future — all gone after this reset"
• Multiple users suggested: give bonus tokens *without* restarting the timer

Why OpenAI does this: Manual resets are triggered by service issues (like the June warroom bug) or "celebrations" (like the April 28 GPT-5.5 announcement). The company views them as benefits — "everyone gets a fresh start" — but users who strategically manage quota see it as a forced forfeiture. (For model releases causing similar policy shifts, see how Sonnet 5 predictions played out.)

No policy has been published on when manual resets will occur or whether alternatives (like bonus credits that don't reset timers) will be implemented.

Why does my Codex quota reset date keep changing?

Your displayed reset date changes when OpenAI performs manual resets or when backend infrastructure updates recalculate your quota window. One user reported 4 resets in 10 days (March 7-11, 2026) with the date shifting forward each time.

Documented case: A bswen.com report tracked 4 quota resets between March 7-11, 2026. Each reset pushed the renewal date forward by one day. On one day, the user experienced two separate resets within hours.

Pattern observed:

• Check at 1pm: 30% used, reset date March 16
• Check at 2pm: 100% quota, reset date March 17
• Check at 3pm (same day): 100% again, reset date March 18

Three likely causes:

1. Bug fix compensation — OpenAI silently resets quotas after fixing backend issues. No announcement, just a quiet refresh. If multiple bugs are fixed in quick succession, you get multiple resets.

1. Promotional token adjustments — The 2X promotional limits that ran until April 2026 may have triggered recalculations. When promotional periods end or caps change, the system might reset windows to apply new limits.

1. Infrastructure scaling — Backend capacity changes during scaling can cause "temporary inconsistencies in how quotas are tracked and displayed." Your actual usage is preserved, but the displayed reset date recalculates.

Community confirmation: A Reddit user (Just_Lingonberry_352) confirmed the same issue: "Before the reset an hour ago it was for 16th, now I see the weekly renew date on the 17th."

Workaround: Treat the displayed reset date as a "minimum, not a guarantee." Check your dashboard before starting intensive coding sessions. One user's advice: "Stop trying to predict resets. Just check status frequently and assume any displayed date could shift."

No official fix: OpenAI hasn't published documentation explaining why reset dates change or how to avoid it. The company hasn't confirmed whether this behavior is a bug or intended.

Frequently Asked Questions

Can I get a refund if my quota was drained by the June bug?

OpenAI reset affected users' limits at no cost but didn't issue cash refunds. The warroom fix restored quotas to 100% for impacted accounts, but users who lost $40+ in credits during the 10-20× drain period didn't receive monetary compensation.

How many banked resets can I have at once?

The June 2026 rollout gave 1 free reset plus up to 3 via referrals (ended June 24). No confirmed maximum beyond that has been published. The feature UI doesn't show your banked reset count until you hit 0% quota.

Does the weekly limit reset on a fixed day like Monday?

No, it's a rolling 7-day cycle from your first use, not a calendar week. If you first use Codex on a Wednesday at 3pm, your weekly limit resets the following Wednesday at 3pm — unless a manual reset happens. Check Settings → Usage for your personal reset date.

Can I avoid hitting the 5-hour limit?

Spread intensive tasks across multiple sessions with breaks. The 5-hour window refreshes continuously, so messages used at 2pm free up at 7pm. If you pause work for a few hours between refactors, you're less likely to hit the burst limit. The weekly limit will still apply to sustained usage.

What's the April 28, 2026 reset everyone mentions?

OpenAI manually reset all paid users' limits "to celebrate a good week and allow everyone to build more with GPT-5.5," but it restarted timers rather than adding bonus quota. Users who'd saved allocation for planned weekend work lost it, leading to frustration and suggestions that future "celebration resets" add bonus credits without restarting the timer.

Where do I find banked resets in the Codex app?

They appear in Settings → Usage or in a popup modal after hitting your limit. Many users report the feature is inconsistent or never appeared despite being eligible Plus/Pro subscribers. Try checking in the desktop app's sidebar profile card or in the VS Code extension after exhausting quota.

Will OpenAI announce future manual resets in advance?

No confirmed policy exists. Past resets had no in-app warning — users learned via X/Twitter posts from the Codex team (primarily @thsottiaux). If you want advance notice, follow the Codex engineering lead on X. That's currently the only notification channel.

Can Linux CLI users access banked resets?

Yes, via the VS Code extension and desktop app. Some users initially reported issues accessing the feature on Linux, but it was later confirmed to work through these clients. The feature is account-level, so redeeming in one client (like VS Code) should apply across all platforms.

Managing Codex usage across multiple models? Velokey routes between OpenAI, Anthropic, and other providers through one unified API — check usage, compare costs, and switch models without managing separate dashboards.

*Last updated: June 30, 2026. Information based on OpenAI Community forums, user reports, and confirmed incidents through June 2026. Reset policies and banking features are subject to change by OpenAI.*