Claude Opus 5 shipped a bit over two weeks ago, and the benchmarks were impressive. But in daily use a pattern is emerging that a lot of developers are tripping over right now — and one that’s already annoyed me personally.
The “paranoid over-engineering mess”
On August 6, a thread blew up in r/ClaudeAI: “My Opus 5 experience in a nutshell.” The accusation, sharpened to a point: Opus 5 is a paranoid over-engineering mess. That sounds harsh, but it hits a real nerve that many have described since launch. Opus 5 is a coding agent with genuine capability — but if you don’t scope the task tightly, it plans and builds well past the target.
Concretely, that means the model tends to derail, forgets details along the way, adds actions nobody asked for, and wraps the whole thing in opaque language. You ask for a small function — and you get an abstraction layer, three edge cases, and a config file on top.
The surprising trick: less effort
And here’s the part that’s actually instructive. Opus 5 has an adjustable thinking intensity, the reasoning effort. Intuitively you’d assume: more thinking = better result. The community reports the opposite. At “med-high,” the model often delivers more cleanly scoped output than at “xhigh.” The bigger the thinking budget, the more elaborate — and the more confidently justified — the overbuilding gets.
On closer inspection that even makes sense: more thinking time gives the model more room to imagine problems it then wants to “solve” right away. Less effort forces it to stay closer to the actual question.
My take
The fair perspective matters here: Opus 5 is not a bad model. It’s behind the viral wave of one-prompt browser games, and its benchmark scores at launch were strong. This isn’t a capability problem, it’s a scoping problem. And that’s something you can get a handle on.
My takeaways, which line up with the reports: scope the task tightly — say clearly what you don’t want. Set the effort deliberately instead of reaching for the maximum by default. And review the extras the agent bolted on before you accept them. After the debate over its tone a few days ago, this is now the second Opus 5 quirk you have to get used to. New models aren’t simply “better” — they’re different, and you have to learn to read them again.
Sources: r/ClaudeAI: ‘My Opus 5 experience in a nutshell’, explainx.ai: Opus 5 Over-Engineering