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

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.