If you pay for Claude Pro, Max, Team, or a seat-based Enterprise plan, your weekly Claude Code allowance changed on Monday, September 14.
Anthropic's announcement says it is permanently raising standard weekly limits by 25%. That is true against the standard limit. It is not what you had last week. Since May, Claude Code had been running on a temporary 50% boost, and that boost ended September 13. After Anthropic deleted its first post and reposted, the company put the other number in writing: compared with before, this works out to a 17% reduction.
The arithmetic: if the old standard allowance was 100, you had 150 all summer. Monday it became 125. More than the spring, less than the summer. Both press-release numbers are correct. Only one of them describes your week.
Why a usage cap is worth writing about
I run most of my work on a Claude subscription. Code, deploys, research, the agents that handle my bookkeeping. When the ceiling moves 17%, that is a budget change, and I would rather plan for it than hit the wall on a Thursday.
What actually eats the allowance
Anthropic's own usage guide lists the levers: message length, attachment size, how long the conversation has run, tool calls such as web search and research, which model you picked, and the effort level. Content stored in a Project is cached and does not count when it is reused. Weekly limits reset separately for Opus only and for all other models, so a heavy Opus week does not have to drain the rest.
What to change, in order of payoff
Check the effort setting first.
Claude Code defaults Fable 5.1 to High effort. Most edits, scripts and reviews do not need it. Medium for routine work, High for the hard problems. This is the single largest lever and the one most people never touch.
Stop paying for re-reads.
A long session that keeps the whole repo in context bills for that context on every turn. Start a fresh session for a fresh task instead of continuing the one from this morning.
Batch the small stuff.
Five one-line questions in five turns cost more than five questions in one turn. Anthropic says this outright in its guide, and it is more true in Claude Code than in chat.
Put standing context in a Project or a CLAUDE.md, not in the prompt.
Cached project content is free on reuse. Pasting the same brief every session is not.
Look at Settings then Usage on a Wednesday, not a Sunday.
The five-hour and weekly bars are both there. If you are at 70% midweek, that is the day to move routine work to a cheaper model, not the day you find out you already hit the wall.
One more reason to watch that usage bar
In late August, Anthropic told some users that common infostealer malware on their own machines had copied active Claude login sessions, and that attackers were spending the victims' allowance. Anthropic is signing affected users out, removing saved payment methods and refunding unauthorized charges, and its notice is explicit that the malware did not come through Claude. A stolen session skips your password and your two-factor prompt, because the browser is already logged in. If your limit ever looks like it refilled and then drained while you were away from the keyboard, that is not a bug in the meter.
Who this is for
Anyone whose AI spend is a subscription rather than an API bill. Read the second number, not the first.
---I write Wired on AI, a weekly newsletter where I take one AI tool, use it on real work, and report what it did, where it broke, and whether it was worth the time. This piece is the tool section from issue 25. Weekly since March 28, no missed weeks.
Top comments (0)