PRACTICAL GUIDE / CLAUDE CODE USAGE LIMITS

Hit a Claude Code Usage Limit? Reset Times, Extra Usage, and Context Management

You are halfway through a refactor when the terminal says “usage limit reached.” Is this a wait-a-few-hours problem or a come-back-in-a-few-days problem? It depends on which clock you hit. Claude runs on two clocks: a 5-hour session and a weekly cap. Using the official documentation, this guide walks through when each one resets, how to keep working before then, how to stretch your allowance with context management, and how Claude Code can pick the job back up on its own after a reset.

Public-source analysis · Edited by Dandan Dad · Editorial policy

Practical GuideSep 23, 2026 (updated Oct 6)·7 min read

Claude Code
Anthropic

CLAUDE USAGE LIMITS / SESSION + WEEKLYPRO · MAX 5X · MAX 20XUPDATED 2026.10.06

한국어 원문 ↗

TL;DR

Claude has two limits: a 5-hour session limit that starts with your first message, and a weekly cap that resets at a fixed day and time assigned to your account. Start by checking which one you hit.
Can’t wait? First look for a free reset under Settings → Usage on the web or in Claude Desktop. On September 22, Anthropic said it was giving subscribers a reset they can save and use whenever they choose. No reset? Then the options are usage credits (pay as you go at API rates) or a higher plan. Some users report a /limit-reset command, but it is not in the official command list.
/clear and /compact shorten the conversation; they do not give back usage you have already spent. Combined with smaller attachments and tightly scoped tasks, they make the rest of your allowance last longer.

First: Which Clock Did You Hit?

The web app (Claude.ai), the desktop app, and Claude Code draw from one usage pool. Spend the morning polishing a report on the web, and Claude Code may hit the wall the moment you open your terminal after lunch. So when the notice appears, first work out which limit it is.

The session clock rolls; the weekly clock is fixed. If only the session limit is full, you wait five hours at most. If the weekly cap is full, five hours will not fix it.

Where to check

Claude Code: type /usage in the terminal to see your plan usage and reset times. Web and apps: claude.ai/settings/usage shows separate session and weekly bars (all models / Fable), plus your weekly reset day and time.

5hsession window
(from first message)

2xClaude Code 5-hour limit
(since May 6; raised again Sep 22)

+25%permanent weekly increase
(Sep 14; -17% vs promo)

$2,000daily credit top-up limit

When Does the Limit Reset?

Your options depend on which limit you hit. A weekly cap does not clear when the session resets. To keep going before the weekly reset, check for a free weekly reset; otherwise consider usage credits or a higher plan.

The session limit resets five hours after your first message. It runs from when you started, not from midnight: send your first message at 9 a.m. and it clears at 2 p.m. The weekly cap resets at a fixed day and time assigned to your account, and that slot stays the same no matter when you start using Claude. You can see both times with /usage in Claude Code or at claude.ai/settings/usage, so plan heavy work around them. The official docs list no command that brings a reset forward; the only official shortcut is the free reset below.

Free resets: check the web or desktop app

According to Claude’s official help (checked October 6, 2026), eligible plans occasionally receive a free reset. When Anthropic launched Opus 5.5 on September 22, it also said subscribers were getting a rate limit reset they can save and use whenever they choose. To see whether you have one, and when it expires, open Settings → Usage → Resets on the web or in Claude Desktop. Click “Reset for free” and confirm, and either your five-hour session limit or your weekly limit, depending on the offer, goes straight back to full. It cannot be undone, and your usual weekly reset day and time stay the same. You can use it before you hit a limit, but it is worth the most when you are nearly out.

The button is not available in the mobile app or in Claude Code’s terminal or IDE. Because the allowance is shared across your account, though, a reset applied on the web or desktop shows up in Claude Code too. It does not refund extra usage you have already been billed for or change your credit balance. Not every account has one at all times, and it has nothing to do with the unofficial /limit-reset reports below.

The /limit-reset command (not in the official docs)

Since early September, some users have reported seeing a /limit-reset command in Claude Code. The reported output reads “Session limit reset · next reset available (date) · your weekly limit still applies,” which suggests it resets only the 5-hour session limit and leaves the weekly cap alone. As of October 6, the command still does not appear in Claude Code’s official command reference or changelog. Even when it shows up in the menu, it may only reply “A session-limit reset isn’t available right now,” so do not build your plans around it.

Session limit reset · next reset available Sep 4 at 2pm · your weekly limit still applies

Claude Code /limit-reset output (user report on r/ClaudeAI, Sep 2026; not in the official docs)

Keep Working Before the Reset: Usage Credits or a Higher Plan

If you have no free reset, or the one you have does not cover the limit you hit, two paths remain: usage credits that you pay for as you go, or a higher plan with a bigger base allowance.

Usage credits (metered)

Pro, Max 5x, and Max 20x accounts can turn on usage credits under Settings → Usage and prepay funds. Once you reach a limit, you keep working at standard API rates. You can set a monthly cap, auto-reload, and alerts, and you can add up to $2,000 a day. Credits are billed by what you use, which is different from OpenAI’s paid resets, where a set price refills your allowance. In Claude Code, /usage-credits opens the credit settings, and /rate-limit-options shows the wait, add-credits, and upgrade options in one place.

Flat refill vs metered overage

OpenAI’s paid instant reset works like a flat refill. You pay, your 5-hour and weekly allowances go back to full right away, and a new weekly cycle starts with your next Work or Codex request. It does not stack extra usage on top; it pulls next week’s allowance forward, and you cannot save it for later. OpenAI also has banked resets and usage credits, and Anthropic hands out free resets, so you cannot split the two companies neatly into “flat” and “metered.”

