Earlier quoted context omitted.
Not every customer, even a paying customer, demands reliability at a particular level. Market segmentation tends to address those situations: pay more, get more.
'I don't want to hold companies to account for failing to deliver services, therefore I think everyone else should live by my permissive "standards".'
Pro Max 5x quota exhausted in 1.5 hours despite moderate usage
471–480 of 695 posts
Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage
#472Earlier quoted context omitted.
> Just because people pay for things doesn't mean they know or understand what they are paying for. I believe, respectfully, that’s precisely what is happening in this thread because you keep complaining about the absence of an SLA that was never in the agreement, as though it is—or is supposed to be—there, and therefore the existence of some “rights” that would flow from that.
There are no SLAs, in any agreement, thats the problem.
Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage
#473Earlier quoted context omitted.
I’m really confused. We were talking about SLAs, not other product features. Are you moving the goalposts?
There isn't an SLA nor is there any protections around file uploads to their services. Two, bad, things can be true at the same time.
Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage
#474Earlier quoted context omitted.
We are taking it seriously, and are continuing to investigate. We are not trusting the metrics.
The quantitative ux research team at Google was created for exactly this problem: a service which became popular before the right metrics existed, meaning metrics need to be derived first, then optimized. We would observe users (irl), read their logs, then generate experiments to improve the behavior as measured by logs, and return to see if the experiment improves irl experiences. There were not many of us and we ar…
Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage
#475I don't have the receipts, but I think they were somewhat closer in Jan/Feb.
Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage
#476Earlier quoted context omitted.
> It goes into long exploration loops for 5+ minutes even when I point it to the exact files to inspect. Give it a custom sandbox and context for the work, so it has no opportunity to roam around when not required. AI agentic coding is hugely wasteful of context and tokens in general (compared to generic chat, which is how most people use AI), there's a whole lot of scope for improvement there.
But the problem is it used to not need that before. These days, you have to think twice before you summon a subagent.
This is exactly what I (and many others) kept trying to tell the pro-AI folk 18 months ago: there is no value to jumping on the product early because any "experience" you have with it is easily gained by newcomers, and anything you learned can easily be swapped out from under you anyway.
Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage
#477Hey 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…
Even if Anthropic is working in good faith to lower infrastructure costs, developers need more than 5 minutes to notice that CC completed a task, review its changes and ask it to merge. Only developers who do not review code changes can live with such a TTL...
Consider making this value configurable as the ideal TTL value is different for each person. If people are willing to pay more for 30 minutes TTL than 5 minutes, they should be able to.
Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage
#478Earlier quoted context omitted.
I think in this case, we probably have different experiences that shape how we see some things differently: I see many (very smart) people doing certain things that are not optimal (eg: copy-paste entire files instead of referencing them or tell claude at every message to "read CLAUDE.md and follow its instructions precisely") which can lead to a lot of token waste. If certain system prompts were tweaked internally o…
This is literally victim blaming. When people haven't been having issues until now, why is it their fault? Anthropic is providing a paid service to paying users. It's not acceptable that they degrade our experience to save some money and it's not acceptable to blame everybody else who didn't cause the issue.
Again, I agree with you and the service should be at least reliable but to be completely fair, if I had to bet, the amount of usage people get for 100/mo is probably only balanced out by the corporate/entreprise customers paying their bill to Anthropic via API usage.
If we look at it through this lens, this limits are not surprising at all, except maybe on how generous they are/were. It’s pretty obvious that they want to force people to pay as they go….
Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage
#479Hey 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…
Long term claude code user here. Is the first time i've had to setup a hook to codex to review claude output.
Is hallucinating like never before
Is missing key concepts/instructions in context like never before
Is writing bad code that will "pass test" much more. Before it use to try be critic and do good code, now it will try to hack test and bypass intructions for a green pass.
Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage
#480Earlier quoted context omitted.
Why are you all of a sudden running into so many issues like this? Could it be that all of the Anthropics employees have completely unlimited and unbounded accounts, which means you don't get a feeling of how changes will affect the customers?
The number of people using Claude Code has grown very quickly, which means: - More configurations and environments we need to test - Given an edge/corner case, it is more likely a significant number of users run into it - As the ecosystem has grown, more people use skills and plugins, and we need to offer better tools and automation to ensure these are efficient We do actually dogfood rate limits, so I think it's som…
with that said, on my 5x plan, I could have multiple sessions working and the limit was far away. Around when you introduced the whole more tokens during off-peak hours and fewer tokens during working US hours, Even with a single session, using no plugins at all (I uninstalled OMC) I run into limits very often.
I have not performed any rigorous tests but it feels like I have about 25% of what I used to have or less. This is all without using teams of agents, or ralph loops or anything like that. Just /plan and execute in a single session. I have restored the /clear context before executing plan to try and mitigate things. I will also try the 400k context since, in my experience, the 1M tokens have not made Opus 4.6 noticeably smarter for my small webapp use-case.
Best of luck to you!
ps: whenever you introduce a change, please make it optional AND ask the user about it at first. Don't just yank things suddenly (like the /clear context and apply plan option.) as I spent hours trying to figure out how I broke it before I saw your note and how to re-enable it.