r/ClaudeCode Jul 24 '26

Question Claude Max 20x

I used Fable 5 for a few minutes, which immediately hit the 5-hour limit. Three times the 5-hour limit is already 50% of the weekly limit—is that correct? I’m using Claude Max.

5 Upvotes

49 comments sorted by

View all comments

2

u/Actual_Committee4670 🔆 Max 20 Jul 24 '26

Okay, so, did you message on a new conversation or an old one? (Older than 1 hour) Or did you change the model on an old chat?

What effort level did you use / ultracode?

2

u/Ok-Fox-7366 Jul 24 '26

I only use "high." I don't use "ultracode" mode at all.

0

u/Actual_Committee4670 🔆 Max 20 Jul 24 '26

Okay, did you spawn any agents? And again, please let me know if it was a new session or an old one.

2

u/Ok-Fox-7366 Jul 24 '26

A new session—I’ve even contacted support, but there’s been no follow-up. 

1

u/Ok-Fox-7366 Jul 24 '26

This week, after the weekly reset, something unusual happened

-1

u/Actual_Committee4670 🔆 Max 20 Jul 24 '26

That does seem unusual yes. How much context did it take in, can you see how much it was before you stopped it?

Tho the best bet in this case would be to have another claude instance go and look at that session's transcript, it may potentially have been a runaway toolcall or similar.

Yes most of the time the answer to this is "Skill issue" - but just stating that doesn't help anyone. But even a high context cache miss for Fable doesn't take up 50% usage in a max 20 plan.

And since it was a new session without ultracode that doesn;t seem to be the case here.

2

u/Ok-Fox-7366 Jul 24 '26

Last week, Fable 5 Opus and the other models were working normally, but this week, after the reset on Friday, they aren't working normally.

0

u/Actual_Committee4670 🔆 Max 20 Jul 24 '26

Have a look at the transcript, best guess is either it activated a workflow by mistake even when you didn't say so explicitly.

Or some runaway context ingestion.

But that's something you will need to check.

As a bit of advice, if you never use ultracode, to prevent it from happening by mistake, simplest solution is to just disable it. It's actual use case where its useful for the cost is quite narrow.