Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Claude Code weekly rate limits

news.ycombinator.com

Post reply on HN
Print view View original

671–680 of 724 posts

Re: Claude Code weekly rate limits

#671

Post by lelanthran »

hkt wrote: post #137
cmsjustin wrote: post #115

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.

What's the reasoning behind this? They are already doing the efficient "economies of scale" thing and they are already at full capacity (hence rate limiting).

The only way forward for this AI providers is to raise prices, not lower them.

Re: Claude Code weekly rate limits

#672

Post by nkassis »

gorbypark wrote: post #633
Aurornis wrote: post #288

Earlier quoted context omitted.

> If I use claude code & claude its over in about 30 minutes. Can you share what you're doing? I've been experimenting with Claude Code and I feel like I have to be doing a lot with it before I even start seeing the usage warning limits on the $20/month plan. When I see people claiming they're getting rate limited after 30 minutes on the $100/month plan I have a hard time understanding what they're doing so different…

As a $20 month user, I can tell you in my experience it's "refactoring" jobs that really smash through those tokens quickly. If you do a "write a component that does this" kinda thing, you can use the $20 plan almost an unlimited amount of time. If you are doing "find all instances of ComponentFoo, change to ComponentBar, refactor each screen for correct usage of ComponentBar" kinda things, it's going to grep through…

That kind of gives a point in favor of AI enabled IDEs, these kind of operations could often be achieved with simple refactoring tools available without AI today and save massive amount of trees.

Re: Claude Code weekly rate limits

#673

Post by randomcarbloke »

zamadatix wrote: post #478
xpe wrote: post #363

Earlier quoted context omitted.

> pressures users to hoard As a pedantic note, I would say 'ration'. Things you hoard don't magically go away after some period of time.

FWIW neither hoard nor ration imply anything about permanence of the thing to me. Whether you were rationed bread or you hoarded bread, the bread isn't going to be usable forever. At the same time whether you were rationed sugar or hoarded sugar, the sugar isn't going to expire (with good storage). Rationed/hoarded do imply, to me, something different about how the quantity came to be though. Rationed being given or…

Bread can be rationed but cannot be hoarded.

Re: Claude Code weekly rate limits

#674

Post by npongratz »

Aurornis wrote: post #231
alwillis wrote: post #175

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…

Words mean things. Please don't call it "unlimited" if you limit it.

Re: Claude Code weekly rate limits

#675

Post by mike_hearn »

gorbypark wrote: post #633
Aurornis wrote: post #288

Earlier quoted context omitted.

> If I use claude code & claude its over in about 30 minutes. Can you share what you're doing? I've been experimenting with Claude Code and I feel like I have to be doing a lot with it before I even start seeing the usage warning limits on the $20/month plan. When I see people claiming they're getting rate limited after 30 minutes on the $100/month plan I have a hard time understanding what they're doing so different…

As a $20 month user, I can tell you in my experience it's "refactoring" jobs that really smash through those tokens quickly. If you do a "write a component that does this" kinda thing, you can use the $20 plan almost an unlimited amount of time. If you are doing "find all instances of ComponentFoo, change to ComponentBar, refactor each screen for correct usage of ComponentBar" kinda things, it's going to grep through…

Are people really using LLMs this way? Can't your IDE at least attempt global refactorings? I get that it's harder with dynamic languages like Python but using an LLM to rename a class seems like using a nuke to crack a nut.

Re: Claude Code weekly rate limits

#676

Post by xpe »

nothrabannosir wrote: post #594
jjani wrote: post #500

Earlier quoted context omitted.

> Hoard seems more ad hoc and fear-driven: better keep yet another beat-up VGA cable, just in case. Counterexample: animals hoarding food for winter time, etc.

Rather a corroborating example than a counter, if you believe how many nuts squirrels lose sight of after burying them.

Exactly. How many random computer dongles and power supplies get buried in sundry boxes that are effectively lost to the world?

Re: Claude Code weekly rate limits

#677

Post by deeth_starr_v »

lukaslalinsky wrote: post #620
TheOtherHobbes wrote: post #593

Earlier quoted context omitted.

Which is a huge problem, because you literally have no idea what you're paying for. One day a few of hours of prompting is fine, another you'll hit your weekly limit and you're out for seven days. While still paying your subscription. I can't think of any other product or service which operates on this basis - where you're charged a set fee, but the access you get varies from hour to hour entirely at the provider's w…

What happens when you have a gym membership, but you go there during their busy hours? What they could do is pay as you go, with pricing increasing with the demand (Uber style), but I don't think people would like that much.

Your analogy would work if the gym would randomly suspend your membership for a week if you worked out too much during peak hours

Re: Claude Code weekly rate limits

#678

Post by Wowfunhappy »

prolly97 wrote: post #576
Wowfunhappy wrote: post #88

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…

> Loosing it for a couple of days is more palatable Sorry, I'll just be "that guy" for a moment. Assuming that access is cut at a random time during the week, the average number of days without Claude would be 3.5. That's not reasonable as it's dependant on usage. So assume that you've always been just shy of hitting the limit, and you increase usage by 50%, then you'd hit the limit 4.67 days in. Just 2-3 hours shy o…

My original post wasn't clear and that's my fault, but I am taking that into account. When I said "that's it for the week" I meant "the remainder of the week." It's just a mouthful to write "the remainder of the week" each time.

And... well, I am worried that I could do something stupid or accidental on Monday and Tuesday and then loose access with more than half of the week left, especially since, as everyone else has noted, Claude doesn't show you how close to the limit you are until you've almost hit it. (That said, I also appreciate that it doesn't warn me too early, or I would be constantly watching the usage tick up well before I actually need to worry about it.)

A couple of weeks ago, Claude got into some kind of weird loop where it just kept saying something like "now I need to add the code continuation" over and over and over again. I had auto-accept turned on, and it was chugging for several hours before I realized something was wrong and stopped it. Who knows how much usage that burned! Luckily, it happened late in the evening, so I knew my usage would reset the next day anyway. But IIRC it was also a Monday evening...

Re: Claude Code weekly rate limits

#679

Post by yifanl »

rapind wrote: post #460
_jab wrote: post #208

Earlier quoted context omitted.

> 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.

A decent chunk (more than 1/20) account shared netflix. Also there are probably some who are account sharing with more than one other person. I don't really doubt it.

Sharing Netflix passwords was literally a common enough phonomena that it purt of Netflix's advertising, that's a very unique case that I don't expect to be happening for Anthropic.

Re: Claude Code weekly rate limits

#680

Post by icelancer »

flashgordon wrote: post #359
icelancer wrote: post #216

Earlier quoted context omitted.

It's not too bad - I run 6x RTX 3090s on a 2nd-gen Threadripper with PCIe bifurcation cards. The energy usage is only really bad if you're training models constantly, but inference is light enough. I use 208V power but 120V can indeed be a challenge. The USA has split phase wiring; every house has 220-240V if they need it. Bit of a misunderstanding of how our power works - we have 220-240V on tap, but typical outlets…

Yeah at this point the goal is to see how to maximize for inference. For training it is impossible from the get go to compete with the frontier labs anyway. Im trying to calculate (even amortized over 2 years) the daily cost of running the equivalent rig that can get close to a single claude agent performance. (without needing a 6-digit gpu).

Really the only reason to have a local setup is for 24/7 on-demand high-volume inference that can't tolerate enormous cold starts.
Post reply on HN