Live data from Hacker News

Pro Max 5x quota exhausted in 1.5 hours despite moderate usage

github.com

231–240 of 695 posts

Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage

#231

Hey all, Boris from the Claude Code team here. We've been investigating these reports, and a few of the top issues we've found are: 1. Prompt cache misses when using 1M token context window are expensive. Since Claude Code uses a 1 hour prompt cache window for the main agent, if you leave your computer for over an hour then continue a stale session, it's often a full cache miss. To improve this, we have shipped a few…

For me definitely the worst regression was the system prompt telling claude to analyze file to check if it's malware at every read. That correlates with me seeing also early exhausted quotas and acknowledgments of "not a malware" at almost every step.

It is a horrible error of judgement to insert a complex request for such a basic ability. It is also an error of judgement to make claude make decisions whether it wants to improve the code or not at all.

It is so bad, that i stopped working on my current project and went to try other models. So far qwen is quite promising.

Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage

#232

Earlier quoted context omitted.

My take is that was the plan all along. Once people won't be able to think anymore and business expect the level of productivity witnessed before, will have no choice but cough up whatever providers bill us.

"enshittification" gets thrown around a lot, but this is the exact playbook. Look at the previous bubble's cash cow: advertising. Online advertising is now ubiquitous, terrible, and mandatory for anyone who wants to do e-commerce. You can't run a mass-market online business without buying Adwords, Instagram Ads, etc. AI will be ubiquitous, and then it will get worse and more expensive. But we will be unable to return…

But why would they make the product shittier and not just more expensive? A lot of the complaints have been the model getting lost and going rogue.

Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage

#233

Earlier quoted context omitted.

source?

After googling https://www.reddit.com/r/singularity/comments/1psesym/openai...

I've seen sources like this before. It's all hearsay and promo. I was asking for any publicly available verifiable information regarding the cost of inference at scale. I haven't seen any such info personally which is why I asked.

I'm dying to see S-1 filing for Anthropic or OpenAI. I don't actually think inference is as cheap as people say if you consider the total cost (hardware, energy, capex, etc)

Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage

#235

Hey all, Boris from the Claude Code team here. We've been investigating these reports, and a few of the top issues we've found are: 1. Prompt cache misses when using 1M token context window are expensive. Since Claude Code uses a 1 hour prompt cache window for the main agent, if you leave your computer for over an hour then continue a stale session, it's often a full cache miss. To improve this, we have shipped a few…

I don't want a nudge. I want a clear RED WARNING with "You've gone away from your computer a bit too long and chatted too much at the coffee machine. You're better off starting a new context!"

Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage

#236
post #91

Earlier quoted context omitted.

Where is your evidence of this "massive cost"? Inference is massively profitable for both anthropic and openai. Training is not.

This article convinced me otherwise https://www.wheresyoured.at/the-subprime-ai-crisis-is-here/

This is a great article, thanks for sharing

Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage

#237

Earlier quoted context omitted.

OpenAI (Codex) keeps on resetting the usage limits each time they fuck up... I have yet to see Anthropic doing the same. Sorry but this whole thing seems to be quite on purpose.

[flagged]

Me and my colleagues faced, over the last ~1 month or so, the same issues.

With a new version of Claude Code pretty much each day, constant changes to their usage rules (2x outside of peak hours, temporarily 2x for a few weeks, ...), hidden usage decisions (past 256k it looks like your usage consumes your limits faster) and model degradation (Opus 4.6 is now worse than Opus 4.5 as many reported), I kind of miss how it can be an user error.

The only user error I see here is still trusting Anthropic to be on the good side tbh.

If you need to hear it from someone else: https://www.youtube.com/watch?v=stZr6U_7S90

Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage

#238
post #200

Claude has gotten noticeably worse for me too. It goes into long exploration loops for 5+ minutes even when I point it to the exact files to inspect. Then 30 minutes later I hit session limits. Three sessions like that in a day, and suddenly 25% of the weekly limit is gone. I ended up buying the $100 Codex plan. So far it has been much more generous with usage and more accurate than Claude for the kind of work I do.…

Any good reasonable alternatives? Gemini is like prodigious 3yo hopeless for my projects, anybody tested some opencode with kimi or something?

I'm adding two extra gpus to my local rig. Turns out qwen 3.5 122b is already enough to handle (finish with moderate guidance) non-planning parts of my tasks.

Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage

#239

Hey all, Boris from the Claude Code team here. We've been investigating these reports, and a few of the top issues we've found are: 1. Prompt cache misses when using 1M token context window are expensive. Since Claude Code uses a 1 hour prompt cache window for the main agent, if you leave your computer for over an hour then continue a stale session, it's often a full cache miss. To improve this, we have shipped a few…

Would it be possible to increase the cache duration if misses are a frequent source of problems?

Maybe using a heartbeat to detect live sessions to cache longer than sessions the user has already closed. And only do it for long sessions where a cache miss would be very expensive.

Post reply on HN