Claude Code usage limits explained: the 5-hour window, weekly limits, and how to check what's left

Claude Code on a subscription runs on two clocks at once: a 5-hour session window and a weekly limit. Here's how each one works, what your plan gets, what happens when you run out, and every way to see how much you have left.

See your 5-hour window in the notchNotchDodo, $9.99 one-time
The short answerOn Pro and Max, Claude Code has a session limit that starts with your first message and resets five hours later, plus a weekly limit that resets at a fixed time assigned to your account. Both are shared with Claude on the web and desktop. Max gets five times Pro's usage; Ultra (formerly Max 20x) gets ten times Pro's weekly usage and, once verified, no 5-hour limit. Anthropic doesn't publish message counts. To check what's left, type /usage in Claude Code or open claude.ai → Settings → Usage.
Limits change. Anthropic says it may adjust usage limits to manage capacity, and plan names have changed recently (Max 20x is now Ultra). Everything here was checked against Anthropic's help center and Claude Code docs on 13 November 2026. Links are in the Sources section.

How the Claude Code 5-hour limit works

If you sign in to Claude Code with a Claude subscription, you aren't billed per token. Instead you get a usage allowance, and the shorter of the two allowances is the session limit, usually called the 5-hour limit. Anthropic's help center puts it simply: the five-hour period starts with your first message and resets five hours later.

A few things follow from that, and they trip people up:

  • It isn't a fixed clock. Send your first message at 9:12am and that window resets at 2:12pm. Nothing is running before you start, so a quiet morning doesn't "use up" anything.
  • It's shared. Anthropic says usage across claude.ai, Claude Code and Claude Desktop all counts towards the same limit. A long research chat in the browser eats into the same window as your terminal.
  • Work isn't measured in messages. Usage depends on conversation length and complexity, the features and tools you use, the model, and the effort level. Claude Code sends your whole conversation with every request, so one question in a session that's been open all day costs far more than the same question in a fresh one.
Timeline of one day: a 5-hour window opens at 9:12am with the first message, the limit is hit at 12:36 until 2:12pm, the Mac sits idle, then a second window opens at 3:06pm and resets at 8:06pm, with a weekly limit bar underneath covering every window
An illustrative day. Each window starts with your first message; every window also counts towards the weekly limit.

How the Claude Code weekly limit works

Underneath the 5-hour window there's a weekly limit that applies across all models. Unlike the session window, it doesn't start when you do: weekly limits reset at a fixed time each week that is assigned to your account, and that time stays the same however you use Claude. You can see it under Settings → Usage.

Claude Code's docs point out that usage counts against the session and weekly allowances at the same time, so one burst of heavy work, such as fanning a big task out to many agents, can use up the week before the 5-hour window even resets. On Max and Ultra there is also a separate weekly limit for Fable models. Claude Code's error reference also lists model-family limits, "You've hit your Opus limit" and "You've hit your Sonnet limit", which only block that one family.

Claude Pro vs Max vs Ultra: Claude Code limits by plan

Anthropic describes its plans relative to Pro rather than in messages or tokens. Here is what each plan gets, in Anthropic's own terms. Prices are US web prices; mobile pricing can differ.

PlanPrice5-hour session limitWeekly limit
Pro$20/monthYesYes, across all models
Max (the 5x tier)$100/monthYes, 5x Pro's usage every five hours5x Pro, plus a separate Fable limit
Ultra (formerly Max 20x)$200/monthNone for verified accounts10x Pro, plus a separate Fable limit
Team / EnterprisePer seatRolling five-hour window per seatWeekly window; size depends on Standard or Premium seat
API key / ConsolePay per tokenNo plan limitsNo plan limits; API rate and spend limits apply

