Live data from Hacker News

Claude Code weekly rate limits

news.ycombinator.com

371–380 of 724 posts

Re: Claude Code weekly rate limits

#371

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…

Don't you also have an API subscription to provide overflow capacity?

Re: Claude Code weekly rate limits

#372
Tools that generate code will have a lot of competition. It's good that Athropic is refining it's pricing but would have been better if users got to know their exact usage and apply own controls.

Frustrated users, who are probably using the tools the most will try other code generation tools.

Re: Claude Code weekly rate limits

#373

Earlier quoted context omitted.

You can use an API key to get more usage on a pay-as-you-go basis.

Yes, but that's so expensive I will never do it!

With one months exception, I've never gotten past $150 with API. I plan to do the $100 plan and use the API for overflow. I think I will come out ahead.

Re: Claude Code weekly rate limits

#374

Earlier quoted context omitted.

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”…

If it behaves anything like the GPT-4.5 Limit, it will let you know when you near the limit.

Claude daily limit sure didn't.

Re: Claude Code weekly rate limits

#375

Earlier quoted context omitted.

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

Right, that's crucial to understand. In 1985 you could make a direct dial from England to the US but it was eye wateringly expensive. £2 per minute. An hour's call to your mum? That's over £100. But the cost to Bell and British Telecom was not £2 per minute, or £1 per minute, or even 1p per minute, it was nothing at all. Their costs were not for the call, but for the infrastructure over which the call was delivered,…

There was some capital expenditure that had to be paid for.

In the US, ATT was just barely deregulated by then so the prices were not just 'out of thin air'.

Re: Claude Code weekly rate limits

#376
post #362

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…

It makes me sad that devs start relying on proprietary online services to be able to work. We have been lucky enough to have FOSS tools to do everything and not to have to rely on any specific service or company to work and some of us are deciding to become like Monsanto-addicted farmers who forgot how to do their jobs without something they have to pay every month.

The very recent agentic open weights models seem to be shaping up, so if all fails you can host one of these yourself (if you have the vram) or host it yourself somewhere.

Re: Claude Code weekly rate limits

#377
post #337

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…

[flagged]

Was it necessary to post this?

FYI many input methods (including my own) turn two hyphens into an em dash. The em-dash-means-LLM thing is bogus.

Re: Claude Code weekly rate limits

#378
post #325

Earlier quoted context omitted.

I hope you thoroughly go through these as a human, purely AI written stuff can be horrible to read.

Docstring slop is better than code slop - anyway that is what git commits are for - and I have 4.5 hours to do that till next reset.

Coding is turning into an MMO!

Re: Claude Code weekly rate limits

#379

I'm not sure how this will play out long term, but I really am not a fan of having to feel like I'm using a limited resource whenever I use an LLM. People like unlimited plans, we are used to them for internet, text messaging, etc. The current pricing models just feel bad.

I personally take an issue with them expecting that your usage would be more or less consistent throughout the month. Instead, I might have low usage throughout most of the month and then an 11 hour binge a few days, which in most cases would involve running into rate limits (either that, or just token limitations for inputs). That's why using the API directly and paying for tokens anything past that basic usage feel…

This is my strategy as well. I definitely have surges of usage.

Except for one catastrophic binge where I accidentally left Opus on for a whole binge (KILL ME!!!), I use around $150/month. I like having the spigot off when I am not working.

Would the $100/month plan plus API for overflow come out ahead? Certainly on some months. Over the year, I don't know. I'll let you know.

Re: Claude Code weekly rate limits

#380
post #234

Earlier quoted context omitted.

You're paying for prioritization during high traffic periods, not for 2x usage.

That's not what they claim: https://www.anthropic.com/pricing > Max > Choose 5x or 20x more usage per session than Pro* > Higher output limits for all tasks > Priority access at high traffic times That first bullet pretty clearly implies 4x the usage and the last one implies that Max gets priority over Pro, not that 20x gets priority over 5x.

That is sort of what it implies, but I don't think that's what's actually happening on the backend. I was looking at this yesterday though and I agree that it's all a bit hand-wavy. I feel for them somewhat though because it's hand-wavy because it's a difficult problem to solve. They're essentially offering spot instances.
Post reply on HN