Live data from Hacker News

Claude Code weekly rate limits

news.ycombinator.com

221–230 of 724 posts

Re: Claude Code weekly rate limits

#221
> affecting less than 5% of users

Probably phrased to sound like little but as someone used to seeing like 99% (or, conversely, 1% down) as a bad uptime affecting lots and lots of users, this feels massive. If you have half a million users (I have no idea, just a ballpark guess), then you're saying this will affect just shy of the 25 thousand people that use your product the most. Oof!

Re: Claude Code weekly rate limits

#224
post #36

Earlier quoted context omitted.

Unlimited works well for everything that is “too cheap to meter”. Internet, text messages, etc are roughly that: the direct costs are so cheap. That’s not the case with LLM’s at this moment. There are significant direct costs to each long-running agent.

Internet and SMS used to be expensive and metered until they weren't thanks to technological advances and expanded use. I think LLMs will follow the same path, maybe on a shorter timespan.

SMS was designed from the start to fit in the handul of unused bytes in the tower handshake that was happening anyway, hence the 160 char limit. Its marginal cost has always been free on the supply side.

Re: Claude Code weekly rate limits

#225

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…

This is why I stopped using the MAX. Downgraded to Pro and started using o3 and others via API. I really don’t need that many hours to game plan in the beginning. At most it will cost me $10 between o3, Gemini, and Opus per project. There are new model releases every couple of weeks and I’d hate to get stuck with just one provider.

Re: Claude Code weekly rate limits

#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 $5M, $100M, $1B per year? And then what behaviors will simply be missed by putting these caps in now - is it worth missing out on success stories coming from elite and creative users?

I'm sure this debate was held internally but still...

Re: Claude Code weekly rate limits

#227
post #201
post #54

Earlier quoted context omitted.

> Starting August 28 Read the announcement. You are getting a full month's notice. If you don't like the limits, don't renew your subscription. Of course that doesn't help if your primary goal is to be an online outrage culture warrior.

True. If it were easy to pirate these warriors would be claiming policy change as reason to pirate.

[deleted]

Re: Claude Code weekly rate limits

#228
post #208

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…

> Anthropic is saying that one out of every 20 users will hit the new limit. Very good point, I find it unlikely that 1/20 users is account sharing or running 24/7 agentic workflows.

Moreover, if you run a SaaS, generally somewhere from 1 in 5 to 1 in 20 users are using you for real, while the others are mostly not using you.

The stat would be more interesting if instead of 1 in 20 users, they said x in y of users with at least one commit per business day, or with at least one coding question per day, or whatever.

I suspect this could be a significantly higher percentage of professional users they plan to throttle. Be careful of defining Pro like Apple does if you market to actual professionals who earn based on using your product. Your DAUs might be a different ratio than you expect.

Re: Claude Code weekly rate limits

#229
> affecting less than 5% of users based on current usage patterns.

How about adding ToS clause to prevent abuse? wouldn't that be better than having a statement with negative effect on the rest of 95%?

Re: Claude Code weekly rate limits

#230
post #221

> affecting less than 5% of users Probably phrased to sound like little but as someone used to seeing like 99% (or, conversely, 1% down) as a bad uptime affecting lots and lots of users, this feels massive. If you have half a million users (I have no idea, just a ballpark guess), then you're saying this will affect just shy of the 25 thousand people that use your product the most . Oof!

Reminds me of gym membership utilization rates. You have something like 50% not even going. A large % left only go a few times a month…. Yada yada
Post reply on HN