Two notes. First, Anthropic's help center says the Max 20x plan is now called Ultra and existing subscribers moved over automatically at the same price. New Ultra accounts keep a temporary limit until Anthropic verifies them from account and payment history; if there's no current session bar in Settings → Usage, you're verified. Second, Anthropic doesn't publish how many prompts or tokens any plan gets. Figures you see quoted online, like "40 prompts per 5 hours", are other people's estimates, often from older plan versions.

One more trap: if the ANTHROPIC_API_KEY environment variable is set, Claude Code authenticates with that key instead of your subscription, and you pay API rates. Anthropic's fix is to run claude logout, then claude login with your plan credentials only.

How to check your Claude Code usage

1. The /usage command

The quickest check is built in. At the Claude Code prompt, type:

Claude Code
/usage

According to Anthropic's docs, on a Pro, Max, Ultra, Team or Enterprise plan this shows your plan usage bars with reset times, activity stats, and a breakdown of what counts against your limits: the share used by skills, subagents, plugins and individual MCP servers, and suggestions such as trimming a large CLAUDE.md. Press d or w to switch between the last 24 hours and the last 7 days. /cost and /stats are aliases, and /usage runs immediately even while Claude is busy.

The dollar figure in the Session block at the top is computed locally at API list prices. Anthropic notes it's meant for API users; on a subscription it isn't what you pay. /status is different: it shows your version, model, account and connectivity, which is handy for confirming you're signed in with your subscription and not an API key.

2. claude.ai Settings → Usage

On the web, open claude.ai, then Settings → Usage. Anthropic says this page shows your current session and the time remaining, plus your next weekly reset. It's also where you turn usage credits on or off. In the Claude desktop app, the usage ring under the prompt box opens the same plan usage.

3. A status line that never goes away

Claude Code can run a script to draw its status line, and for Pro, Max and Ultra subscribers it passes in rate_limits.five_hour and rate_limits.seven_day, each with a used_percentage and a resets_at time. The fields appear after the first response in a session. A minimal version of the script from Anthropic's docs (it needs jq):

~/.claude/statusline.sh
#!/bin/bash
# ~/.claude/statusline.sh: show 5-hour and weekly usage in Claude Code's status line
input=$(cat)
FIVE_H=$(echo "$input" | jq -r '.rate_limits.five_hour.used_percentage // empty')
WEEK=$(echo "$input" | jq -r '.rate_limits.seven_day.used_percentage // empty')
LIMITS=""
[ -n "$FIVE_H" ] && LIMITS="5h: $(printf '%.0f' "$FIVE_H")%"
[ -n "$WEEK" ] && LIMITS="${LIMITS:+$LIMITS }7d: $(printf '%.0f' "$WEEK")%"
echo "${LIMITS:-limits not loaded yet}"

Make it executable with chmod +x ~/.claude/statusline.sh and point Claude Code at it in ~/.claude/settings.json:

~/.claude/settings.json
{
  "statusLine": {
    "type": "command",
    "command": "~/.claude/statusline.sh"
  }
}

What happens when you hit the limit

Claude Code warns you first, with a line such as You've used 85% of your session limit · resets 3:45pm. When the allowance runs out, it blocks new requests until the reset time in the message. Your options, from Anthropic's docs:

  • Wait, and let it continue on its own. In an interactive session signed in with a subscription, Claude Code v2.1.234 and later waits in the open session and picks the task up shortly after the reset. Keep the terminal open; press Esc to cancel. /rate-limit-options shows the choices.
  • Turn on usage credits. Run /usage-credits (it was called /extra-usage) on Pro, Max or Ultra. Work continues past the limit at standard API rates, billed separately from your plan, until your balance or monthly spend limit runs out. On Team and Enterprise it sends a request to your admin.
  • Switch model, for model limits only. After an Opus or Sonnet limit, /model to another family keeps you going. It won't help with the session or weekly limit.
  • Upgrade. Pro to Max, or Max to Ultra. Anthropic says upgrades take effect immediately.
  • Use an API key from the Claude Console and pay per token instead.
