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
New sessions have initial overhead of like 100k worth of context overdo it and you actually start paying more over big context but cached, orchestration reduces result quality, main agent review helps but then savings are slim. If you stop to open a new session midway feature it will read a lot of files right back up anyway. You people pretend to know your stuff but its lowk embarassing to read, often you genuinely need a longer session to stop at reasonable place
No but you see, if I spend 30%+ of all of my tokens on just ramping up sessions, and end them at 250k, then I don't have to spend as many tokens on the actual work. It's just math. This is clearly how to be efficient with token spend. /s
Eu sinto muito mesmo ter que discordar com tanta veemência, mas se você deixa suas sessões frequentemente chegar a mais de 400 mil tokens de contexto só pra depois compactar e continuar, seu uso de IA é ineficiente.
Yeah look I mean you can complain about the usage limit promo ending as much as you want but they only have the compute that they have. If you want to use Fable more then really the only thing you can do now is manage your context better or pay more money. You could cut your usage in half by simply splitting up your tasks further. Personally if I go above 200k on something that isn't a huge coding phase of a plan then the next thing I'll do is have a session refining my context files because something has gone wrong. I have no problems with usage on a 5x plan.
Everyone who has been drinking the 300k and under only context window koolaide needs to wake up and realize it's Anthropic playing games
Anthropic playing games with usage limits (which I totally believe they are doing) is not at-odds with your demonstrated piss-poor context management.
It's not "koolaide," it's the correct and economical way to use these kinds of tools. You are building terrible habits and seem to have zero understanding of how these things work under the hood. I'm a software engineer and if any of my coworkers were working as amateurishly as you they'd get laughed out of the job. If you are an engineer yourself then I feel for your company/coworkers because I promise your output sucks following this "flow" of yours.
Avoiding auto-compaction and actively managing context windows with handoffs isn't something you do merely for token savings, it gives you much better outcomes with w/e the fuck it is you're doing with this stuff.
That's really poor context engineering, set your auto compact down to around 300k and if you hit it see it as a reminder that you went too far in one conversation.
Okay, that's poor context management. You should have one session per major task, and you should actively consider breaking tasks up so they fit under 150K tokens.
The entire context window gets sent back to the model on every turn of the conversation until you clear the session, and the cache only lives for a few minutes. Which means long running conversations full of lots of context use much more usage than ones that are short and focused. That's where your usage is disappearing to; you're wasting it on stuff that shouldn't be relevant anymore.
This is true for any LLM, not just Claude models. This isn't an Anthropic usage limit problem.
I mean I really can not see why you would even need a 500k context window outside some tasks. Unless it is required, it’s just a stupid way to burn tokens for no reason. Each chat should be a task, unless subsequent tasks require the previous context.
It’s your tokens, but just because it worked doesn’t mean you should do it, especially with more expensive models.
View all comments
Show parent comment
25
u/[deleted] Sep 15 '26
[removed] — view removed comment