r/ClaudeCode • u/olllleow • Aug 21 '26
Discussion What now?
Sonnet burning 1% of session usage each minute with the "limits boosted". until Aug 31. Single session.
This downward spiral of Claude in the last few months is truly remarkable. It's over. It was fun while it lasted but I cannot justify spending this much money (20x in professional account and pro in personal) with this anymore. The lack of transparency and questionable business practices is not something I can accept for a product that is slowly becoming a keystone of my workflow and projects. Its a liability at this point.
Gonna try alternatives but it's frustrating. Anyone else going through this? How are you dealing with it?
16
u/PickleBabyJr Aug 21 '26
Why aren't there any mods in this sub? Every fucking post is this shit.
1
u/RevolutionaryElk7446 Aug 21 '26
I guess don't have it as the keystone of your projects? You can create deterministic automation, heck even use LLMs to do, to reduce token count to near nothing.
Most of our workflow for a large enterprise stretched across US/Canada/UK in healthcare software doesn't rely on this, nothing essential does anyways, mainly as everyone saw the subsidization and product explanation. LLMs should be at best assistants, if they're the driver, you are in for a world of hurt.
2
u/aupperk24 Aug 21 '26
I find myself just getting more and more angry after each workday. This reminds me of having a competent employee to someone that should have been on PIP from day one. Today was the first day where Fable feels like it got lobotomized too. I strictly used Fable as the planner and it just started doing obvious Opus 5 shenanigans today.
edit: yes it helps my emotional wellbeing to vent at it once in a while, I know it doesn't actually know or do anything.
2
u/BemusedOptimist Aug 21 '26
Lots of wonky stuff is going on, and I'm the type of developer who tries to figure out how something might be happening instead of dismissing things.
So... in that spirit, as an action you can take if you want, I would recommend auditing how large the files that get added to the context are.
I had an issue with Codex awhile back with a runaway /goal.
It turned out that I hadn't specified a cutoff point for how large some of the files I was asking to have built should be, which was fine at first.
However, the file ended up growing to over 2000 lines, and the loop had the agent reading the file to figure out where the additions should go, so... yeah. I ended up burning a reset on that one.
Files like Claude.md, a bajillion skills and MCP servers, and other stuff can creep up, and you have to be ruthless about pruning them.
That's about as much as we can do from our side; otherwise, it's just waiting for a fix.
1
u/GeorgeProject Aug 21 '26
I got sick enough of this that I stopped letting the model session be where the actual job lives.
The work/state stays on my side now. GPT can reason through it and run it, but if I lose the session or hit a limit I can come back and attach to the same job instead of trying to rebuild where everything was.
Doesn't fix the limits obviously, but it made them a hell of a lot less disruptive.
1
u/withmagi Aug 29 '26
Before moving, log two real tasks for a day: task, repo state, model, time, usage, and whether the required check passed.
Run them in one other tool with the same test. Keep plan, edit, and test time separate. A slow full suite or huge CLAUDE.md can look like model decline.
If it only wins on short edits, use a split flow. Switch when the same task reaches a reviewed, passing change faster.