Troubleshooting · Quota

When you see "Claude usage limit reached"

First tell the 5-hour rolling window from the weekly cap. The +50% weekly boost ran 2026-05-13 to 2026-09-13 and is over; @ClaudeDevs gave 2026-09-14. Recovery paths are completely different.

Updated 2026-09-21

#Quota#5-hour window#Weekly cap#Claude Code

Four things to know

5 hours

Rolling window

A short-cycle cap on a rolling window. It restores on its own — nobody needs to be contacted.

Weekly

Weekly cap

A longer-cycle total. Once you hit it, waiting out the 5-hour window will not help.

+50%

Temporary boost (ended)

Help Center, fetched 2026-09-20, is past tense: the +50% weekly boost ran 2026-05-13 to 2026-09-13; @ClaudeDevs 2026-08-29 gave 2026-09-14, one day later. From 2026-09-14 weekly limits are 25% above pre-promotion.

00:00 / 02:00

Two different reset times

On the QCode side: the daily limit resets at 00:00 Beijing time; booster quota resets separately at 02:00 the next day.

What the message actually says

The full string is usually "Claude usage limit reached. Your limit will reset at …" followed by a specific time. That time is the tell: a few hours out generally means the rolling 5-hour window; a few days out means the weekly cap. Both are set by Anthropic per subscription tier and have nothing to do with your network, client version or API key.

Two official end dates on the record

The Help Center article 15910845, fetched 2026-09-20, reads in the past tense: It ran from May 13 through September 13, 2026. Same article: starting September 14, 2026, weekly limits in Claude Code are 25% higher than before the promotion, for Pro, Max, Team and legacy seat-based Enterprise; 5-hour limits were outside this promotion. The earlier @ClaudeDevs post of 2026-08-29 said +50% until September 14. Those two end dates differ by a day and stay separate. Putting standard about 17% under the promo is our own 1.25/1.50 math, not official wording.

Timeline

Early Aug 2026

Many developers publicly log "most of my allowance gone in minutes", usually alongside parallel threads and whole-repo sweeps.

2026-08-18

On 2026-08-18 Help Center extended the +50% weekly boost to 2026-08-31 and mentioned capacity pressure. That was the wording then; the later line is @ClaudeDevs 2026-08-29 (gave 2026-09-14).

2026-08-29

@ClaudeDevs wrote +50% until September 14. Help Center, fetched 2026-09-20, is past tense: the promo ran 2026-05-13 to 09-13, and weekly limits are 25% above pre-promotion from 09-14.

Work out which one you hit first

What is confirmed

The literal “Claude usage limit reached. Your limit will reset at …” has shown up consistently in public threads. Two dates cover the +50% weekly boost: Help Center, fetched 2026-09-20, gives 2026-05-13 to 2026-09-13; @ClaudeDevs 2026-08-29 gave 2026-09-14. From 2026-09-14 weekly limits are 25% above pre-promotion.

No evidence — do not treat as fact

Some claim that under load the vendor silently routes requests to a smaller or quantised model. We searched public discussion and found no first-person evidence at scale and no official statement, so this page does not make that claim. Being refused, truncated or blocked by a classifier is a different phenomenon from "they swapped the model".

The two caps

Rolling 5-hour window

A short-cycle ceiling. It restores automatically at the time printed in the error. You normally hit it through dense use in a short span.

Weekly cap

A longer-cycle total. After hitting it, waiting for the 5-hour window does nothing — you either wait for the cycle to reset or continue on another path.

Why some people burn it in minutes

Public reports share a few patterns: running several threads in parallel, letting the model sweep an entire repository, and spending the most expensive model on work a small one would finish. One developer logged 23% of the allowance gone in six minutes; another hit the 5-hour cap in twenty minutes with four threads. Tightening scope, forbidding large refactors outright and pushing simple work to cheaper models are the fixes the community keeps confirming.

What QCode can and cannot do here

What it can do: when you are out, switch model family and keep working — one key covers Claude, GPT, Gemini, GLM, Kimi, DeepSeek and Qwen, so you do not need a second subscription. If today’s allowance runs short you can also self-serve a booster pack. What it cannot do: if you are still calling Anthropic’s own line, their 5-hour window and weekly cap still apply. We cannot remove them.

FAQ

How do I tell which cap I hit?

Read the reset time in the error. A few hours out is usually the rolling 5-hour window; a few days out is the weekly cap. It is the fastest and most reliable signal.

Do I need support to lift the 5-hour window?

No — it restores on its own. Treat any offer to "instantly lift an official cap" with suspicion.

Has the official 50% boost ended?

It ended. Help Center, fetched 2026-09-20, is past tense: the promo ran 2026-05-13 to 2026-09-13; @ClaudeDevs 2026-08-29 gave 2026-09-14. From 2026-09-14 weekly limits are 25% above pre-promotion. Our 1.25/1.50 math puts that near 17% below the promo; the official line states 25%. Do not plan capacity on the +50%.

Why does one small fix eat a big slice of the weekly cap?

Usually because the model went out of scope: it swept the repo, questioned the architecture, refactored config, and only then touched the bug. Pinning the scope and forbidding large refactors normally helps a lot.

Does QCode have a 5-hour window too?

No. Personal plans dropped the 4-hour window entirely in July 2026; the only dimension now is a daily limit that resets at 00:00 Beijing time. If it runs short you can self-serve a booster pack, which resets separately at 02:00 the next day — deliberately two hours later than the daily limit, leaving a buffer for work that runs past midnight.

Will switching to QCode make this error go away?

If you are still calling Anthropic’s own line, their caps still apply. The value is that when you run out you have other model families to switch to immediately — not that the official cap disappears.

Sources

Error literal from publicly searchable developer threads. +50% weekly boost: Help Center article support.claude.com/en/articles/15910845 (fetched 2026-09-20, past tense: “It ran from May 13 through September 13, 2026”; “starting September 14, 2026, weekly limits … are 25% higher than they were before the promotion”). Other date: @ClaudeDevs 2026-08-29 16:47 GMT, post 2093742321473065266 (“+50% until September 14”). The 17% gap is our 1.25/1.50 math. Rechecked 2026-09-20.

Out of quota? Six other model families are still there

One key across seven model families; the daily limit resets at 00:00 Beijing time and boosters are self-serve.

Related reading

Official limits and the temporary boost follow Anthropic's published wording. This page keeps the end dates apart: Help Center fetched 2026-09-20 (the promo ran 2026-05-13 to 2026-09-13) and @ClaudeDevs 2026-08-29 (until 2026-09-14), plus limits 25% above pre-promotion from 2026-09-14. QCode reset timing follows this site's pricing page.

Try first, then decide

Not sure which tier? Start with Starter ($8.57/mo) and upgrade when you're happy — the unused value of the old plan goes back to your balance.