Why did my weekly limit reset early?
Most likely the vendor reset everyone. Match the date against the reset log on whenreset to see which one it was. On Codex, the next weekly reset is 7 days after your first message following the reset, so send one right away. On Claude, your weekly reset time does not move, so the reset is a free extra.
Codex
OpenAI reset everyone. Your next weekly reset is 7 days after your first message following the reset.
Find the closest entry in the Codex log on whenreset; if the date matches, that is the one. A reset for everyone applies directly, with nothing to click. After it, the new week starts with your first message, and the next weekly reset is 7 days later. So send a message as soon as you see the reset: wait a day and the next reset comes a day later. This is also why your weekly reset time keeps changing. Each reset for everyone, and each banked reset you use, restarts the 7 days from the first message after it.
What the official docs say
An automatic reset is applied directly to the usage limits covered by the announcement. The automatic reset itself is not saved for later. Usage after it is applied counts toward your refreshed allowance.Your new weekly usage period starts with your first request in Work or Codex after the reset is applied, regardless of whether you have any remaining usage. Your next automatic weekly reset is scheduled 7 days after that first request.Using a full banked reset refreshes your 5-hour and weekly Codex usage windows and changes your weekly reset date. Check Settings → Usage for your updated reset time.Claude
Anthropic reset everyone. Your own weekly reset time stays the same, so it is a free extra.
Match the date against the Claude log on whenreset first. Your weekly reset time on Claude is fixed to your account and is always the previous one plus 7 days. A reset for everyone clears your usage, and your scheduled weekly reset still arrives on time and clears it again. There is no need to rush a message out the way you would on Codex. Your next weekly reset is in /usage in Claude Code, or in Settings › Usage on claude.ai.
What the official docs say
Weekly limits reset at a fixed time each week that is assigned to your account. Your reset day and time stay the same regardless of when you start using Claude or when your subscription begins, and you receive your full weekly allowance each cycle. You can see your next reset time in Settings > Usage.Today we are resetting usage limits for all subscribers.A reset was announced, but my usage did not change
First check that the reset covers your product and your limits, then refresh the usage page. Work through these in order.
Open the original post from the entry on whenreset and read what it says. Every entry is labelled with its type and links to the official post. Two mismatches are most common. The post granted a banked reset, which does nothing until you use it on your usage page. Or the reset was for another product, such as one given only to Grok Bot users.
Refresh the usage page. OpenAI notes that the usage dashboard can take a short time to update. When Claude Code cannot fetch fresh numbers, /usage shows data from the last 60 minutes with a note that reads Showing last-known usage; press r to fetch again.
Check that you are signed in with your subscription. On Codex, check the account and the workspace. Claude resets for everyone cover subscribers; Claude Code signed in with an API key has no plan allowance to reset.
On Codex, if it still looks wrong, contact support. OpenAI support does not reset limits by hand, but OpenAI says to contact them if a reset you were eligible for was not applied, or if access has not returned after the reset time shown. Anthropic has not published an equivalent route.
What the official docs say
OpenAI may occasionally provide eligible users with a one-time reset of Codex or ChatGPT Work usage limits. Eligibility, the limits affected, and any redemption or expiration requirements may vary by offer.Your usage dashboard may take a short time to update.When the request for your plan limits fails, most often because the usage endpoint is rate limited, /usage shows the last usage bars it loaded on this machine within the past 60 minutes, along with a Showing last-known usage note stating how long ago that data was fetched. Press r to retry.Contact Support if your usage appears incorrect, access has not returned after the stated reset time, or you believe a reset you were eligible to receive was not applied as described.Common misconceptions
- An early reset is a bug, and the usage will be taken back in a few days
It will not be taken back. A reset for everyone is announced publicly, and usage after it counts toward the fresh allowance. To confirm that is what happened, match the date in the log on whenreset; every entry links to the official post.
- After an early reset on Claude, my weekly reset day moved later
It did not. Your weekly reset time on Claude is fixed to your account, always the previous one plus 7 days; a reset for everyone is one extra clear on top. Codex is the one that moves: it counts 7 days from your first message after the reset.
- An announced reset clears every limit for every user
Not always. Which product and which limits a reset covers is set by the announcement itself. Some announcements grant a banked reset, which only takes effect when you use it on your usage page. Every entry on whenreset is labelled with its type and links to the official post.
In practice
- When your usage suddenly drops to zero, match the date in the log on whenreset first. If it matches, it was a reset for everyone and nothing is wrong with your account.
- Codex: send a message right after the reset. The next weekly reset is 7 days from that message; waiting only pushes it later.
- Claude: do nothing. Your weekly reset time does not move, and the scheduled reset still arrives.
- Announced but not applied to you: open the original post from the entry on whenreset, check whether it was a direct reset or a banked reset you have to use yourself, then refresh the usage page.
- Turn on reset alerts on whenreset, so next time you do not have to guess.