Terminal mock showing example Claude Code messages: You've used 85% of your session limit, You've hit your session limit, Usage limit reached, and Continuing automatically at 3:45pm, Esc to cancel
Example messages, worded as in Anthropic's Claude Code docs. Times are illustrative, not from a real session.

Anthropic is also rolling out a small "wrap-up" allowance: if you hit the five-hour limit mid-response, Claude Code may finish the current step and show Usage limit reached · wrapping up. On Pro that can happen up to once per weekly period; on Max, each time you reach a five-hour limit. It still counts towards your weekly limit.

ccusage: usage from your local logs

ccusage is a popular open-source, MIT-licensed command-line tool that reads the session logs Claude Code saves on your machine and turns them into reports. Nothing to install if you have Node:

Terminal
npx ccusage@latest            # daily report
npx ccusage@latest blocks     # usage grouped into 5-hour blocks
npx ccusage@latest blocks --active   # the current block, with burn rate and projection

The blocks report groups your usage into 5-hour blocks and, for the active one, shows a burn rate in tokens per minute and a projected total if you keep going at that pace. Add --token-limit max to measure the current block against your biggest past block:

Terminal
npx ccusage@latest blocks --active --token-limit max

Two caveats. ccusage estimates cost at API prices and only sees logs on this Mac, so usage on claude.ai or another computer is invisible to it. And its blocks are an approximation built from timestamps, not Anthropic's meter, so use it to understand how fast you're burning through a window, and /usage to know how much is actually left. Also note that Claude Code deletes local session data older than 30 days by default (the cleanupPeriodDays setting), which limits how far back any log-based tool can see. The old blocks --live monitor was removed in ccusage v18 in favour of its status line command.

Watch the 5-hour window from your notch

Running /usage or npx ccusage means stopping to ask. NotchDodo is a Mac app that turns the MacBook notch into a small dashboard, and its AI Usage page reads the same local logs so the numbers are just there. What it shows:

  • Your current 5-hour window: tokens used against a budget, burn rate per minute, and the reset time, with a bar that turns orange at 80% and red at 100%. Like ccusage, a window opens at the hour of your first message. The budget is set in Settings, or on auto it uses your biggest past window (at least 1M tokens).
  • Each agent session: project, branch, model, running or waiting, active time, messages, tokens and estimated cost.
  • Today and the last 7 days, in tokens and estimated cost at API list prices.
  • Warnings in the notch once per window at 80% and at the limit, and a live activity while an agent runs.
  • Codex and Gemini CLI sessions too. Gemini counts towards today and the chart but not the 5-hour window, since Google doesn't limit usage that way.
NotchDodo AI Usage panel under the MacBook notch showing the current window at 2.36M of 5.00M tokens with its reset time, three running or waiting agent sessions, and a 7-day token chart
NotchDodo's AI Usage panel: the current window, live sessions and the last 7 days. Demo data.

Same caveat as ccusage: it's an estimate from your Mac's logs, not Anthropic's meter, and nothing is uploaded. It pairs with approval alerts for Claude Code and with keeping your Mac awake while agents work, so a long task doesn't stall because the Mac went to sleep (for other jobs, see how to stop your Mac sleeping).

Which way of checking should you use?

/usageSettings → UsageccusageNotchDodo
Anthropic's real remaining allowanceYesYesNo, an estimateNo, an estimate
Weekly limit and resetYesYesNoNo
Includes claude.ai and other devicesPlan bars yes, breakdown noYesNoNo
Tokens and estimated cost per sessionCurrent sessionNoYesYes
Always visibleNoNoNoYes, in the notch
Codex and Gemini CLINoNoYesYes
CostBuilt inBuilt inFree, open source$9.99 one-time

For the number that decides whether you get blocked, use /usage or Settings → Usage. Use ccusage or NotchDodo to see where your tokens go and how fast a window is filling, so the limit doesn't surprise you.

