Live data from Hacker News

Claude Code weekly rate limits

news.ycombinator.com

341–350 of 724 posts

Re: Claude Code weekly rate limits

#341
post #137

Earlier quoted context omitted.

They were not expensive to operate, they were only expensive for consumers

Competition is the thing. Prices will drop as more AI code assistants get more adoption. Prices will probably also drop if anyone ever works out how to feasibly compete with NVIDIA. Not an expert here, but I expect they're worried about competition regulators, who will be watching them very closely.

> Prices will drop as more AI code assistants get more adoption.

No, they won't. Because "AI assistants" are mostly wrapped around a very limited number of third-party providers.

And those providers are hemorrhaging money like crazy, and will raise the prices, limit available resources and cut off external access — all at the same time. Some of it is already happening.

Re: Claude Code weekly rate limits

#342

Earlier quoted context omitted.

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…

> My opinion is all of these tools should completely get rid of the "pay 20/month, 200/month", etc just to get access. I think that you should just subscribe to a preset allotment of tokens at a certain price, or a base tier with incremental usage costs for models that aren’t tiny (like paid per minute “long distance calling”). I use an LLM tool that shows the cost associated with each message/request and most are pe…

> you should just subscribe to a preset allotment of tokens at a certain price

The problem is that there's no way to gauge or control token usage.

I have no idea why Claude Code wrote that it consumed X tokens now, and Y tokens later, and what to do about it

Re: Claude Code weekly rate limits

#343
I hope that this communication is not typical of the output of Claude, but if it is it should get a prize of sorts for vagueness and poor style. No way for users to find out if they are affected or not, lots of statements that carry zero information. Not impressed, to put it mildly, besides, they should have enforced their limits from day #1 as they were, not allow people to spend 10K worth of resources on a $200 plan. Now they risk those that are not even affected from re-thinking their relationship with the company.

Re: Claude Code weekly rate limits

#344
post #11

200 bucks a month isn't enough. Fine. Make a plan that is enough so that I will be left alone about time limits and enforced breaks. NOTHING breaks flow better than "Woops! Times up!"; it's worse than credit quotas -- at least then I can make a conscious decision to spend more money or not towards the project. This whole 'twiddle your thumbs for 5 hours while the gpus cool off' concept isn't productive for me. '35 ho…

> '35 hours' is absolutely nothing when you spawn lots of agents, and the damn thing is built to support that behavior. I wouldn't call "spawning a lot of agents" to be a typical use case of the personal plan. That was always in the domain of switching to a pay as you go API. It's nice that they allowed it on the fixed rate plans, but those plans were always advertised as higher limits, not unlimited.

It’s literally recommended in “Best practices”: https://www.anthropic.com/engineering/claude-code-best-pract...

Re: Claude Code weekly rate limits

#345

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 don't understand why the current setup for rate limits wouldn't be sufficient to stop this kind of thing.

Re: Claude Code weekly rate limits

#347

I understand, but I also will not pay a subscription fee for limited service. I canceled as soon as I got this e-mail. Too bad I signed up for an annual subscription last month. This is also exactly why I feel this industry is sitting atop a massive bubble.

As far as the email says, this change is triggered at your next billing cycle. So your account is grandfathered in until next year.

Re: Claude Code weekly rate limits

#348

Earlier quoted context omitted.

Think of an insane number of requests. Now 20x it, that's what the top 1% of Claude users are at. Just fleecing the service dry. hard problem, what else could Claude do tbh

...maybe use their superintelligent AI to come up with a solution that specifically targets the abusers?

Claude says - The key is maintaining user agency—let them choose how to manage their usage rather than imposing arbitrary cutoffs.

It suggests:

Transparent queueing - Instead of blocking, queue requests with clear wait time estimates. Users can choose to wait or reschedule.

Usage smoothing - Soft caps with gradually increasing response times (e.g., 2s → 5s → 10s) rather than hard cutoffs.

Declared priority queues - Let users specify request urgency. Background tasks get lower priority but aren't blocked.

Time-based scheduling - Allow users to schedule non-urgent work during off-peak hours at standard rates.

Burst credits - Banking system where users accumulate credits during low usage periods for occasional heavy use.

Re: Claude Code weekly rate limits

#349
This is fantastic news. They're burning through too much cash too fast. They're going to have to sooner or later charge more money at which point businesses will balk at the price and the AI hype cycle will come to an end. I can't wait.
Post reply on HN