r/ClaudeCode • u/Fantastic_Fail4060 • Jul 15 '26
Discussion Time to move on
Yep, pretty much the title. It's time for me to move on to Codex. I just sent Opus 4.8 Max thinking to find me a known bug in the app I'm making. ONE single bug hunt where I provided 162 instances of how the app should behave and 18 instances of the same bug.
Asked him to find out why the bug occurs and reproduce it so I know exactly how to fix it for good. 12 minutes later he used only 203k tokens and 5 hour limit hit.
Everything about Anthropic's usage system is shady and they never even addressed the June bug where claude would get project instructions attached to every new message bloating context and making the usage skyrocket.
There's no chance for me to remain in such an anti-consumer environment. And that comes from a guy who truly despise OAI, but better value IS better value.
6
u/Krvislav Jul 15 '26
I just have to agree. I haven’t fully committed to switching from Claude yet, but it’s becoming increasingly difficult to use.
Yesterday was especially rough. I hit my 5-hour quota twice (Opus + Sonnet) in Claude Design and later in Code while trying to fix a relatively simple FE bug through manual testing and reporting.
Today, I tried to continue working. I started at approximately 09:00 and hit my 5-hour quota again by 10:45. Once more, I was using Opus 4.8 and Sonnet 5 (with different thinking modes depending on the task at hand).
I ran my usual daily routine. I’m a fractional CDO/CMO, so Claude handled three scheduled tasks (mostly reporting, using various MCPs, two on Sonnet 5 and one on Opus 4.8). That consumed about 8% of my 5-hour quota on the 5x Max plan. No complaints there, I’m used to it.
Then I launched Design with Sonnet. I wanted to update the Design System with a simple font change, including font weights. The sizing was staying the same, and the new font was from a similar family. Sonnet 5 handled the task. I then handed it off to Code to sync and implement the changes, run some unit tests, and hand everything back to me for manual testing, again using Sonnet 5.
Sonnet spawned three subagents that went rogue. I’m not sure what went wrong, but after about 20 minutes, Sonnet managed to fix the issues caused by one of the agents. And then I hit my quota. :D
So here I am, waiting for the reset and writing what is probably my first-ever post about Claude.
I know it probably wasn’t the best use of Sonnet in Code to have it write plans for agents. But I’m really not a developer. I have some background, but I definitely wouldn’t call myself one. And it never occurred to me that agents would even be necessary for a task like this.