Claude Usage Limit Reset: How to Check Limits with /usage
On September 22, 2026, Anthropic's Claude Opus 5.5 launch page mentioned two things about usage limits: an increase to the five-hour usage limits, and a one-time rate limit reset that subscribers can save and use whenever they choose. That is everything the official announcement says about the Claude usage limit reset. Anthropic did not publish new numbers, so this article does not claim a multiplier. Below is only what you can verify on official pages, plus how to check your own limits in Claude Code. Everything here is current as of October 2026.
What exactly did Anthropic say?
The launch page says: "we're increasing five-hour usage limits on Pro, Max, Team, and seat-based Enterprise plans." And: "We're also providing subscription users a rate limit reset, which you can now save and use whenever you choose." (Source: Anthropic's official launch page)
As a table:
| Item | Officially stated | Not stated |
|---|---|---|
| Five-hour limit | Raised on Pro, Max, Team, and seat-based Enterprise | How high it went |
| Rate limit reset | One per subscriber, can be saved, you choose when to use it | Expiry, where to trigger it, whether it stacks |
| Other plans | Non-seat-based Enterprise is not mentioned | Whether it applies |
Multipliers measured by third parties and circulating online are reference points only, not official data. For how to claim and use the reset, follow the official help center and the prompts in your own account.
What is the difference between the five-hour window and the weekly limit?
They are counted separately. The five-hour limit works on a rolling short window: once you hit it, it recovers after some waiting. The weekly limit is a cap over a longer period. Anthropic only mentioned raising the five-hour limit this time and said nothing about the weekly limit changing. So if you get blocked in the middle of the week, don't assume it's the five-hour window. To find out which one you hit, check the message in Claude Code and run /usage. If you want to compare how the plan tiers are structured, read What's the difference between Claude Max 5x and 20x.
How do I check my limits in Claude Code?
- Type
/usagein Claude Code to see your current plan's usage. - Read the text of the message you got when blocked to tell whether it was the five-hour window or the weekly limit. Claude Code 2.1.283 fixed a bug where
/usagedid not show the weekly model limit when telemetry was turned off. If you disabled telemetry and don't see that line, upgrade first (Source: Claude Code changelog). - Subscribers can use
/rate-limit-options. The changelog shows that 2.1.284 added it to/helpand the command menu, so the command mentioned in limit messages is easier to find. - For users already on the top Max tier, starting with 2.1.284 the limit warning and
/upgradepoint to/usage-credits(when available) instead of suggesting an upgrade.
The exact options and output of these commands depend on your local version and the official docs.
What if an unattended job hits the limit?
If you run long tasks with the retry watchdog, version 2.1.301 (October 15, 2026) added the environment variable CLAUDE_CODE_RETRY_WATCHDOG_MAX_USAGE_LIMIT_WAIT_MS. When the limit will take a long time to reset, unattended retry mode ends the request instead of waiting indefinitely. The name ends in MS, so treat the unit as milliseconds. The official changelog gives no default or recommended value, so try it on a small task first.
export CLAUDE_CODE_RETRY_WATCHDOG=<value per official docs>
export CLAUDE_CODE_RETRY_WATCHDOG_MAX_USAGE_LIMIT_WAIT_MS=<milliseconds>
For handling this together with 529 overloaded errors, see Claude Code hits 529 Overloaded and usage limits.
When should I use the reset?
Anthropic only says you can pick the timing and gives no rules. What follows is a way of thinking about it, not official advice:
- If you hit the five-hour limit but it will recover on its own soon, there is no rush to use it.
- If you hit a limit and have work that can't wait, then consider using it.
- Run
/usagefirst to confirm which limit you hit, and don't spend the reset before you know.
My quota suddenly disappeared. Is it me or the service?
It isn't necessarily that you used too much. Check official status first, then see whether others report the same thing:
- Check the probe results for Anthropic's official status page to see whether the API has problems.
- Go to the Is Claude down page or the Claude Code page to see community reports. Both pages support one-click reports such as "rate limited," "quota was reset," and "logged out," and you can submit one when it happens to you.
- For how to read status pages, see How to read the OpenAI and Claude status pages.
Codex users run into similar quota issues; see the Codex usage limit reset timeline, whose tracking method you can borrow.
Summary and next steps
- Officially confirmed: five-hour limits went up, and subscribers get one savable reset; the numbers were not published.
- Run
/usagefirst, then decide whether to spend the reset. - For unattended jobs, you can set a maximum wait to avoid idling for a long time.
