Live data from Hacker News

Claude Code weekly rate limits

news.ycombinator.com

231–240 of 724 posts

Re: Claude Code weekly rate limits

#231

From Anthropic’s Reddit account: One user consumed tens of thousands in model usage on a $200 plan. Though we're developing solutions for these advanced use cases, our new rate limits will ensure a more equitable experience for all users while also preventing policy violations like account sharing and reselling access. This is why we can’t have nice things.

I worked at a startup that offered an unlimited option.

It's amazing how fast you go from thinking nobody could ever use that much of your service to discovering how many of your users are creatively abusing the service.

Accounts will start using your service 24/7 with their request rating coming at 95% of your rate limiter setting. They're accessing it from a diverse set of IPs. Depending on the type of service and privacy guarantees you might not be able to see exactly what they're doing, but it's clearly not the human usage pattern you intended.

At first you think you can absorb the outliers. Then they start multiplying. You suspect batches of accounts are actually other companies load-splitting their workload across several accounts to stay under your rate limits.

Then someone shows a chart of average profit or loss per user, and there's a giant island of these users deep into the loss end of the spectrum consuming dollar amounts approaching the theoretical maximum. So the policy changes. You lose those 'customers' while 90+% of your normal users are unaffected. The rest of the people might experience better performance, lower latencies, or other benefits because the service isn't being bombarded by requests all day long.

Basically every startup with high usage limits goes through this.

Re: Claude Code weekly rate limits

#232
The 5% being ‘abusive’ limit seems high (1/20 users — that feels like an arbitrary cost cut based on customer numbers rather than objective based on costs/profit). I would have much preferred to see a scalpel applied to the abusive accounts than this — and from what I’ve seen those users should be very obvious (I’ve seen posts on Reddit with people running dozens of CC instances 24/7).

I also have to wonder how much Sub Agents and MCP are adding to the use, sub agents are brand new and won’t even be in that 95% statistic.

At the end of this email there a lot of unknowns for me (am I in the 5%, will I get cut off, am I about to see my usage increase now that I added a few sub agents?). That’s not a good place to be as a customer.

Re: Claude Code weekly rate limits

#233

From Anthropic’s Reddit account: One user consumed tens of thousands in model usage on a $200 plan. Though we're developing solutions for these advanced use cases, our new rate limits will ensure a more equitable experience for all users while also preventing policy violations like account sharing and reselling access. This is why we can’t have nice things.

guy was bragging about it on twitter yesterday. $13,200 of spend for his $200 account. he said he had like 4-5 opus only agents running nonstop and calling each other recursively. clearly that's abusive and should be targeted. but in general idk how else any inference provider can handle this situation. cursor is fucked because they are a whole layer of premium above the at-cost of anthropic / openai etc. so everyone…

> guy was bragging about it on twitter yesterday. $13,200 of spend for his $200 account. he said he had like 4-5 opus only agents running nonstop and calling each other recursively.

Do you have a link?

I'm always curious to see these users after working at a startup that was the target of some creative use from some outlier customers.

Re: Claude Code weekly rate limits

#234

Confused on the Max 5x vs Max 20x. I'm on the latter, and in my email it says: > "Most Max 20x users can expect 240-480 hours of Sonnet 4 and 24-40 hours of Opus 4 within their weekly rate limits." In this post it says: > "Most Max 5x users can expect 140-280 hours of Sonnet 4 and 15-35 hours of Opus 4 within their weekly rate limits." How is the "Max 20x" only an additional 5-9 hours of Opus 4, and not 4x that of "M…

You're paying for prioritization during high traffic periods, not for 2x usage.

Re: Claude Code weekly rate limits

#236
post #226

I'm probably not going to hit the weekly limit, but it makes me nervous that the limit is weekly as opposed to every 36 hours or something. If I do hit the limit, that's it for the entire week —a long time to be without a tool I've grown accustomed to! I feel like someone is going to reply that I'm too reliant on Claude or something. Maybe that's true, but I'd feel the same about the prospect of loosing ripgrep for a…

if it affects only a minority of accounts, why not figure out how to special case them without affecting everyone else is the primary question I would ask myself if I worked on this the principle: let's protect against outliers without rocking the behavior of the majority, not at this stage of PMF and market discovery i'd also project out just how much the compute would cost for the outlier cohort - are we talking $5…

What do you think they should have done instead?

Re: Claude Code weekly rate limits

#237
post #84
post #67

Earlier quoted context omitted.

I'm ok using a limited resource _if_ I know how much of it I am using. The lack of visible progress towards limits is annoying.

It's not exactly the same thing, but imagine my complete surprise when, in the middle of a discussion with Copilot and without warning, it announced that the conversation had reached its length limit and I had to start a new one with absolutely no context from the current one. Copilot has many, many usability quirks, but that was the first that actually made me mad.

ChatGPT and Claude do the same. And I have noticed that model performance can often degrade a lot before such a hard limit. So even when not hitting the hard limit, splitting out to a new session can be useful. Context management is the new prompt engineering...

Re: Claude Code weekly rate limits

#238

Earlier quoted context omitted.

"they paid for" $100 doesn't even cover the electricity of running the servers every night, they were abusing a service and now everyone suffers because of them.

It is still not the users fault, pricing is not their responsibility. As a user, I check the price and what the service offers, then I subscribe and I use it. If these users did something illegal or breaking some conditions, any service would be free to block them. But they didn’t, meaning the AI tools promised too much for the price so they update their conditions, they are basically figuring out the pricing. I don’…

a lot of "all you can eat" restaurants have to charge extra for uneaten food. there are people who just enjoy the feeling of abundance they get from paying a flat fee and then wasting something.

This is clearly what was happening with the most extreme Claude Code users, because it's not actually that smart yet and still requires a human to often be in the loop.

However, Anthropic can't really identify "wasted code".

Re: Claude Code weekly rate limits

#239
post #181

Earlier quoted context omitted.

I imagine they will add some features soon where you have more control. It could get complicated quickly. Before they put this in I think they should have at least given you an easy way to buy more credits at a hugely discounted rate. I know entire offices in Bangladesh share some of these accounts, so I can see how it is a problem.

That is exactly the use case they're trying to stop. Sharing accounts.

Which is why I said I see how it could be a problem :)

Re: Claude Code weekly rate limits

#240
post #226

I'm probably not going to hit the weekly limit, but it makes me nervous that the limit is weekly as opposed to every 36 hours or something. If I do hit the limit, that's it for the entire week —a long time to be without a tool I've grown accustomed to! I feel like someone is going to reply that I'm too reliant on Claude or something. Maybe that's true, but I'd feel the same about the prospect of loosing ripgrep for a…

if it affects only a minority of accounts, why not figure out how to special case them without affecting everyone else is the primary question I would ask myself if I worked on this the principle: let's protect against outliers without rocking the behavior of the majority, not at this stage of PMF and market discovery i'd also project out just how much the compute would cost for the outlier cohort - are we talking $5…

They did have several outages last week, it would be good to find better plans for those huge users but I can also see them wanting to just stop the bleeding.
Post reply on HN