Verified against official client & documentation · Updated
How the Claude Code /limit-reset command works
The /limit-reset command in Claude Code is a built-in terminal action that can reset an active usage limit when made available to your account. In publicly observed execution, it clears a blocked 5-hour session limit while your weekly limit continues to apply. Newer clients support server-defined reset grants, so verify your active status with /usage after running it.
Fast reference: how /limit-reset operates
| Dimension | Observed Session Reset | Newer Server Grant Capability |
|---|---|---|
| Reset target | Clears the active 5-hour session limit, returning terminal status to allowed. | Client can represent server-defined targets including 5-hour and 7-day limit types. |
| Weekly limit status | Weekly limit remains in place. Work completed after resetting continues drawing down weekly quota. | Server payload defines target limits. Resetting weekly limits via grants has not been verified in real-world public reports. |
| Reset allowance & cadence | Historically described in client copy as once weekly (1/week) with a cooldown date. | Grants carry server-defined fields for total resets, remaining resets, start time, and expiration. |
| Command visibility | /limit-reset may not appear in normal slash-command suggestions, so its absence from autocomplete does not by itself establish that your client cannot recognize it. Also surfaced dynamically in terminal rate-limit option dialogs. | |
| Applicable accounts | Primarily relevant to Claude Code sessions using an included plan or seat allowance. Anthropic has not published the exact plans or accounts eligible for manual reset grants. API-key sessions use pay-as-you-go API billing rather than subscription limits. | |
| Verification method | Run /usage before and after invocation to confirm active rate-limit status and verify which limit was cleared. | |
What /limit-reset resets: observed behavior and server grants
Understanding what /limit-reset does requires distinguishing between what has been observed in production and what recent clients are architected to handle:
1. Observed session-reset behavior
In publicly observed real-world execution, running /limit-reset unblocks an active 5-hour session limit. When successful, the terminal reports:
- Your 5-hour session capacity is unblocked immediately.
- Your weekly account allowance is not reset.
- Prompts submitted after the reset continue to count against your remaining weekly allowance.
- The action has historically been described in the client as once weekly (
1/week), and subsequent attempts during the cooldown period report that the reset has already been used.
2. Newer server-issued reset grants
Recent distributions of Claude Code also contain code for a more flexible reset-grant system. Under this model, Anthropic's backend can return a grant payload defining:
- Total reset count and remaining resets
- Grant start and expiration timestamps
- Specific target limits (the client can represent
five_hour,seven_day,seven_day_opus, andseven_day_sonnet)
/limit-reset will clear a weekly lockout, but do not assume every grant only clears 5-hour sessions. Read your terminal response and run /usage to confirm what changed.How to run /limit-reset in your terminal
You can invoke the command manually in an active Claude Code session:
Rate-limit dialog prompts
When your session hits a usage limit during a prompt turn, Claude Code may present an interactive options menu:
If auto-continue is enabled in your session configuration, selecting the reset option clears the session block and resumes processing your queued turn automatically. If auto-continue is not active, the session unblocks and waits for your next input.
How to verify your limits before and after resetting
Because a session reset does not replenish your weekly pool, running /limit-reset when your weekly quota is nearly exhausted can lead to an immediate weekly lockout. Follow this verification sequence:
Check your weekly quota before running the command
Run /usage in Claude Code before executing a reset:
Review your weekly usage percentage. If your weekly limit is close to 100%, unblocking your 5-hour session may only yield a few messages before your account halts on the weekly ceiling. For details on how weekly allowances are pooled, see our weekly limit guide.
Execute /limit-reset
Submit the command in your terminal session:
Verify which limit changed
Run /usage again immediately after resetting:
Compare your meters before and after invocation. In standard session resets, your 5-hour session meter will restore to active capacity while your weekly meter remains unchanged. You can also monitor your active session metrics with a Claude Code statusline or in Settings › Usage on the web.
Terminal responses and what they mean
When you execute /limit-reset, Claude Code evaluates eligibility with Anthropic's backend and returns one of the following outputs:
1. Reset successful
- Meaning: Your 5-hour session block has been cleared.
- Next reset: The displayed date indicates when your account may next be eligible for a reset under the older cadence. If auto-continue is not enabled, the CLI prompts you to send a message to continue.
- Weekly limit: Prompts continue to consume your existing weekly quota.
2. Reset already used
- Meaning: Your account has already consumed its manual reset allowance for the active period.
- Next step: You must wait for your regular rolling session window to restore access. See our reset timing guide for details on how scheduled resets operate.
3. Reset not available
- Meaning: Claude Code did not make a reset available for your current account or session state.
- Next step: Use
/usageto check your current rate-limit status, and review the alternative continuation options below.
4. Authentication error
- Meaning: The client could not validate your credentials with the reset service.
- Next step: Run
/loginin your terminal to refresh your session credentials, then re-try/limit-reset.
Why does it say “A session-limit reset isn't available right now”?
If running /limit-reset returns A session-limit reset isn't available right now., Anthropic has not published enough information to determine the exact reason from that message alone. Current client behavior reflects states consistent with:
- No qualifying active limit: The command is designed to clear an active usage block. If your account is not currently in a rate-limited state, the server will not execute a reset.
- No reset grant currently provisioned: Availability is governed dynamically on Anthropic's backend. The feature is not guaranteed to be active for all accounts or at all times.
- Grant already consumed or expired: If a previously issued reset grant has already been used or has passed its expiration timestamp, subsequent attempts are declined.
- API-key authentication: If Claude Code authenticates using an
ANTHROPIC_API_KEYenvironment variable, usage is billed per token through the Anthropic Console. Included subscription usage limits and manual reset grants do not apply to API-key sessions.
/usage and use the continuation options currently available to your account.What to do if /limit-reset is unavailable or spent
If a manual reset is unavailable or you have exhausted your allowance, three primary options remain for continuing your work:
1. Continue with Usage Credits
Subscribers on eligible plans (Pro, Max) or Team members with credits enabled by their administrator can continue prompting past limits using pay-as-you-go Usage Credits:
- How it works: Requests submitted after reaching an included limit draw against prepaid credits at standard API token rates.
- Configuration: Enable Usage Credits under Settings › Usage in the Claude web app. See our usage credits guide for setup requirements and spend controls.
2. Authenticate Claude Code with an API key
If you maintain an Anthropic Console account with active billing, you can direct Claude Code to use an API key instead of your subscription credentials:
claude
API-key usage is metered separately per token and bypasses your subscription's 5-hour and weekly caps. Separate Anthropic API rate limits apply.
3. Wait for your scheduled reset
If you do not need immediate access, wait for your standard rolling window to clear. Your chat banner and /usage display your assigned reset time. For an overview of recovery steps when an allowance runs out, consult our limit reached troubleshooting guide.
Frequently asked questions
Does /limit-reset work in Claude for Web or Desktop?
/limit-reset is a Claude Code terminal command. In Claude web and desktop, manual resets are not triggered by slash commands; eligible accounts occasionally receive a saveable “Reset for free” button under Settings › Usage. Otherwise, web and desktop interfaces rely on scheduled rolling resets or Usage Credits.
Does running /limit-reset clear my weekly limit?
In all publicly observed real-world executions, /limit-reset clears only the 5-hour session limit, and the output explicitly states that your weekly limit still applies. While newer Claude Code distributions contain data structures capable of representing weekly-limit grants, real-world public evidence of an account receiving a weekly-limit reset has not been verified. Run /usage after resetting to confirm what changed.
How often can /limit-reset be used?
Under the older observed mechanism, the command is described in the client as once weekly (1/week), and running it displays a cooldown date. Newer client versions support server-issued grants that define their own reset counts and expiration dates. The output returned to your specific account is more authoritative than any universal frequency rule.
Why doesn't /limit-reset show up in my slash-command menu?
Claude Code registers /limit-reset as an unlisted command in client definitions. /limit-reset may not appear in normal slash-command suggestions, so its absence from autocomplete does not by itself establish that your client cannot recognize it.