Claude routines draw down the weekly usage limit

Claude Code's routines docs say they draw down subscription usage the same way interactive sessions do. A saved prompt on a schedule, an API POST, or a GitHub pull request still counts as you.

The 50 percent weekly bump ending 31 August 2026 makes that debit louder, not cheaper.

A closed laptop is still a session#

A routine is a saved Claude Code configuration. Prompt, repositories, connectors, packaged once and run automatically. It executes on Anthropic-managed cloud, or a self-hosted environment when routed there, so it keeps working when the laptop is closed.

Pro, Max, Team, and Enterprise plans with Claude Code on the web can create them at claude.ai/code/routines or from the CLI with /schedule. They run as full cloud sessions. No permission-mode picker, and no approval prompts during a run.

That last bit inverts auto-mode default approval fatigue. Interactive sessions train you to click through. A routine never asks.

Same tools. Same GitHub identity. Same weekly bar.

Zero steering while it burns.

You'll hit this if you wire a pull-request opened trigger on a busy repo and then sit down Monday to write. The night already spent the week.

Green in the run list means the session started and exited without an infrastructure error. It does not mean the prompt succeeded.

Open the transcript before you trust the checkmark.

The triggers are three facts, not a buffet of extra quota.

• A schedule, hourly to weekly, or a one-off timestamp
• An API POST to a per-routine endpoint with a bearer token
• A GitHub pull request or release event

A single routine can combine them. Nightly plus every new PR is still one account, still one week.

The daily start cap is a second ceiling#

Docs add a daily cap on how many runs can start per account. Remaining daily routine runs live at claude.ai/code/routines or claude.ai/settings/usage. That counter is not a second gift quota.

Launch-week recaps still print Pro 5, Max 15, Team 25. Anthropic's April launch post had those counts. They are not on the fetched docs page.

Two ceilings, one pool. The start counter limits how often a session can begin. The weekly bar limits how much those sessions can think.

Hitting the start cap rejects new runs until the window resets, unless usage credits are on. One-off runs skip the daily routine cap. They still draw down regular subscription usage like any other session.

The "free" one-off is free of the start counter. The week still moves.

GitHub webhooks during research preview have per-routine and per-account hourly caps. Events beyond the limit are dropped until the window resets. A noisy trigger does not queue.

It vanishes.

The minimum schedule interval is one hour. Cloud polling every five minutes is rejected. /loop on the machine still can, and it still spends.

Overage is a bill, Code Review is a different SKU#

The generous reading is that overage saves you. Usage credits for paid Claude plans keep a routine running past the bar at standard API rates, with a $2000 daily redemption cap.

The night shift continues. The invoice grows.

That is a real door. It is also a metered door. They are not bundled into Max 5x at $100 or Max 20x at $200.

They are the Console price list wearing your login.

Claude Code GitHub Actions can authenticate with an API key and bill the Console instead of the seat. Same repo, same PR comments, different wallet.

Official Code Review on Team and Enterprise is billed separately through usage credits and does not count against included usage. Each review averages 15 to 25 dollars, scaling with PR size.

That is actual extra capacity. It is also not this product. It is not on Pro or Max.

Then the cut.

GitHub Actions with a subscription OAuth token still uses the Claude subscription. The Actions docs say so in one line. Wire the seat token into CI and the weekly bar still moves while you sleep.

Desktop scheduled tasks and /loop are not a loophole. They need the machine on, or the session open. They still start Claude Code sessions against the same plan.

Laptop-closed was the whole point of a routine. That is also why it costs.

Think of one tank with two hoses. One hose is the CLI you watch. The other is the cloud job you forget about until Monday.

The gauge does not care which hose was open.

Spend the week on a routine only when you would have spent that session anyway. Extra capacity exists. A cloud routine on a Pro or Max login is none of these.

• Usage credits at API rates after the included bar
• GitHub Actions with an API key, billed to Console
• Official Code Review on Team and Enterprise, billed separately

The extra 50 percent makes the debit worse#

Anthropic's Help Center still calls the extra week a limited-time promotion. Through 31 August 2026 at 11:59 PM PT, weekly Claude Code limits are 50 percent higher. After that, they return to standard, with no change to plan or billing.

Max 5x is $100 a month. Max 20x is $200. The bump is not in those prices.

The 50 percent weekly bump is the product already argued that coupon. This post is the night-shift tax on it.

A routine that felt cheap on the boosted bar is the same session on a shorter week. People on r/ClaudeAI were already asking how fast sessions will eat the week after 31 August. Budget the standard bar, then decide which triggers earn a start.

Phone remote control is a different product. Running Claude Code from your phone still has you in the loop. A routine does not.

What would change the bet is a docs rewrite that puts routines on a separate quota, or a catalog line that actually includes the extra. Until then, treat unattended PR review as you, on the clock, with the lid shut.