How subscription quota is calculated and reset

Monthly subscriptions include a usage allowance. Both 5-hour and weekly limits apply. Actual consumption depends on context length, output size and task complexity.

What affects subscription usage?

Subscription usage depends on the model, context length, cache use, output size and task complexity. Long text and multi-step tool workflows typically use more allowance. Check your dashboard for actual usage and reset times. Failed requests consume no allowance, and internal web searches carry no additional subscription quota charge.

Usage varies with your tasks:

• Everyday questions, code completion and small edits typically use less allowance.
• Long context, larger outputs and multi-step agent tasks use allowance more quickly.

5-hour and 7-day windows

Paid subscriptions use separate fixed 5-hour and 7-day windows, timed from each window’s start. Usage for a window resets when it expires, and the next call opens a new window. Check the Console or usage API for your reset times. If either window has insufficient quota, further calls can receive a 429 rate-limit response. Failed requests consume no quota, and subscription overage charges are not added automatically.

Compare workflows on the plans page. To see usage live in Claude Code: Usage in Claude Code.

What a 429 means

• concurrency_limit: concurrency over your plan cap — slow down, reduce parallel calls, or compare higher-tier plans.
• window/quota: 5h or weekly window usage exhausted — wait for reset or upgrade.
• upstream_busy: transient upstream load — usually clears shortly.