Anthropic’s credits are metered overage: only the tokens you use past the limit are billed at API rates. So pointless retries cost real money, and long agent runs add up faster than you expect.

Set a monthly cap before you turn credits on. “Unlimited” plus an overnight agent job equals a surprise invoice in the morning.

Upgrade the plan

Max 5x ($100 a month) gives five times Pro’s session usage; Max 20x ($200 a month) gives twenty times. Max also includes Fable 5.1 within the plan, capped at 50% of your weekly limit. If you run Claude Code for hours every day, a flat Max bill is easier to predict than credits that swing from month to month. Current prices and limit structures are updated weekly in the Limits and Pricing Tracker.

Auto-Continue After the Reset

Since v2.1.234, Claude Code can do the waiting for you. If an interactive session signed in with a claude.ai subscription hits a usage limit mid-task, Claude Code keeps the session open and resumes the task on its own once the limit resets. This is on by default, and while it waits you see a line such as “Usage limit reached · continuing automatically at 3:45pm.” At the reset, Claude Code sends a fixed prompt to pick up where it stopped; it does not resend your last message.

It does not give you more usage. It simply waits for the reset and starts again, so the session has to stay open. If the reset is more than 24 hours away, as it can be with a weekly cap, Claude Code does not start the wait on its own; you can still choose the wait-and-continue option from /rate-limit-options. Press Esc to cancel.

Use Less Going Forward: Context Management

The surest way to hit fewer limits is to use less, and that is where /clear and /compact come in. Neither gives back usage you have already spent, but both cut down what the model has to reread on every turn from here on.

Limits are consumed by compute, not message count. The same one-word “continue” costs more late in a long conversation, because the model rereads everything before it. Official help lists the drivers: message and conversation length, attachment size, tool use (Research, web search), model and effort level, artifacts, and multi-step tasks such as running code or creating files.

The biggest waste is dragging an old conversation along. Start fresh when a task ends; summarize with /compact when you need to keep going.

/clear when a task ends. Start the new task with an empty context instead of stacking it on an old conversation. A simple test: if your next prompt would make sense in a brand-new terminal, clear first. Project memory (CLAUDE.md) stays. The previous conversation is kept and can be reopened with /resume.
/compact when you must continue. Replaces the conversation so far with a short summary. Claude Code auto-compacts near the limit, but doing it early wastes less.
One goal per task. Instead of “refactor the whole project and add all tests,” split the work by module or file and give each piece one goal you can check.
Attach only what is needed. Send the relevant pages instead of a 50-page PDF, and the 20 or 30 lines around the error instead of the whole log.
Match model and effort to the job. Sonnet handles most everyday coding, and Haiku is enough for quick edits. Save Opus or Fable for hard design and tricky debugging. Switch models with /model and effort with /effort.
Project knowledge is cached. Documents you reference repeatedly cost less when they live in a project. Caches expire after inactivity, though, so the first message after a long break counts them in full again.
Make /usage a habit. For example, if you are past 80% and the reset is hours away, save the big job for after it. Pick your own threshold based on the work left.

FAQ

What time does the limit reset?

The session limit has no fixed clock time: it is your first message plus five hours. The weekly cap resets at a fixed day and time per account, shown at claude.ai/settings/usage.

Does web usage count against Claude Code?

Yes. The web app (Claude.ai), the desktop app, and Claude Code share the same pool, and so does Cowork.

I do not see /limit-reset.

That is expected. /limit-reset is not in the official command list and is known only from user reports. The documented free reset is a different thing: check Settings → Usage → Resets on the web or in Claude Desktop. If you have none, wait for the automatic reset or consider usage credits or a plan change.

Does /clear reset my usage limit?

No. /clear and /compact manage conversation context, so usage already spent stays spent. The similarly named /reset is just another name for /clear and does not touch your limits either. After /clear, you can reopen the previous conversation with /resume.

If auto-continue is on, will I stop hitting limits?

No. Auto-continue waits until the limit resets and then picks the task back up. The session has to stay open while it waits.

Do credits remove the session limit?

No. The session limit still resets every five hours; credits only let you choose “continue” when you reach it.

Can I use Fable 5.1 in Claude Code on Pro?

Only with usage credits. Max plans can spend up to 50% of the weekly cap on Fable at no extra cost and continue with credits after that (per official help).

Points to Consider

Good

The 5-hour limit doubled in May, rose again on September 22, and peak-hour reductions are gone
If you have a free reset, you can refill a limit when it suits you
With credits on, you can keep working past a limit, billed in proportion to usage
Managing context with /compact and /clear can reduce usage on later work

Watch out

A weekly cap does not clear with a session reset
/limit-reset has user reports only and is not in the official command list
Auto-continue does not raise the limit; it waits for the reset and resumes
An “unlimited” credit setting plus overnight agents can produce a surprise bill

Based on Anthropic’s official help pages, the Claude Code docs, and Anthropic announcements. The /limit-reset details come from user reports and technology press; the command is not in Claude Code’s official command reference (checked Oct 6, 2026). One Anthropic help article describes /clear as if it deleted the conversation, but the official command reference says you can reopen the previous conversation with /resume. Anthropic does not publish exact token or message counts per plan, or the size of the September 22 increase to five-hour limits. Oct 6, 2026 update: added the September 22 five-hour limit increase, the saveable free reset, and when auto-continue does not start on its own. Policies change often; check the official page before paying.

Sources

Trademark notice · Claude, Anthropic: Anthropic, PBC. Logos and trademarks belong to their respective owners and are used unaltered only to identify the services discussed. Dandan Life is an independent blog and is not affiliated with, endorsed by, or sponsored by any of these companies.