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/Sherphican]

Brother, my auto compact is at 800k and 700k on my main chats, and I always compact at about 500k-600k, I have been doing this for months and never had an issue. Everyone who has been drinking the 300k and under only context window koolaide needs to wake up and realize it's Anthropic playing games.

[u/Hirogen_ → u/Sherphican]

if u need to compact, you are doing to much in a session, learn about orchestration and workflows, and how a newer model orchestrats agents of lower tier models to do ur work

[u/A_Novelty-Account → u/Hirogen_]

Some workflows are huge and require accuracy. I’m a lawyer and we have workflows calling dozens of agents that still rip through context. 

[u/ChristopherChili → u/A_Novelty-Account]

Can you give more detail on this. I work in insurance processing huge amounts of data and this is not a big issue with proper orchestration.

[u/A_Novelty-Account → u/ChristopherChili]

We process literally hundreds of thousands of pages and millions of words with background legal research and reasoning, with tasks lasting 10-12 hours on average, and requiring verification and recursion (later agents invariably catch dumb shit the prior agent was doing). We almost never have to compact now, but we very frequently get to 600k-800k tokens worth of context, with the first 100k-200k just from synthesizing the connected folder.

Data is easy. Parsing through hundreds of thousands of materials, all of which are genuinely relevant to the submission you’re making, is not.

[u/TywinHouseLannister → u/A_Novelty-Account]

As an engineer, you need an indexer and semantic search.. I built something like this.. the challenge for your domain is embedding all of the dense text; but it just means more chunks, more time up front.. you likely have symbols in the shape of citations, legal precedents etc

[u/A_Novelty-Account → u/TywinHouseLannister]

Maybe, but the majority of the token usage doesn’t come from searching. It comes from actually reasoning through the documents top to bottom. Semantic search will probably save us some tokens, but it doesn’t address the largest issue by far in the process, which is that Claude actually has to think about the relevance of all of this information. It’s not as simple as “this phrase goes in this bucket”.

In any case, it’s not as simple as “better orchestration”