Live data from Hacker News

Claude Code weekly rate limits

news.ycombinator.com

261–270 of 724 posts

Re: Claude Code weekly rate limits

#261
post #26

Guess they ran into the usage limits themselves when they worked on the messaging in Claude Code: "Claude usage limit reached. Your limit will reset at 8pm (UTC)" Why not use the user's timezone?

this is a super-american thing, not a AI company thing

Re: Claude Code weekly rate limits

#262
post #256

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…

Of course ripgrep runs on your machine and you control it.

ripgrep is an example for "tool I've grown accustomed to", where it runs is irrelevant.

Re: Claude Code weekly rate limits

#263
post #135

Earlier quoted context omitted.

That’s not what the parent commenter asked though, they wanted a price for not being concerned about limits. The API pricing is that.

I doubts thats what they want. They want a static fixed price, $5k a month for example and never have to think about it.

Take the API and assume 24/7 usage (or whatever working hours are). That’s your fixed cost.

It’s more likely that this sum is higher than they want. So really it’s not about predictability.

Re: Claude Code weekly rate limits

#265
I have been using Gemini for some time now. I switched away from Claude because I was frustrated with the rate limits and how quickly I seemed to reach them. Last week I decided to give it Claude another try so I resigned up. I linked a personal repository I am working on, prompted it for suggestions on potential refactoring recommendations and hit send. It immediately stopped and said this prompt would reach my limits. Immediately reconsidered my subscription.

Re: Claude Code weekly rate limits

#266
I'm working on a coding agent for typescript teams and I'm curious how people would like to consume these things generallyin terms of price a predictability. I've thought through a bunch of stuff, not sure what is best... Right now I have a base fee and then a concept of credits, the base fee ($500) includes 10k credits, and the credits are tied to PRs, it works out to 100 "credits" per simple PR and 200 "credits" for a complex PR, Commit is 20 credits. 20 credits are $5. PR reviews are free.

Is this way too complicated? It feels complicated to me and I worked on it, so I presume it is?

I don't want to end up in some "you can work for X number of hours" situation that seems... not useful to engineers?

How do real world devs wanna consume this stuff and pay for it so there is some predictability and it's useful still?

Thank you. :)

Re: Claude Code weekly rate limits

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

Because the goal is to extract more money from the people who have significant usage. These users are the actual targets of the product. The idea that it’s a few bad actors is misdirection of blame to distract “power users”.

They undercharged for this product to collect usage data to build better coding agents in the future. It was a ploy for data.

Anecdotally, I use Claude Code with the $20/mo subscription. I just use it for personal projects, so I figured $20 was my limit on what I’d be willing to spend to play around with it. I historically hit my limits just a few times, after ~4hrs of usage (resets every 5hrs). They recently updated the system and I hit my limits consistently within an hour or two. I’m guessing this weekly limit will affect me.

I found a CLI tool (which I found in this thread today) that estimates I’m using ~$150/mo in usage if I paid through the API. Obviously this is very different from my payments. If this was a professional tool, maybe I’d pay, but not as a hobbyist.

Re: Claude Code weekly rate limits

#268
I think they should totally do this but I think they should call it "rate-limiting" instead of "weekly limit". Seems pretty clear to me that the purpose is to avoid situations where people are running 5 background agents 24/7, not the person working during business hours normally. Reframing this makes it more clear this is about bots not users.

Re: Claude Code weekly rate limits

#269

We will see but I hit the limit multiple times a day so I am a bit scared that this would mean looking for alternatives.

Using Claude Code or the web UI? If when using Claude Code, you may need to break your codebase up into smaller chunks to help. That said, there's no fucking way I am getting what they claim w/Opus in hours. I may get two to three queries answered w/Opus before it switches to Sonnet in CC.

Claude Code cli. Yeah, I gave up on Opus as I deed it switches really fast (200 sub). I made my own flow tooling and prompting which uses way less than it does on its own, but I still hit the limits.

Re: Claude Code weekly rate limits

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

> if it affects only a minority of accounts, why not figure out how to special case them without affecting everyone else

that's exactly what they have done - the minority of accounts that consume many standard deviations above the mean of resources will be limited, everyone else will be unaffected.

Post reply on HN