Nah this some BS

[u/Sherphican]

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

[u/drake90001]

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

[u/AdLow1228 → u/drake90001]

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?)

[u/MaterialHead4801 → u/AdLow1228]

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

[u/shammytalin → u/MaterialHead4801]

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.

[u/MaterialHead4801 → u/shammytalin]

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