Live data from Hacker News

Claude Code weekly rate limits

news.ycombinator.com

271–280 of 724 posts

Re: Claude Code weekly rate limits

#271
post #46
post #44

Earlier quoted context omitted.

If 95% of users are under the limit then it isn't a "fake" plan.

fake for 5% of users. will they refund me my sub? when I subbed It was unlimited, they've rugged the terms twice already since then in less than a month

> when I subbed It was unlimited,

Where did you see unlimited usage? The Max plan was always advertised as higher limits, not unlimited usage.

Re: Claude Code weekly rate limits

#273
post #68

Earlier quoted context omitted.

The long term is unlimited access to local LLMs that are better than 2025’s best cloud models and good enough for 99% of your needs, and limited access to cloud models for when you need to bring more intelligence to bear on a problem. LLMs will become more efficient, GPUs, memory and storage will continue to become cheaper and more commonplace. We’re just in the awkward early days where things are still being figured…

I'm often using LLMs for stuff that requires recent data. No way I'm running a web crawler in addition to my local LLM. For coding it could theoretically work as you don't always need latest and greatest but would still make me anxious.

That’s a perfect use case with MCP though.

My biggest issue is local models I can run on my m1/m4 mbp are not smart enough to use tools consistently, and the context windows are too small for iterative uses.

The last year has seen a lot of improvement in small models though (gemma 3n is fantastic), so hopefully it’s only a matter of time.

Re: Claude Code weekly rate limits

#275

I'm not sure how this will play out long term, but I really am not a fan of having to feel like I'm using a limited resource whenever I use an LLM. People like unlimited plans, we are used to them for internet, text messaging, etc. The current pricing models just feel bad.

My opinion is all of these tools should completely get rid of the "pay 20/month, 200/month", etc just to get access to some beholden rate limited amount that becomes hard to track. Mask off completely and just make it completely usage based for everyone. You could do something for trial users like first 20 (pick your number here) requests are free if you really need to in order to get people on board. Or you could do…

> Mask off completely and just make it completely usage based for everyone.

you can already pay per token by giving Claude Code an API key, if you want.

thus, the subtext of every complaint on this thread is that people want "unlimited" and they want their particular use to be under whatever the cap is, and they want it to be cheap.

Re: Claude Code weekly rate limits

#276
post #46
post #44

Earlier quoted context omitted.

If 95% of users are under the limit then it isn't a "fake" plan.

fake for 5% of users. will they refund me my sub? when I subbed It was unlimited, they've rugged the terms twice already since then in less than a month

you were rugged? you sincerely expected you could run parallel opus agents 24/7 for $200/mo? who did the rugging here? did it occur to you that paying $7/day for a 24/7 team of dedicated senior engineers, roughly being paid 30 cents an hour, was not sustainable?

yes it was unlimited. so is the public water fountain. but if you show up and hold the button down to run nonstop while chanting "it says unlimited free water doesn't it??" you must expect that it will no longer be unlimited.

we went from reasonably unlimited, which 95% of users enjoyed, respected and recognized was subsidized, to no unlimited anymore because 5% wanted to abuse it. now you can scream about being rugged, just like you did for cursor, and jump to the next subsidized provider that you can abuse until there's none left. you do realize that every time "unlimited" gets abused it raises the standard of limits and pricing across the board until it becomes normalized. this was going to happen anyways on a longer timeframe where providers could optimize inference and models over time so the change wasn't so shocking, but abuse accelerated it.

Re: Claude Code weekly rate limits

#277

Earlier quoted context omitted.

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.

SMS routing and billing systems did cost money. Especially billing, as the standards had nothing for it, so it was done by 3rd party software for a very long time.

Of course, how pleasingly circular. "It's so expensive because it costs so much to charge you for it".

Re: Claude Code weekly rate limits

#278
post #226

Earlier quoted context omitted.

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.

I've noticed the frequent perf issues and I'm on the 20x plan myself - good point that you'd want to stop the bleeding or bad actors to make sure the majority have a better experience

Re: Claude Code weekly rate limits

#279
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…

> why not figure out how to special case them without affecting everyone else

I’m guessing that they did, and that that’s what this policy is.

If you’re talking about detecting account sharing/reselling, I’m guessing they have some heuristics, but they really don’t want the bad press from falsely accusing people of that stuff.

Post reply on HN