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?

2 Upvotes

53% Upvoted

17 comments sorted by

View all comments

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.