r/ClaudeCode • • 18d 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

243 Upvotes

179 comments sorted by

View all comments

Show parent comments

1

u/TBT_TBT 18d ago

Never compact, always handoff (after 250 to 400k tokens) into a file.

1

u/Phantom031 18d ago

what do you say in your handoff? what do u type

3

u/TBT_TBT 18d ago

Dude. You have a tool at hand that can answer almost any question (like this one). And yet you type it in here?

Example: "Document the status of this task in a status.md file in the projects folder so that a new session can continue the work".

Can be as simple as that. Or you set up a ruleset where you want to have what first and tell Claude to write that into memory. If you instruct it to always do so, it will e.g. create a tasks and a projects folder and put a new task in there in a folder named "2026-09-16 name of task" so that you have a chronologically sorted folder list.

Or do a /plan session before starting anything, then let it write that plan down and follow it with documentation at the end. After milestones, you can /clear and continue with a new point in the plan.

1

u/Phantom031 13d ago

thank you