Most Claude Code users learn about the 5-hour limit on day one. They learn about the weekly cap on day four — usually a Thursday morning, when a fresh 5-hour window refuses to open and the editor explains why with a thousand-second countdown. The 7-day rolling cap is the quieter limit that decides whether the week stays usable. Here is how it works, how it interacts with the short throttle, and what pooling does to the math.
The 7-day rolling window — Anthropic's quieter limit
Anthropic publishes two rolling rate-limit windows for Claude Code subscriptions: the loud, immediate 5-hour window, and a quieter, slower 7-day window. The two are tracked independently on the server. A request that fits inside the 5-hour budget can still be rejected if it would push you over the 7-day cap. The reverse is also true — you can have weekly headroom and still be blocked by a hot 5-hour window.
The 7-day window is rolling for the same reason the 5-hour window is. The clock is tied to your activity, not to a calendar week. Sunday at midnight is not a reset. The "week" measured by the cap is the trailing 168 hours of your account's request history. As the oldest hour of usage ages out, capacity returns.
The weekly cap exists to keep heavy outlier days from consuming a month of subscription value in a long weekend. It is generous enough that a normal coding day does not touch it. It is also strict enough that two unusual days in a row can lock the rest of the week.
Anthropic's published rate-limit page is the authoritative source for the current numerical ceiling on each plan. Numbers do change. The window shape — rolling 168 hours, per account — has been stable.
How the 5-hour and 7-day windows interact
Two budgets in series:
- The 5-hour window is the throttle. It is what you feel during a session. It limits burst usage.
- The 7-day window is the ceiling. It is what you feel between sessions. It limits aggregate usage.
The 5-hour window resets fast — within hours of stopping. The 7-day window resets slowly — your Monday spend is still on the books until next Monday. That asymmetry is what creates the felt experience of "I can use Claude Code on Monday and Tuesday but not Wednesday through Sunday."
Under normal coding load, the 5-hour window is the only one that ever bites. A senior developer hits it once or twice a day, waits for the rolling window to recover, and moves on. The 7-day window sits in the background, never crossed, never thought about.
Under heavy load — autonomous fix loops, large sub-agent fan-outs, multi-day refactors — the 7-day window becomes the operative limit. Once you have spent eighty percent of your 7-day budget by Wednesday, the 5-hour window stops being interesting. The remaining 5-hour budgets can be perfect and the cap will still close every session prematurely because the weekly ceiling is the binding constraint.
The worst-case schedule
A realistic two-day spike:
| Day | Pattern | 5-hour windows used | 7-day cap consumed |
|---|---|---|---|
| Monday | Heavy refactor + autonomous lint loop | 3 | 45% |
| Tuesday | Continued refactor + sub-agent fan-out | 3 | 35% |
| Wednesday | Quick review prompts | 1 | 8% |
| Thursday | Attempt morning session | Blocked | 88%+ |
The Reddit thread that captured this pattern most viscerally was titled with the verbatim complaint we still see weekly:
unusable for 5–6 days per week
That is not the 5-hour window producing that experience. The 5-hour window is fast enough to recover that no single day's usage triggers a week of lockout. It is the 7-day cap, slow to refill, fast to drain on two heavy days, that produces the multi-day dead zone.
What pooling does to weekly caps
Each Claude.ai account has its own 7-day window. The cap does not federate across accounts on the same billing card, the same machine, or the same household. Two accounts = two 7-day buckets. Four accounts = four 7-day buckets. Pooling at the account level multiplies the user's effective weekly ceiling without raising any single account's published cap.
This is a structural change, not a hack. Anthropic is not being asked to grant you more headroom on one account. The terms of service permit one individual to hold multiple Claude.ai accounts. Each account is billed independently. Each account is rate-limited independently. A pooled router simply chooses which account's bucket to draw from on each request, and prefers the bucket with the most remaining 7-day budget. Balanced Mode makes that bucket choice for you on every request. You can install Power Claude free with no credit card and and the 7-day free trial includes full Pro access, or start the 14-day Premium Trial for $0 today and cancel anytime before day 15 to add Balanced Mode on top.
Two important properties of pooled weekly caps:
- The math is per account, not per pool. Pooling four accounts does not give you "4× the headroom of one account" on every dimension. The 5-hour windows are independent, so a pooled day can run four parallel 5-hour windows simultaneously. The 7-day windows are also independent, but they all started at the same time when you set up the pool, so they all expire in lockstep. The structural improvement comes from the multiplication of windows, not from staggering them.
- Smart routing matters more than the count. Pooling two accounts naively will tank the first one fast and idle the second. A router that distributes load across the pool evenly — by projected remaining budget per account — keeps all of them recovering at similar rates and pushes the felt ceiling out the most.
Plan-tier interactions (Pro vs Max)
Anthropic offers Claude Code subscriptions at two main tiers. The differences relevant to the weekly cap are qualitative:
- Pro is designed for a single user's daily coding workflow. The 7-day window is sized for a typical engineering week and rarely binds on light-to-moderate use. Heavy autonomous workloads can saturate it.
- Max raises both the 5-hour and 7-day ceilings substantially. The architecture is identical — rolling windows, per-account, no calendar alignment — just with more headroom per account. A Max account holder still hits the weekly cap under sustained heavy autonomous load; it just takes more days to get there.
For current numerical ceilings, Anthropic's published plan documentation is the authoritative source. The numbers move from time to time. The structural relationships — Pro < Max, both have 5-hour and 7-day windows, both are per-account — have been stable.
A pool of Pro accounts and a pool of Max accounts behave the same way structurally. The Max pool just costs more and produces more headroom per account. Mixed-tier pools work; a router can prefer Max accounts when they are healthy and fall back to Pro accounts when Max is hot.
Frequently asked questions
Is the weekly cap a calendar week or a rolling 7 days?
Rolling. The 168 hours are measured from each individual request backward. Sunday at midnight does not reset anything. As the oldest requests in your history age past 168 hours, their token weight rolls off your weekly budget and capacity returns.
If I only use Claude Code on weekdays, does the weekend "rest" reset the weekly cap?
The weekend rest is recovery time, and yes, it helps. By Monday morning roughly two days' worth of older usage has rolled off the 7-day window. If your heavy days were the prior Monday and Tuesday, those have now fully decayed and you start the new week with a clean cap. If your heavy days were the prior Thursday and Friday, only the Thursday spend has fully rolled off — the Friday spend is still on the books until this Friday.
Does Max plan have a weekly cap or only the 5-hour one?
Both. The 7-day window applies to all Claude.ai subscription tiers. Max raises the ceiling but does not eliminate the limit. Anthropic's documentation publishes current numbers per tier.
Can pooling multiple accounts violate Anthropic's TOS?
Anthropic's published terms permit each individual to hold multiple Claude.ai accounts so long as each account is owned and controlled by that person and is not being shared or resold. Pooling accounts you personally hold is consistent with those terms. Pooling accounts that belong to other users is not. Check the current TOS rather than relying on yesterday's reading.
If one of my accounts hits the weekly cap, do other pooled accounts keep working normally?
Yes. The 7-day window is per account. A capped account just means the router will not route traffic to that account until its window decays. The other accounts in the pool are unaffected by their sibling's state — they keep their own buckets and continue serving requests.
What developers are reporting
The weekly-limit megathread on GitHub (anthropics/claude-code #9424) collects report after report of Pro and Max users exhausting the 7-day cap in a day or two — "making paid subscriptions effectively unusable for 5-6 days per week." Pooling the accounts you already own is the most direct answer to that specific failure mode.
Closing
The weekly cap is what determines whether Claude Code stays usable across a full work week or only for the first two or three days of it. A single account cannot keep up with the kind of autonomous, sub-agent-heavy workloads senior developers actually run. Account pooling turns one 7-day bucket into N, and the cap stops being the limit of the work week.
If you want to put a full week of heavy usage behind a pool of your own accounts, the 14-day Premium Trial is $0 today and you can cancel anytime before day 15 — it adds Balanced Mode, the watchdog, and usage analytics on top of pooled rotation. Not ready to add a card? Install Power Claude Free instead: the 7-day free trial gives you full Pro access, no credit card.