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

641–650 of 724 posts

Re: Claude Code weekly rate limits

#641

Post by eichin »

forty wrote: post #583
epolanski wrote: post #564

Earlier quoted context omitted.

People who use it extensively may know whether it makes them significantly faster or not.

I assume they have an opinion on the topic, but it doesn't mean they are right (or wrong). Think of driving a car. If the shortest path (in term to time of travel) is through traffic jam, and there is a longer path where you can drive must faster, it's very likely that most people will have the feeling to be more efficient with the longer path. Also the slow down of using LLM might be more subtle and harder to measur…

We've known for decades that self-reported time perception in computer interactions is drastically off (Jef Raskin, The Humane Interface in particular) so unless they have some specifically designed external observations, they are more likely to be wrong. (There have been more recent studies - discussed here on HN - about perception wrt chat interfaces for code specifically - that confirm the effect on modern tools.)

Re: Claude Code weekly rate limits

#642

Post by blitzar »

rapind wrote: post #459
blitzar wrote: post #282

Earlier quoted context omitted.

> Anthropic is saying that one out of every 20 users will hit the new limit. I regularly hit the the Pro limits 3 times a day using sonnet. If I use claude code & claude its over in about 30 minutes. No multi 24/7 agent whatever, no multiple windows open (except using Claude to write a letter between claude code thoughts). I highly doubt I am a top 5%er - but wont be shocked if my week ends on a wednessday. I was jus…

I think you'll want to specify your /model to not use opus. Strangely unintuitive, but I opted out of opus on the max plan myself and aren't really having any usage issues since.

no opus in claude code on my el'cheapo plan ($20 - pro) - used it occasionally in claude desktop and its as expensive as they advertise.

Re: Claude Code weekly rate limits

#644

Post by zelphirkalt »

epolanski wrote: post #586
forty wrote: post #583

Earlier quoted context omitted.

I assume they have an opinion on the topic, but it doesn't mean they are right (or wrong). Think of driving a car. If the shortest path (in term to time of travel) is through traffic jam, and there is a longer path where you can drive must faster, it's very likely that most people will have the feeling to be more efficient with the longer path. Also the slow down of using LLM might be more subtle and harder to measur…

Apologies, but from antirez[1] to many other brilliant 1000x developers advocate for LLMs speeding up the process. I can see the impact on my own input both in quantity and quality (LLMs can come up with ideas I would not come up to, and are very useful for tinkering and quickly testing different solutions). As any tool it is up to the user to make the best out of it and understand the limits. At this point it is cle…

1000x developers, ahahaha! Come on now, this is too comical. Even 10x is extremely rare.

The deciding factor is not speed. It is knowledge. Will I be able to dish out a great compiler in a week? Probably not. But an especially knowledgeable compiler engineer might just do it, for a simple language. Situations like this are the only 10x we have in our profession, if we don't count completely incapable people. The use of AI doesn't make you 1000x. It might make you output an infinite factor of AI slop more, but then you are just pushing the maintenance burden to a later point in time. In total it might make your output completely useless in the long run, making you a 0x dev in the worst case.

Re: Claude Code weekly rate limits

#645

Post by wiseowise »

el_benhameen wrote: post #128
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…

This is how I feel about the 100 msg/wk limit on o3 for the ChatGPT plus plan. There’s no way to see how much I’ve used, and it’s an important enough resource that my lizard brain wants to hoard it. The result is that I way underutilize my plan and go for one of the o4-mini models instead. I would much prefer a lower daily limit, but maybe the underutilization is the point of the weekly limit. *edited to change “pro”…

> There’s no way to see how much I’ve used

Hover on it on a desktop, it’ll show how many requests you have left.

Re: Claude Code weekly rate limits

#647

Post by Filligree »

raincole wrote: post #448
CodeBrad wrote: post #179

Earlier quoted context omitted.

I think Claude Code also already has the option to provide an API key directly for usage based pricing. I'm a fan of having both a subscription and a usage based plan available. The subscription is effectively a built in spending limit. If I regularly hit it and need more value, I can switch to an API key for unlimited usage. The downside is you are potentially paying for something you don't use, but that is the same…

Giving how expensive Claude Code is if you use API key, I think it's safe to assume the subscription model is bleeding money out.

Claude is also really expensive compared to every other model.

Maybe that reflects higher underlying costs. Maybe their API prices are just inflated.

Re: Claude Code weekly rate limits

#648

Post by kelnos »

I don't have a problem with companies adding usage limits and whatnot, but it's shady to do for existing customers who have pre-paid for some amount of time. If I pay the yearly up-front amount, I expect my terms of use to stay the same for that entire year.

Re: Claude Code weekly rate limits

#649

Post by kelnos »

Wowfunhappy wrote: post #509
aspenmayer wrote: post #454

Earlier quoted context omitted.

> prevent people from gaming the system If I sit down for dinner at an all-you-can-eat buffet, I get to decide how much I’m having for dinner. I don’t mind if they don’t let me take leftovers, as it is already understood that they mean as much as I can eat in one sitting. If they don’t want folks to take advantage of an advertised offer, then they should change their sales pitch. It’s explicitly not gaming any system…

I feel like using Claude Code overnight while you sleep or sharing your account with someone else is equivalent to taking home leftovers from an all-you-can-eat buffet. I also find it hard to believe 5% of customers are doing that, though.

I think this is just a bad analogy. I've definitely set Claude Code on a task and then wandered off to do something else, and come back an hour or so later to see if it's done. If I'd chosen to take a nap, would you say I'm "gaming the system"? That's silly. I'm using an LLM agent to free up my own time; it's up to me to decide what I do with that time.

Re: Claude Code weekly rate limits

#650

Post by Filligree »

j45 wrote: post #432
furyofantares wrote: post #74

Earlier quoted context omitted.

The Sonnet usage does not really look limited at 240-480 hours per week (a week has 168 hours in it). Opus at 24-40 looks pretty good too. A little hard to believe they aren't losing a bunch of money still if you're using those limits tbh.

The calculation of hours is a little tough to imagine sometimes, is it the inference time itself, or the period of time used? Is there an average token cost per hour of use (average or explicit?)

It had better be inference time; I regularly have Claude call out to tools that take hours to run.
Post reply on HN