DEV Community

Cover image for How Codex and Claude usage-limit resets actually work (and how I track them)
Fawwaaz Sheik
Fawwaaz Sheik

Posted on

How Codex and Claude usage-limit resets actually work (and how I track them)

If you use Claude Code or Codex every day, you've probably had this moment: you hit your limit, then someone on X says "limits just got reset" and you have no idea if that applies to you, if it already happened, or if it's still rolling out.

I kept refreshing X to figure this out, so I built a small tracker with Claude Code that logs every reset with its source post. After a few months of watching the data, here's what I've learned about how these resets actually work.

First: there are two kinds of "reset"

This is where most of the confusion comes from.

1. Your normal windows. Both products have a rolling short window and a weekly window.

  • Claude: paid plans have a session limit that resets every five hours, plus weekly limits that reset once a week. Your weekly reset day and time are fixed per account and shown in Settings > Usage. Usage on claude.ai, Claude Code and Claude Desktop all counts toward the same limit.
  • Codex: on Plus and Business Standard you get a five-hour window and a weekly window, and you need allowance left in both to keep going. A new five-hour window starts with your first message after the previous one ends. The Pro tiers currently have no five-hour limit, but a weekly allowance still applies.

These roll over on their own. Nobody announces them.

2. Extra, one-off resets. These are the ones people actually talk about. Someone at Anthropic or OpenAI posts on X that limits have been reset, and everyone's allowance goes back to full. There's no published schedule for them. They just happen.

The rest of this post is about type 2.

How often do they happen?

From my log (all times UTC):

  • Codex: 63 full resets logged, plus 7 banked grants. The median gap between resets is 3 days. The longest wait was 68 days (Dec 25, 2025 to Mar 3, 2026).
  • Claude: 13 full resets logged, plus 1 banked grant. The median gap is 7.5 days, and the longest wait between two resets was 47 days.

October 2026 has been wild for Codex: 12 resets in the month so far. Tibo (@thsottiaux) has been numbering his posts like a countdown ("Day 17/ Bet you thought we forgot, but no, it's reset day today", "Day 20/ Rest and reset", "Day 21/ Wonder what happens the remaining seven days. But today is a reset.").

Claude is the opposite right now. The last full Claude reset was Sep 4, 2026 (Max plans), which is already longer ago than the previous longest gap in my log.

So the honest answer to "when's the next reset?" is: nobody knows, and anyone giving you a date is guessing. What you can do is look at the rhythm. That's why the Codex reset tracker and the Claude reset tracker each show the median gap and how many resets landed in the last 7, 30 and 90 days instead of a fake countdown.

Announced isn't the same as landed

This one bit me a few times. A reset post goes up, you check your usage, and nothing has changed.

That's because some resets are announced first and propagate later. I log both timestamps when there's a separate "it's live now" post. Across the four Codex resets where I have both, the average gap between announcement and landing is 9 h 12 min:

Reset Announced (UTC) Landed (UTC) Lag
Aug 24, 2026 Aug 23, 06:29 Aug 24, 00:46 18 h 18 min
Sep 8, 2026 Sep 7, 19:24 Sep 8, 04:05 about 8 h 41 min
Oct 11, 2026 Oct 10, 22:15 Oct 11, 04:01 about 5 h 46 min
Oct 13, 2026 Oct 13, 01:03 Oct 13, 05:06 about 4 h

The Aug 24 Codex reset is the extreme case: announced the day before, then "Reset has been propagated to accounts..." almost 18 hours later. If you saw the first post and checked right away, you'd have thought it was fake.

Takeaway: if a reset was just announced and your usage hasn't moved, wait a few hours before assuming you weren't included.

Banked resets: the ones you have to redeem

Both companies now also hand out banked resets. These don't touch your limits automatically. They're a credit you use yourself, when you choose.

Codex. Per the Codex changelog, the feature shipped on June 11, 2026: Go, Plus, Pro and Business users get one free saved reset that expires 30 days after it's credited, and Plus and Pro can earn more via referrals (up to four banked). To redeem one:

  • Desktop or web: Settings > Usage
  • Codex CLI: /usage > Redeem reset
  • The allowance it covers has to be under 80% remaining, or you can't use it.

Per OpenAI's help page, a full banked reset restores the 5-hour and weekly allowance on Plus and Business Standard, and the weekly allowance on Pro tiers. It also changes your weekly reset date, so don't burn it right before your normal reset.

Claude. Anthropic calls it "Reset for free". You'll find it in Settings > Usage on the web or in Claude Desktop. It's not currently available on Claude Mobile or inside Claude Code in the terminal or IDE. It can't be undone once used, it's forfeited if you downgrade or cancel first, and your weekly limits still reset on their usual day.

Expiry matters here. The only Claude banked grant so far came on Sep 22, 2026 (with the Opus 5.5 launch, for Pro, Max and Team) and expired on Oct 22 at 9am PT. Plenty of people only found out it existed after it was gone, so I now show status and expiry for every banked grant.

How the tracker works

Nothing fancy, which is kind of the point:

  • Every entry links to its source post on X. Entries I've checked myself get a "Verified" badge, and ones where the primary link is cited but not yet checked are marked "Source-linked".
  • Part of the data is synced from codex-reset.com and claude-resets.com (credited on the site), merged with my own log, and the site rechecks every few minutes.
  • Each reset gets its own page with the announced and landed times, the lead time, the type (global or banked) and, for banked ones, the expiry.
  • You can get alerts without signing up for anything: there's an RSS feed at /feed.xml, a calendar you can subscribe to, and raw JSON at /resets.json if you want to build something on top of it.

I built the whole thing with Claude Code, which is a little funny given how many of those sessions ended in "5-hour limit reached".

If you just want the one-line answer, it's on the homepage: did Claude or Codex reset today?

TL;DR

  • Your 5-hour and weekly windows reset on their own. Extra resets are separate, ad hoc and unscheduled.
  • Codex resets a lot more often than Claude (median gap 3 days vs 7.5 days in my log).
  • A reset can be announced hours before it reaches your account. The average lag I've measured on Codex is about 9 hours.
  • Banked resets have to be redeemed by you and they expire. Check Settings > Usage.

If you spot a reset I missed, let me know in the comments and I'll add it with its source.

Top comments (0)