Essentially I also am now using sonnet instead of opus most of the time as a default. Even a single project only coding session with opus without any external plugins or skills won’t make it to the 5hr mark now before limits claw in. And the weekly limit is even more brutal now it seems, reaching 50%+ in like ~2 days now easily … with mostly sonnet! On the highest 20x plan!
Pro Max 5x quota exhausted in 1.5 hours despite moderate usage
431–440 of 695 posts
Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage
#432Earlier quoted context omitted.
https://support.claude.com/en/articles/14063676-claude-march... "Usage remains unchanged" between 8am and 2pm. I feel the Claude subreddits are mostly full of speculation and dramatics, not much productive discussion, like endless exaggerated complaining about downtime. Pretty much the same as a pretty significant chunk of reddit nowadays. Edit: the rumor was probably stemming from this https://www.theregister.com/20…
https://www.reddit.com/r/Anthropic/comments/1s4iefu/update_o... is an official post by Anthropic. > Your weekly limits remain unchanged. During peak hours (weekdays, 5am–11am PT / 1pm–7pm GMT), you'll move through your 5-hour session limits faster than before. Overall weekly limits stay the same, just how they're distributed across the week is changing. I'm Eastern time and peak usage works out as 8am-2pm (the bulk o…
Yeah I hadn't been aware of that change previously. I'm also ET, but perhaps I just don't use it enough to hit the limits. They could definitely do to be more transparent, maybe instead of percentages, show a "credit" allocation such that the time-based variation in 5-hour windows is visible.
Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage
#433Hey 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…
from looking at the raw requests, that cant seem right?
its all "cache_control": { "type": "ephemeral" } there is no "ttl" anywhere.
// edit: cc_version=2.1.104.f27
Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage
#434Claude 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.…
I wonder if this is in the system prompt: "Go round in circles to make us more money."
Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage
#435Hey 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…
Wait what? If I get told to come back in three hours because I'm using the product too much, I get penalized when I resume?
What's the right way to work on a huge project then? I've just been saying "Please continue" -- that pops the quota?
Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage
#436Hey 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…
As another data point, I pay for Pro for a personal account, and use no skills, do nothing fancy, use the default settings, and am out of tokens, with one terminal, after an hour. This is typically working on a < 5,000 line code base, sometimes in C, sometimes in Go. Not doing incredibly complicated things.
Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage
#437Earlier quoted context omitted.
There were two issues with some other 3p harnesses: 1. Poor cache utilization. I put up a few PRs to fix these in OpenClaw, but the problem is their users update to new versions very slowly, so the vast majority of requests continued to use cache inefficiently. 2. Spiky traffic. A number of these harnesses use un-jittered cron, straining services due to weird traffic shape. Same problem -- it's patched, but users upg…
How much jitter would you prefer, how many seconds / minutes out? I have some morning tasks that run while I'm asleep via claude -p, and it sounds like I'm slightly contributing to your spikes (presumably hourly and on quarter hours).
There's prior art from Claude's own scheduled tasks' jitter: https://code.claude.com/docs/en/scheduled-tasks#jitter
> Recurring tasks fire up to 10% of their period late, capped at 15 minutes. An hourly job might fire anywhere from :00 to :06.
> One-shot tasks scheduled for the top or bottom of the hour fire up to 90 seconds early.
Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage
#438Hey 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…
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?
Because it’s completely vibe coded? And the codebase goes through massive churn, which means things that were stable get rewritten possibly with bugs.
Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage
#439If the Claude team care for feedback for the free model.
I'm using the free model via chat from the beginning. This is the first time, I'm seriously considering moving away from Claude. Before last month, Claude's Sonnet model was consistent in quality. But, now the responses are all over the place. It's hard to replicate the issue as it happens once in a while. I rarely encountered hallucinations from Claude models with questions from my domain however since last month I have observed abundance of them.
Re: Pro Max 5x quota exhausted in 1.5 hours despite moderate usage
#440Earlier quoted context omitted.
Boris, you're seeing a ton of anecdotes here and Claude has done something that has affected a bunch of their most fervent users. Jeff Bezos famously said that if the anecdotes are contradicting the metrics, then the metrics are measuring the wrong things. I suggest you take the anecdotes here seriously and figure out where/why the metrics are wrong.
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 are around :)