claudeusage.dev

Verified against Anthropic documentation · Updated

Claude usage limit reached: what happened and what to do now

When you see a Claude usage limit reached notice, Claude has paused new prompts because you exhausted either your 5-hour session allowance or your account's weekly limit. Your chat interface or Settings › Usage displays your exact reset time. To keep working immediately, you can enable pay-as-you-go Usage Credits, switch Claude Code to an API key, or wait for the scheduled reset.

Immediate troubleshooting summary
  • •
    Which limit paused you: Check your chat banner or Settings › Usage. A session pause shows 5-hour limit reached - resets [time]; a weekly pause reflects your account's weekly limit schedule.
  • •
    Your prompt access is paused, not your account: Reaching a limit is a usage-cap event, not an account suspension. You can still view past conversations and account settings while waiting.
  • •
    How to keep working immediately: Eligible accounts can continue via Usage Credits at standard API rates (enabled in Settings › Usage for Pro and Max, or by an Organization Owner for Team members), or switch Claude Code to an API key.
  • •
    Reset is automatic: Your included allowance restores automatically when the scheduled reset time arrives—no logout, restart, or cache clearing required.

How to tell which limit you hit: 5-hour vs. weekly

Claude accounts operate under two separate limits at the same time. Knowing which one stopped you determines whether you are waiting a couple of hours or until your weekly reset day:

5-Hour Session Limit

Resets every 5h

Applies across Claude.ai, desktop apps, and Claude Code. When reached, Claude displays an explicit notice directly in your chat:

5-hour limit reached - resets [time]

When that reset time arrives, your session allowance restores automatically. For full mechanics, see our 5-hour limit guide.

Weekly Account Limit

Resets weekly

Relevant paid plans also carry weekly usage limits that apply across all models. In Settings › Usage, Claude displays your weekly usage information and when your account's weekly limits reset.

Resets once every 7 days at a fixed day and time assigned to your account. For reset schedules, see our weekly limit guide.

Model-specific weekly views: In Settings › Usage, Anthropic exposes separate weekly usage information for “Opus only” and “all other models.”

How long until your Claude limit resets?

You do not need to guess, calculate from your first message, or convert time zones manually. Your reset timing is already tracked directly in your account:

In the web or desktop chat notice: When a 5-hour limit is reached, Claude displays the explicit local reset time in the blocking notice (for example, 5-hour limit reached - resets 4:30 PM).
In Settings › Usage: Click your profile avatar in the lower-left corner and open Settings › Usage. Claude shows progress toward the current five-hour session limit, the amount of time remaining in that session, and when the weekly usage limits reset.
In Claude Code: Run /usage in any active terminal session to view your plan's usage limits and current rate-limit status.

Resets do not happen at midnight or Sunday midnight. When the stated time arrives, your included allowance restores automatically. For detailed timing mechanics and misconceptions, read our reset timing guide.

What can you do right now to keep working?

If you have urgent work and cannot wait for your scheduled reset, several immediate options are available depending on your plan:

1

Enable Usage Credits (Fastest continuation)

Subscribers on eligible plans can enable optional pay-as-you-go Usage Credits to continue prompting after reaching included limits at standard API rates.

Individual plans (Pro, Max 5x, Max 20x): Subscribers can enable Usage Credits for their account in Settings › Usage. Normal five-hour session limits continue to reset as usual; Anthropic explicitly states that Usage Credits do not affect five-hour reset timing.
Team and seat-based Enterprise: Usage Credits must be enabled and configured by an Organization Owner or Primary Owner. Once enabled for the organization, eligible members can continue past included seat limits at standard API rates. (Current usage-based Enterprise plans do not use credits because usage is consumption-billed directly).
In-chat notice change: Once active, the five-hour notice updates to 5-hour limit resets [time] - continuing with usage credits.

For token pricing details, discounted prepaid bundles, and spend controls, read our usage credits guide.

2

Check for a /limit-reset grant in Claude Code

If you are working in the Claude Code CLI, your session may offer the built-in /limit-reset command. In publicly observed use, this unblocks an active 5-hour session limit when a reset grant is available for your account (weekly limits continue to apply).

Reset availability is determined server-side, so check your terminal rate-limit options or run /limit-reset to see if a grant is currently offered.

3

Switch Claude Code to an Anthropic API key

Claude Code prioritizes an ANTHROPIC_API_KEY environment variable over subscription credentials. Setting an API key switches Claude Code onto Anthropic's separate API billing system rather than using your subscription's included allowance:

export ANTHROPIC_API_KEY="sk-ant-..."

API usage is billed separately from your Claude subscription and requires the associated Anthropic Console account to have active billing or credits. It remains subject to Anthropic API rate limits and will pause if prepaid API credits run out.

4

Wait for the automatic reset

If your pause is on a 5-hour session window, the wait is typically between 30 minutes and a few hours. Because past conversation history remains readable, you can review drafts and prepare next prompts offline until the clock reaches your reset time.

What still works while your Claude usage is paused?

Reaching a usage limit is a standard usage-cap event, not an account suspension or ban. You are not locked out of your account:

Past conversations and account access

You can still open, read, and review your previous conversations, check account settings, and inspect your usage status.

Only new prompt submissions are paused

Claude only pauses sending new messages under your exhausted included allowance until your scheduled reset time arrives or additional usage is enabled.

Why did your Claude limit drain so quickly?

Anthropic does not enforce limits with a simple message counter. Your usage is consumed dynamically based on factors documented by Anthropic, including:

  • •Message and conversation length
  • •Conversation complexity
  • •File attachment size
  • •Model choice
  • •Effort level (such as extended thinking)
  • •Tools and features (Research, web search)
  • •Artifact creation and usage

Anthropic notes that longer conversations consume more of your usage limit, and recommends starting a new conversation for a new topic when appropriate.

Need a larger included allowance? Compare plan tiers and session multipliers in our plan limits reference.

How to track your usage so you don't hit the limit unexpectedly

Before you reach 100%, Claude displays an in-app notice: Approaching 5-hour limit. On web and desktop, Settings › Usage tracks progress toward your current five-hour session limit and shows when weekly limits reset. In Claude Code, /usage displays your plan's usage limits and current rate-limit status.

If you want continuous visibility while working, you can use claude-usage—a free local tracker that monitors your 5-hour session and weekly limits in your macOS menu bar, terminal, or localhost dashboard.

CLI + local web dashboardmacOS · Linux
$curl -fsSL https://www.claudeusage.dev/install.sh | sh
Download Mac appmacOS 13+ · Universal ZIP

Reuses your existing local Claude Code OAuth session and connects directly from your machine to Anthropic for usage data. Your credentials, prompts, code, and usage metrics are never sent to claudeusage.dev. See the full breakdown on the tracker installation page.