How to make your usage last longer

These come from Anthropic's own guide to managing Claude Code costs, and they work the same way on a subscription:

  • Clear between tasks. /clear starts fresh and costs nothing. Stale context is re-sent with every message.
  • Compact with intent. /compact Focus on code changes keeps what matters, but compacting a huge context is itself a large request, so don't compact when a clean start would do.
  • Match the model to the job. Anthropic suggests Sonnet for most coding and Opus for complex reasoning. Switch with /model.
  • Lower the effort with /effort for simple tasks; thinking tokens count as output.
  • Trim fixed context. Keep CLAUDE.md short, move specialised instructions into skills, and disable MCP servers you aren't using. /context shows what's taking space.
  • Be specific. "Add input validation to the login function in auth.ts" reads far fewer files than "improve this codebase".
  • Watch background work. Loops, scheduled tasks, subagents and agent teams all use your allowance, even while you're idle. The /usage breakdown shows their share.
Never get surprised by the 5-hour limit.NotchDodo keeps your Claude Code window, burn rate and reset time in the MacBook notch, warns you at 80%, and tracks Codex and Gemini CLI too. Plus calendar, clipboard, Pomodoro and more. One-time purchase, no subscription.Get NotchDodo for $9.99See pricing

Sources

Claude and Claude Code are trademarks of Anthropic. ccusage belongs to its developers. Mac and MacBook are trademarks of Apple Inc. NotchDodo is an independent app and is not affiliated with Anthropic or Apple.

Frequently asked questions

What is the Claude Code 5-hour limit?

On Pro and Max, Claude Code shares a session limit with Claude on the web and desktop. The five-hour period starts with your first message and resets five hours later. When you use it up, Claude Code shows "You've hit your session limit" with the reset time and stops sending requests until then, unless you turn on usage credits. Verified Ultra accounts have no five-hour limit, only a weekly one.

When does the Claude Code weekly limit reset?

At a fixed time each week that Anthropic assigns to your account. It doesn't move based on when you start working. You can see your next weekly reset under Settings > Usage on claude.ai, or with /usage inside Claude Code.

How do I check my Claude Code usage?

Type /usage at the Claude Code prompt. On a Pro, Max, Ultra, Team or Enterprise plan it shows your plan usage bars, reset times and a breakdown of what is using your allowance. /cost and /stats open the same screen. On the web, open claude.ai, then Settings > Usage, to see the current session, time remaining and your next weekly reset.

How many messages do I get with Claude Code on Pro or Max?

Anthropic doesn't publish a fixed message count. Usage depends on how long and complex your conversations are, the model, the effort level, the tools you use and how much context Claude reads. Anthropic describes plans relative to each other instead: Max gives five times Pro's usage every five hours and every week, and Ultra gives ten times Pro's usage every week.

Is Claude Code usage shared with claude.ai?

Yes. Anthropic says usage across claude.ai, Claude Code and Claude Desktop counts towards the same usage limit. A long chat on the web leaves less for your terminal, and the other way round.

What happens when I hit the Claude Code usage limit?

Claude Code blocks new requests until the reset time in the message. In an interactive session signed in with a subscription, recent versions can wait and continue the task automatically after the reset. You can also turn on usage credits with /usage-credits to keep working at API rates, upgrade your plan, or, for an Opus or Sonnet limit only, switch to another model family with /model.

Does switching models get around the limit?

Not for the session or weekly limit: those are shared across all models. It does help with the model-specific messages, "You've hit your Opus limit" or "You've hit your Sonnet limit", where switching to a model outside that family with /model keeps you working.

Is ccusage accurate?

ccusage reads the Claude Code logs on your Mac and prices tokens at API rates, so it's a good guide to how hard you're working, but it isn't Anthropic's meter. It can't see usage from claude.ai or other devices, and its 5-hour blocks are its own approximation. For your real remaining allowance, trust /usage or Settings > Usage.