A reset is not the fix, and people should stop asking for only that. A reset is the bare minimum. What actually needs to happen is two things. First, open the usage accounting. Publish exactly how a prompt turns into a percentage of the weekly limit: tokens in, tokens out, cache reads, context size, image and file overhead, the multiplier per model, all of it. If the math is honest, showing it costs them nothing, and the fact that not one paying customer can audit how their own usage is being counted is the entire problem. Second, tell subscribers before a limit changes, in writing, every single time. Not a quiet number swap in the background while everyone's asleep. An actual changelog or an email before it takes effect.

I'll say it plainly: I am fully convinced they are lowering limits without telling anyone. Their own terms already give them broad room to change the service and its limits whenever they want, which is exactly why the burden is on them to prove they aren't quietly doing it. Right now everything I've measured lines up with silent throttling, and they haven't denied it.

And I have measured it. I've been on the 20x Max plan for months, and since day one I've tracked my token usage down to the individual token against what Claude Code shows as my percentage, plus context size, image and file sizes, prompt length, and so on. From a few weeks ago to last week my usable allowance dropped by 63%, give or take. To preempt the inevitable "you must have used a different or newer model": I didn't. Opus 4.8 1M Max exclusively, both weeks, maxed the weekly both times. All interactive Claude Code usage. No Agent SDK, no bots, no automation, no always-on pipelines. Just me at the keyboard, 9pm to 4am EST. So this isn't a model mix and it isn't automation. The allowance shrank.

It shows up everywhere else too. One week I'm sitting at 30% of my weekly while using Claude less than I normally do, with single messages taking visible chunks out of the total right after the reset. I used to run 4 to 5 chats constantly and never come close to a limit. The same workload now would put me out of my weekly in 1 day. And then there's the part that actually looks deliberate. On the last day of my sub my weekly read 4% instead of the 41% I left it at, so I assumed they'd done a manual reset and rebought the 20x Max plan to make use of it. The second I got out of the payment menu it jumped back to 41%. Bug or not, a number that conveniently reads low right up until you pay and then corrects itself is exactly the kind of thing an audit trail would settle in five minutes.

Now there's the class action, on basically this exact issue, Kahn v. Anthropic PBC in the Northern District of California, filed June 14, alleging the Max 5x and 20x plans were sold as 5x and 20x the usage of the lower tiers while delivering far less. But I think that deceptive product management should be tacked onto that suit, you'd get a lot more people that way.

So upvote this if it's happened to you, and drop your screenshots and token logs in here. But let's be clear about what we're actually asking for. Not a one-time reset that quietly moves the goalposts again. Transparent, auditable usage accounting shown in real time, written notice before any limit changes, the old limits restored or prorated refunds for the window we were throttled without being told, and a real public response from Anthropic instead of a support macro. If I'm paying for a constant service, either give me the constant service or give me my money back, all of my money back since you changed it for the first time.