Guide · Claude Code
Claude Code usage limits, explained
Two limits, one shared pool. Here’s how the five-hour and weekly windows work, how to check them, and what to do when Claude Code says you’re out.
By Thomas Kanze
Last checked October 9, 2026. Limits change; the sources linked below are the final word.
The short version
On a Claude Pro or Max plan, Claude Code has two limits running at once: a session limit that resets every five hours and a weekly limit. Max plans add a separate weekly limit for Fable. Claude Code shares these limits with claude.ai and Claude Desktop. To see where you stand, run /usage inside Claude Code.
There’s no fixed message count to memorize. Anthropic says usage depends on how long and complex your conversations are, the features you use, the model and the effort level. So a long agentic session with big files burns through a window much faster than a few short questions.
How the two windows work
The five-hour session limit
Anthropic’s help center describes the session limit as resetting every five hours. Claude Code’s error docs call it a rolling usage allowance. When it runs out, Claude Code blocks further requests until the reset time printed in the message.
The weekly limit
On top of sessions there’s a weekly cap. For Max, Anthropic says it applies across all models and resets at a fixed time each week assigned to your account. That time stays the same no matter when you start using Claude or when your subscription began. Max plans also have a separate weekly limit for Fable.
They count at the same time
Every request counts against both the session and the weekly allowance. Claude Code’s docs warn that a big burst of work can use up the weekly allowance before the session window even resets. If you lean on Claude Code all week, keep an eye on the weekly number as well as the session one.
Pro vs Max
- Pro: both limits, shared with claude.ai and Desktop.
- Max 5x: five times Pro’s per-session allowance, plus the weekly limits.
- Max 20x: 20 times Pro’s per-session allowance, plus the weekly limits.
Note the wording: the multiplier is per session. Anthropic doesn’t describe it as a multiple of Pro’s weekly allowance. Team and Enterprise seats work differently. Each member draws from a per-seat allowance with a rolling five-hour window and a weekly window.
How to check your usage
/usagein Claude Code. Shows plan usage bars and when they reset./costand/statsopen the same screen. On paid plans it also breaks down what’s eating your allowance: skills, subagents, plugins, MCP servers, long context or cache misses. That breakdown is estimated from session history on this machine only.- Settings → Usage on claude.ai. Shows your next reset times and your usage-credit settings. It also counts usage from claude.ai and other devices.
- The status line. Claude Code can pipe your five-hour and weekly percentages and reset times to a custom status line script. See showing limits in the status line.
/status. Shows version, model, account and connectivity, which is handy for confirming you’re signed in with your subscription and not an API key. Anthropic’s plan article also mentions/statusfor monitoring your allocation. In current builds the usage bars are under/usage.
You’ll also get warning messages as you approach a limit. If you’d rather see the number before the warning, Quotchi keeps your Claude Code and Codex usage and reset times in the Mac menu bar, with alerts you set yourself.
What to do when you hit a limit
The message tells you which limit you hit and when it resets:
You've hit your session limit · resets 3:45pm
You've hit your weekly limit · resets Mon 12:00am- Check which limit it is. Session and weekly limits apply across all models, so switching models won’t help. If the message names one model family, like Opus or Sonnet, switching to a model outside that family with
/modelkeeps you working. - Wait it out, automatically. In an interactive session signed in with a claude.ai subscription, Claude Code can wait and pick the interrupted task back up after the reset.
/rate-limit-optionslists this option on v2.1.234 or later. - Use usage credits. On Pro and Max,
/usage-creditsopens Settings → Usage, where you can turn on pay-as-you-go usage past your limit. Monthly API credits included with Max can’t be used in Claude Code. - Upgrade if you hit limits all the time: Pro to Max 5x, or Max 5x to Max 20x.
One trap to avoid: if ANTHROPIC_API_KEY is set in your environment, Claude Code uses that key instead of your subscription, and you pay API rates.
Why a session drains faster than expected
Claude Code’s cost docs list the usual causes. Each request resends the whole conversation, so a session left open all day costs more per question. After a break longer than the prompt cache lifetime (an hour on a subscription), the next message reprocesses everything. Subagents, agent teams, scheduled loops and /compact all send requests of their own. Use /clear between unrelated tasks and check the /usage breakdown to see what’s heavy.
Want the number without asking for it? Quotchi is a small Mac menu bar app that shows Claude Code and Codex usage, reset times and gentle alerts. It’s Free, local-first, and needs no account.
See how Quotchi worksEvery limit type at a glance
Claude Code can stop you for several different reasons. The wording of the message tells you which one, and that decides what helps:
Limit types, messages and fixes
| Limit | Message | Scope | What helps |
|---|---|---|---|
| Session | You've hit your session limit · resets 3:45pm | All models; shared with claude.ai and Desktop | Wait (auto-continue), usage credits |
| Weekly | You've hit your weekly limit · resets Mon 12:00am | All models; fixed weekly reset | Usage credits, a limit reset if offered, wait |
| Opus / Sonnet | You've hit your Opus limit · resets 3:45pm | One model family | /model to another family |
| Fable (Max) | Fable limit reached · continuing on Fable 5.1 uses usage credits… | Fable models on Max | Confirm credits, or /model |
| Monthly spend limit | You've hit your monthly spend limit | Your usage-credit cap | Raise it in Settings → Usage |
| Not a usage limit | 529 Overloaded, temporarily limiting requests | Server capacity | Retry, check status.claude.com, switch model |
The full walkthrough, including a decision tree, is in Claude Code usage limit reached: what to do.
A worked week
Example
Monday and Tuesday are heavy: two long refactors, and on Tuesday afternoon you hit You've hit your session limit · resets 5:20pm. Claude Code waits and continues at 5:20pm. By Thursday the session windows are fine, but /usage shows the weekly bar past 80%. You keep Thursday’s tasks small, run /clear between them, and save the big migration for after your weekly reset. Nothing here needed a bigger plan, just knowing which bar was filling.
If the same pattern repeats every week, that’s when Anthropic’s advice applies: consider Max 5x if you consistently hit limits on Pro. See Max vs Pro.
Keeping work moving
Automatic continue
From v2.1.234, when a claude.ai usage limit stops Claude mid-task, Claude Code waits in the open session and continues after the reset. It’s on by default in interactive sessions signed in with a claude.ai subscription. You’ll see:
Usage limit reached · limit resets 3:45pm
Continuing automatically at 3:45pm · esc to cancelIt won’t start on its own for a reset more than 24 hours away, which usually means a weekly limit; pick Wait here, then continue automatically from /rate-limit-options instead. Turn it off with Continue automatically at usage limit in /config.
Usage credits
Anthropic’s help center says usage credits work on Pro, Max 5x and Max 20x, are billed at standard API rates separately from your subscription, and apply to Claude Code. Set a monthly spend limit when you turn them on. While you’re drawing on credits, the main conversation’s prompt cache drops from one hour to five minutes.
One-time limit resets
Anthropic occasionally gives eligible plans a free reset. Use it from Settings → Usage on the web or in Claude Desktop; it isn’t available in Claude Code in a terminal or IDE.
Common mistakes and myths
“Max 20x has 20 times the weekly limit.”
Anthropic describes 20 times Pro’s per-session allowance. It doesn’t describe the weekly limit as a multiple.
“Switching to Sonnet gets me past the limit.”
Only past an Opus-specific limit. Session and weekly limits apply across all models.
“My chat on claude.ai doesn’t count.”
It does. Anthropic says limits are shared across Claude and Claude Code.
“Max’s API credits cover Claude Code overflow.”
Anthropic says monthly API credits included with Max can’t be used in Claude Code or the Claude apps.
“/compact saves usage.”
It can shrink future requests, but the summarization is itself a request that reads the whole conversation. /clear costs nothing.
What changed recently
As of October 9, 2026, automatic continue at the usage limit (Claude Code v2.1.234) is on by default for claude.ai sign-ins. /usage shows last-known bars when the usage request is rate limited (v2.1.208), and a usage-credits row as soon as credits are on (v2.1.236). Max plans also list a separate weekly limit for Fable. Anthropic publishes these as version notes, not calendar dates.
Sources
Official pages we read on October 9, 2026. If anything here disagrees with them, they win.
- Claude Help Center: Use Claude Code with your Pro or Max plan
- Claude Help Center: How do usage and length limits work?
- Claude Help Center: What is the Max plan?
- Claude Code docs: Manage costs effectively (/usage)
- Claude Code docs: Errors (usage limit messages)
- Claude Code docs: Commands
- Claude Code docs: Customize your status line
- Claude Help Center: Manage usage credits for paid Claude plans
FAQ
Does Claude Code share limits with claude.ai?
Yes. Anthropic says usage on claude.ai, Claude Code and Claude Desktop counts towards the same usage limit, and IDE usage counts too.
How many messages do I get every five hours?
Anthropic doesn’t give a fixed count. It depends on conversation length and complexity, features, model and effort level. Max 5x and Max 20x get 5 and 20 times Pro’s per-session allowance.
Which command shows my Claude Code usage?
Run /usage. It shows plan usage limits and when they reset; /cost and /stats are aliases. Settings → Usage on claude.ai also shows your next reset times.
Will switching models get me past a session limit?
No. Session and weekly limits apply across all models. Only a model-specific limit, such as an Opus or Sonnet limit, can be worked around by switching to a model outside that family.
Can I keep working after hitting the limit?
On Pro and Max you can turn on usage credits (/usage-credits), which bill pay-as-you-go past your limit. Otherwise wait for the reset time shown in the message, or upgrade your plan.
Does Fable have its own limit?
On Max plans, yes. Anthropic lists a separate weekly limit for Fable. When it’s reached, continuing on Fable uses usage credits after you confirm.
Does auto-continue work for the weekly limit?
Not on its own. Claude Code doesn’t start the wait automatically when the reset is more than 24 hours away, but you can start it from /rate-limit-options.
Why did I hit the limit so fast?
Each request resends the whole conversation. Long sessions, cache misses after breaks over an hour, subagents and scheduled loops all add up. The /usage breakdown shows what was heavy.
Is a 529 error a usage limit?
No. Claude Code’s docs say a 529 Overloaded error is a capacity issue and doesn’t count against your quota.