Claude session limit vs weekly limit: the difference
The session limit resets five hours after you start; the weekly limit resets at a fixed time for your account. They count at once, so you can hit either first.
The session limit is a short window that resets five hours after your first message. The weekly limit is a longer allowance that resets once a week at a fixed time assigned to your account. Both count your usage at the same time, so you can run out of either one first. Anthropic puts it this way: "Paid plans have two types of usage limits: a session limit that resets every five hours, and weekly limits that reset once every week" (Help Center).
The two windows side by side
| Session limit | Weekly limit | |
|---|---|---|
| Length | Five hours | One week |
| When it starts | When you send your first message of the period | Fixed day and time assigned to your account |
| Reset | In full, five hours after the period started | At the same assigned day and time each week |
| Depends on billing date | No | No |
| Applies to | Pro, Max, Team; Ultra only until verified | Every paid plan except usage-based Enterprise |
| Where Claude Code calls it | five_hour in status line data |
seven_day in status line data |
Sources: the Help Center article above, the Ultra plan article and the status line docs, as of November 2026.
The weekly reset is not seven days after first use: "Your reset day and time stay the same regardless of when you start using Claude or when your subscription begins" (Help Center). Both resets are covered in detail in when the 5-hour limit resets and when the weekly limit resets.
They count at the same time
Your usage does not go into one bucket and then the other. Every request counts against the session allowance and the weekly allowance together. Anthropic's Claude Code documentation says: "A single burst of heavy activity, such as a large workflow fanout, can exhaust the weekly allowance before the session window resets" (Claude Code docs).
That gives you two different ways to be blocked:
- Session first. You burn through the session in a long afternoon, wait for the five-hour window to end, and carry on. The weekly allowance has been going down the whole time.
- Weekly first. A very large burst (many parallel subagents, a long automated run) uses so much of the week that the weekly limit is hit while the session still has room, or right after a fresh session starts. Waiting five hours does not help here, because the week only comes back at your weekly reset (or with a weekly limit reset from Anthropic, if you have one).
One user has reported a Team seat's weekly usage reaching 100% about 30.5 hours after its reset (GitHub issue 107390). That is a single user report, not an official figure.
Anthropic does not publish how many messages or tokens either limit holds, so you cannot work out in advance which one you will hit. The only reliable guide is the usage bars. See where to see your Claude limits.
What the messages say
Claude Code names the limit you hit. Anthropic's documented examples:
You've hit your session limit · resets 3:45pm
You've hit your weekly limit · resets Mon 12:00am
In both cases "Claude Code blocks further requests until the reset time shown in the message" (Claude Code docs). Switching models does not get you around either: "The session and weekly limits are shared across all models, so switching models doesn't restore access" (same page).
If you hit the session limit, see what to do when you hit the session limit in Claude Code. If it is the weekly one, see your options when you hit the weekly limit.
Which plans have which
As of November 2026:
- Pro, Max and Team: both a five-hour session limit and a weekly limit.
- Ultra: a weekly limit. Verified Ultra accounts have no five-hour limit; unverified ones have a temporary limit until verified (Help Center). See Ultra verified accounts.
- Seat-based Enterprise: a weekly limit. Usage-based Enterprise has no plan or seat limits (Enterprise plan article).
Anthropic describes the size of the plans as multipliers, not message counts. Max gives "5x Pro usage every 5 hours and every week", and Ultra gives "10x Pro usage every week" (claude.com/pricing). Team Standard seats include "1.25x the Pro plan's per-session usage allowance" and Premium seats 6.25x (Team plan article). What "1x" means in tokens is not published.
A third limit on some plans
Weekly limits apply "across all models, and some plans also have a separate weekly limit for Fable" (Help Center). On Max, Ultra and Team Premium seats you can use up to 50% of your weekly limit on Fable models, drawn from the same weekly allowance (Fable article). It is a share of the weekly limit, not extra room. The details are in how the Fable weekly limit works.
What a heavy user should do differently
- Watch the weekly bar, not only the session bar. A session that resets every five hours can make you feel safe while the week drains underneath.
- Be wary of very wide parallel work. Anthropic's own example of a weekly-first burst is a large workflow fanout.
- If you are on a plan with a session limit, Anthropic suggests you "plan intensive work sessions around your five-hour usage windows" (Help Center).
Seeing both at a glance
Headroom is a free Mac menu bar app that shows both numbers for every Claude Code account signed in on your Mac. Each account row has small meters for Session % and Week %, plus a per-model weekly meter when the account has one. Every number is how much you have used, never how much is left, and bars turn red at 90%.
The menu bar number is the average session use across tracked accounts, and accounts with no five-hour limit are left out of that average. Headroom does not send prompts, so checking does not use any of your limits. It reads the same usage figures Claude Code shows, which Anthropic does not publish as an official interface, so a change on Anthropic's side can break it until it is updated. It is an independent app, not made or endorsed by Anthropic.