Claude usage limit reached — what to do (Claude Code)

Two limits: the 5-hour session limit and the weekly limit

Pro and Max plans have a usage limit per session that resets every five hours, and a weekly limit on top. Anthropic: “Your session-based usage limit will reset every five hours.” And: “Weekly limits reset at a fixed time each week that is assigned to your account.” (Pro plan, Max plan)

Claude and Claude Code draw on the same limits: “all activity in both tools counts against the same usage limits.” (Using Claude Code with Pro or Max) A long chat on claude.ai draws on the same limit as your coding session.

Each request counts against both at once — “Usage counts against the session and weekly allowances at the same time.” — and once you are blocked, another model does not help: “The session and weekly limits are shared across all models, so switching models doesn’t restore access.” (Claude Code docs: errors)

What changed on 14 September 2026

Anthropic ran a promotion with higher weekly limits in Claude Code over the summer. Since then: “starting September 14, 2026, weekly limits in Claude Code are 25% higher than they were before the promotion for Pro, Max, Team, and seat-based Enterprise plans.” The 5-hour limits were not part of it: “5-hour usage limits were not affected by this promotion.” (Anthropic help center)

See where you stand: /usage

Type /usage in Claude Code. On Pro and Max, “Subscribers see plan usage bars, activity stats, and a usage breakdown on the same screen” — including how much skills, subagents, plugins and MCP servers count against your plan. The cost figure in the Session block is meant for API users, not for subscriptions. (Claude Code docs: costs)

The limit message itself names the reset time; Anthropic’s advice there: “Run /usage to see your plan limits and when they reset”. On claude.ai, Settings › Usage shows the same two bars for the five-hour session and the week. (errors, usage limit best practices)

Limit reached right now: wait, buy usage credits, or a bigger plan

Wait for the reset. Claude Code “blocks further requests until the reset time shown in the message.” (errors)
Usage credits. On paid plans: “Instead of being blocked when you hit your session limits, you can switch to consumption-based pricing at standard API rates and continue your work without interruption.” They are “charged separately from your paid Claude subscription”. In Claude Code, /usage-credits manages them. (Manage usage credits, costs)
A bigger plan. “Max 5x includes five times the Pro plan’s per-session usage allowance.” (Max plan)

Use less of your limit: Anthropic’s own tips

Anthropic’s documentation for Claude Code lists these ways to use fewer tokens — and on Pro and Max, fewer tokens means the limit lasts longer (Reduce token usage):

Clear between tasks. “Use /clear to start fresh when switching to unrelated work. Stale context wastes tokens on every subsequent message.” To stay in the same task, /compact with a focus keeps what matters.
Pick the model for the task. “Sonnet handles most coding tasks well and costs less than Opus.” Switch with /model.
Lower the effort level for routine work with /effort (or in /model). Higher effort uses more tokens.
Turn off MCP servers you do not use: run /mcp and disable them.
Keep CLAUDE.md short: “Aim to keep CLAUDE.md under 200 lines by including only essentials.”
Hand verbose work to subagents, so only a summary returns to your conversation — but “The subagent’s own requests still draw on your usage.”
Careful with agent teams: they “use approximately 7x more tokens than standard sessions when teammates run in plan mode”.

Token-saving plugins

Free plugins promise to save tokens — for example caveman (shorter answers) and context-mode (keeps large tool output out of the context, by its own description). They are popular and free to try. Advertised and measured savings can differ: JetBrains measured caveman on 86 tasks and wrote “Advertised saving: 65%. Measured saving: 8.5%.” — a measurement by JetBrains, not by us (JetBrains AI blog, July 2026).

The fair test is your own work: note your bars in /usage, work as usual, compare. We collected what has been measured — ours and others’ — on Token savers for Claude Code, measured.

One more option: Grace

Our own product — this section is advertising.

Grace is a plugin for Claude Code on Mac and Windows, made by us. You install it once and keep typing your tasks as usual; your plan does more work before the limit. We measured it against Claude Code with caveman and context-mode installed:

Test result

≈ −49 % of the 5-hour limit for the same 60 tasks.

Measured against Claude Code with two token-saving plugins already installed: caveman and context-mode.

Read from the limit in whole percentage points, two measurements added up: 32 % with Grace 0.3.8, 63 % with Claude Code + caveman + context-mode · 60 tasks, Claude Max 20x on both sides · October 2 – 3, 2026: 30 tasks at the same time on two accounts, 30 with the comparison run measured separately on the same day · on the comparison account 54 s of readings are missing at a 5-hour reset, which can only make the saving look smaller

≈ 96–100 %more work in the same limit
Calculated from the limit value above: ≈ 96 % more. On 43 of the 58 tasks both runs finished, at least twice as much: 2.0× to 4.4×, calculated from Claude’s cost per task (quality on those: 94 % with Grace, 93 % Claude alone). 2 more such tasks are not counted because of their quality (45 % with Grace, 93 % Claude alone).
49 %less time
Measured at the same time with Grace 0.3.8 (October 3, 2026): 3 h 41 min with Grace, 7 h 10 min Claude alone — the time of all 30 tasks, added up. Grace was faster on 28 of them; quality: 93 % with Grace, 90 % Claude alone. Only the 30 tasks measured at the same time are compared on time; the other 30 were measured separately.

All measurements, task by task Token savers, measured

Try it yourself: your first month is free, and /usage shows the difference on your own work.

Try free for 30 days

Just create an account · no payment details · ends on its own

Questions

When does the Claude usage limit reset?

The session limit resets every five hours; the weekly limit at a fixed time each week that is assigned to your account. The limit message and /usage in Claude Code show the exact time.

Do Claude and Claude Code share the same limit?

Yes. On Pro and Max, all activity in Claude and Claude Code counts against the same usage limits.

Does switching to another model help once I am blocked?

No. The session and weekly limits are shared across all models. A cheaper model only helps before you hit the limit, because it uses less of it.

Can I keep working after hitting the limit?

Yes, with usage credits on a paid plan: you continue at standard API rates, charged separately from your subscription. Or you wait for the reset time.

Why do I hit the limit so fast?

Long conversations resend their context with every message, high effort levels and large models use more tokens, and MCP servers, skills and subagents add their own usage. /usage shows what counts against your plan. Clear between tasks, pick model and effort for the task, and turn off what you do not use.

Is there a way around the limit?

No legitimate one — and Grace does not bypass it either. You can use less of it (the tips above), buy usage credits, or move to a bigger plan. Grace lets the same work use less of the limit.

Sources

Anthropic’s pages, checked on 2 October 2026. Anthropic changes limits and wording from time to time — their pages are what counts.

What is the Pro plan? support.claude.com
What is the Max plan? support.claude.com
Use Claude Code with your Pro or Max plan support.claude.com
How do usage and length limits work? support.claude.com
Claude Code May–August 2026 weekly limits promotion support.claude.com
Manage usage credits for paid Claude plans support.claude.com
Usage limit best practices support.claude.com
Claude Code docs: Manage costs effectively code.claude.com
Claude Code docs: Errors code.claude.com

More guides

All guides