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?
Claude Code weekly rate limits
261–270 of 724 posts
Re: Claude Code weekly rate limits
#262I'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.
Re: Claude Code weekly rate limits
#263Earlier 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.
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
#264Re: Claude Code weekly rate limits
#265Re: Claude Code weekly rate limits
#266Is 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
#267I'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…
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
#268Re: Claude Code weekly rate limits
#269We 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.
Re: Claude Code weekly rate limits
#270I'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…
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.