Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

github.com

Post reply on HN
Print view View original

501–510 of 695 posts

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

#501

Post by shamcleren »

toddmorey wrote: post #326
reenorap wrote: post #290

Earlier 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.

On the subject of metrics, better user-facing metrics to understand and debug usage patterns would be a great addition. I'd love an easier way to understand the ave cost incurred by a specific skill, for example. (If I'm missing something obvious, let me know.) Baking deeper analytics into CC would be helpful... similar to ccusage perhaps: https://github.com/ryoppippi/ccusage

[flagged]

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

#502

Post by otterley »

xyzzy_plugh wrote: post #498
otterley wrote: post #473

Earlier quoted context omitted.

Did you talk to them about purchasing an SLA? If so, what did they say?

I feel like you aren't really understanding what a Service-level Agreement actually is in practice. It's not a piece of paper with a specific number of nines and an associated price tag. They can be and often are very complicated documents that take multiple rounds of redlining to arrive at something both parties agree to. If zero data-retention was non-negotiable for the customer, it's totally possible that the nego…

As both an attorney and SRE, I understand what an SLA is. And you can absolutely get an SLA when you buy cloud services from many vendors, including AWS. Some vendors provide it at all price points; others include it at higher service tiers, without complex negotiations needed at all. And, yes, if it’s not on the menu, you may need to negotiate one. But you can’t conclusively say “they don’t offer one” unless you’ve actually gone to the company and asked.

https://aws.amazon.com/legal/service-level-agreements/

https://trailhead.salesforce.com/content/learn/modules/slack...

https://support.atlassian.com/subscriptions-and-billing/docs...

Before you casually accuse someone of not knowing what they’re talking about, first make sure you’re on firm ground yourself.

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

#503

Post by g4cg54g54 »

j-pb wrote: post #347
bcherny wrote: post #210

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…

The /clear nudge isn't a solution though. Compacting or clearing just means rebuilding context until Claude is actually productive again. The cost comes either way. I get that 1M context windows cost more than the flat per-token price reflects, because attention scales with context length, but the answer to that is honest pricing or not offering it. Not annoying UX nudges. What’s actually indefensible is that Claude…

currently "clear makes it worse" https://github.com/anthropics/claude-code/issues/47098 + https://github.com/anthropics/claude-code/issues/47107

launching with `CLAUDE_CODE_DISABLE_GIT_INSTRUCTIONS=1 claude "Hello"` till those are fixed seems to be th way

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

#504

Post by cdelsolar »

eurekin wrote: post #238
comboy wrote: post #200

Earlier quoted context omitted.

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.

what kinda gpus are you using?

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

#505

Post by anoazian »

bcherny wrote: post #210

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’ve seen the /clear command prompt and I found the verbiage to be a bit unclear. I think clarifying that the cache has expired and providing an understandable metric on the impact - ie “X% of your 5-hour window” for Pro/Mad users and details on token use for API users. A pop-up that requires explicit acknowledgment might also help, although that could be more of an annoyance to enterprise users.

One pattern I use frequently is using one high level design and implementation agent that I’ll use for multiple sessions and delegate implementation to lower level agents.

In this case it’d be helpful to have one of two options:

1. If Claude CLI could create an auto compaction of the conversation history before cache expiration. For example, if I’m beyond X minutes or Y prompts in a conversation and I’ve been inactive for a threshold it could auto-compact close to the expiration and provide that as an option on resume. 2. If I could configure cache expiration proactively and Anthropic could use S3 or a similar slow load mechanism to offload the cache for a longer period - possibly 24-72h.

I can appreciate that longer KV cache expiration would complicate capacity management and make inference traffic less fungible but I wouldn’t mind waiting seconds to minutes for it to load from a slower store to resume without quota hits.

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

#506

Post by taspeotis »

bcherny wrote: post #210

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…

Hi, thanks for Claude Code. I was wondering though if you'd considering adding a mode to make text green and characters come down from the top of the screen individually, like in The Matrix?

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

#507

Post by bpodgursky »

reenorap wrote: post #290
bcherny wrote: post #210

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…

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.

But the default 1M context window just rolled out a few weeks ago. If refreshing old sessions on 1M context windows is the problem, it's completely aligned with what Boris is saying.

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

#508

Post by ares623 »

losvedir wrote: post #245
SkyPuncher wrote: post #125

I skimmed the issue. No wonder Anthropic closes these tickets out without much action. That’s just a wall of AI garbage. Here’s what I’ve done to mostly fix my usage issues: * Turn on max thinking on every session. It save tokens overall because I’m not correcting it of having it waste energy on dead paths. * keep active sessions active. It seems like caches are expiring after ~5 minutes (especially during peak usage…

Haha. yeah my eyes glazed over immediately on the issue. Absolutely this was someone telling their Claude Code to investigate why they ran out of tokens and open the issue. Good chance it's not real or misdiagnosed. But it gives me some degree of schadenfreude to see it happening to the Claude Code repo.

I love the irony of it all. You reap what you sow.

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

#509

Post by egeozcan »

lelanthran wrote: post #476
egeozcan wrote: post #63

Earlier quoted context omitted.

But the problem is it used to not need that before. These days, you have to think twice before you summon a subagent.

> 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.

The value is all the things I built with it? Surely, this constant change deteriorates the experience but to be clear, here we're nitpicking on the experience, not questioning the value.

I also don't understand the "pro-AI" phrase. It's a tool, it brings results. I'm not pro-car when I drive to work.

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

#510

Post by zmmmmm »

Chaosvex wrote: post #202
SkyPuncher wrote: post #125

I skimmed the issue. No wonder Anthropic closes these tickets out without much action. That’s just a wall of AI garbage. Here’s what I’ve done to mostly fix my usage issues: * Turn on max thinking on every session. It save tokens overall because I’m not correcting it of having it waste energy on dead paths. * keep active sessions active. It seems like caches are expiring after ~5 minutes (especially during peak usage…

I love how some comments tell you to turn max thinking on and others tell you to turn thinking off entirely. Apparently, they both save tokens! Vibes, indeed.

Could be some logic to it - bad thinking is worse than no thinking and good thinking
Post reply on HN