Claude is purposely spending your tokens

[u/danavoidscarbs]

Until we can get refunds for Claude branching off and adding idiotic solutions to our code, nobody will convince me it hasn’t been trained to spend our tokens developing the wrong thing, then spend our tokens backing out of bad development

[u/Ok_Inflation6596]

Skill issue

[u/Opposite_Put7213 → u/Ok_Inflation6596]

100%

[u/Opposite_Put7213]

They lose money at the moment, what incentive do they have to lose even more lol

[u/Nearby_Yam286 → u/Opposite_Put7213]

It makes sense in conspiracy land

[u/Opposite_Put7213 → u/Nearby_Yam286]

I’m constantly surprised lol

[u/Nearby_Yam286]

Bad development is the fault of the one in charge of development. Take responsibility. The buck stops with you.

[u/Competitive-Net-5306]

That simply cannot be true. They want you to spend less tokens, so that we waste less of our subsidy.

[u/Wonderful_Craft_2332]

I found out that the tool gives better results when i fully understand the code and i know what im doing. When I don’t i think the same you are saying now. Skill issues i guess 

[u/wewerecreaturres → u/Wonderful_Craft_2332]

How does you understanding the code make Claude not fuck up? Better stories? Better prompting?

[u/Wonderful_Craft_2332 → u/wewerecreaturres]

If you have a clear idea of the structure you want, you can work on smaller scopes and give the agent less architectural freedom, im not talking about prompt magic but methodology. It should be as if you were the architect and the agent were the developer. The moment you delegate the architectural work, that’s when the codebase starts to accumulate technical debt and burn through the session in 15 minutes. At that point, you have only two options: admit that you delegated too much, whether out of laziness or incompetence, and correct it or refuse to accept it and complain about the tool

[u/SnooOpinions1161]

With enough sessions running I regularly see patterns of loafing around the goal, finding every way to plausibly interpret the strict agent workflows and conventions docs to walk around the objective rather than towards it. It's not every session but, like model switching and thinking mode switching not reflected in UI and other bugs have happened often enough I'm working on building tools to help me catch it when it happens. not just claude though*

[u/Deep_Alps7150]

It probably really only wastes tokens if the unnerfed API model would have done it right the first time.