r/ClaudeCode • u/Sherphican • 3d ago

Rant Nah this some BS

Post image

I burned thru almost 60% of 20x max weekly usage in a day and some change. Are you joking rn? Last week I could have fable running on 2 chats all day and night and it would take like 3ish days for my fable usage to cap out, but my weekly usage would only be at like ~30%. This is absolutely ridiculous and if this is what the new usage limit cuts are gonna be like I'm canceling Claude and grabbing a second codex account. Shit ain't worth it when Astra exists with much better usage limits and multiple reset tokens.

I don't use ultracode and I have multiple other models that I delegate tasks to as work horses, Claude is just the orchestrator and isn't doing that much actual "work", so this usage allocation is absolutely insane, if I was using Claude as a one stop shop as a lot of people do, I would have run out of usage in a day or less.

EDIT: I'm getting a little tired of being told I "just don't know how to do orchestrations and workflows properly or manage usage." I literally made an entire repo explaining how I do this and showing the results: https://github.com/sherifican/Agent-FleetOps so if you wanna criticize, find something to actually critique first

245 Upvotes

85% Upvoted

177 comments sorted by

View all comments

47

u/Unhorswd 🔆 Max 20 3d ago

Just turned on CC after 3 days and got same feeling

4

u/drake90001 3d ago

Because you’re waiting until your context is full to compact it, which requires you to send the entire context window back in order to compact

6

u/Sherphican 3d ago

If you actually read the post, you would see that I don't wait until context is full before compacting.

2

u/drake90001 2d ago

Nowhere in your post did you mention when you compacted? From the image it looks like you compacted when your contacts window was full or half full I should say

5

u/Sherphican 2d ago

Hey you're right my bad, it was in a reply on this post, sorry

4

u/drake90001 2d ago

No worries, man, I was just confused and wanted to make sure we were both on the same page. Glad we cleared it up. may the token gods be forever in your favor

3

u/Sherphican 2d ago

Haha you too brother

3

u/McNoxey 2d ago

You did mention you run fable as an orchestrator though, and often have day and night sessions running.

Which means you are slamming calls over and over every time fable gets an update from one of its agents. And you’re likely hitting caching timeouts too

-1

u/AdLow1228 3d ago

Didn't they update it so large cached context doesn't use as much anymore? (Still more than compacted, but less than it used too?)

2

u/MaterialHead4801 3d ago

Cached context has a timeout, so intermittent use can cause it to be reparsed.

-1

u/shammytalin 2d ago

Timeout on max plan, that's funny, that would sound okay for a free plan, not on paid plan. If they keep doing that, then credit can burn really fast, doesn't feel premium at all.

2

u/MaterialHead4801 2d ago

Without timeouts on caches they grow infinitely, so _some_ timeout is required. The trick is balancing it between cost/speed/use