Comment by sidrag22
14 hours ago
it just doesn't interact good with human beings, and it leaves incredibly strange long winded comments within code filled with session context that will likely not be relevant later on.
Also always seems to have this annoying tendency to leave "questions for you" at the bottom of every output.
Just a high friction human interaction type model, imo should never have even been released, regardless if it scores better on whatever tests, its a horrible experience and a downgrade over past models.
I have to wonder if everyone else is just running these models raw without any custom instructions. I hear all these things about voice and code comments and those are all things I've dealt with long ago via claude.md instructions, rules, and hooks. My claude can already respond in any "voice" I want and the quantity and quality of comments is within my control.
Currently, I'm using custom instructions plus reinjecting the writing cues Opus 5 ignores most frequently via a UserPromptSubmit hook. Again and again, I'm reminding the model what voice I want. Again and again, Opus 5 ignores it.
Opus 5 is remarkably bad at instruction following over long chats. I have to repeat “Be succint”, “talk like a friend or colleague would”, “no rambling” or some variant of it every few messages
it really just seems like people pump out that its on the end-user, and i just disagree. They have a walled garden around claude code and using their models within it, it should work instantly out of the box when going from an opus 4.8 to an opus 5.0 with the same workflows. it doesn't.
claude.md for all my projects are fairly tight, its seldom where im upset at anything a model does, and if it happens, its likely because i swapped provider and didn't realize i was failing to feed it proper context beforehand.
Opus 5.0 fails in different ways that I haven't had to deal with. Its insufferable with its choice of language, something I've never had to compensate for on any other model across any provider, so of course I have no preexisting rules for that, it also is sometimes just incredibly stubborn and just WONT finish, and requires several just "keep going" prompts.
This is much different than the issues people would make fun of users for in regards to treating models like slot machines and just pulling the lever over and over, this is more its stopping for no reason short of its task, and literally just needs to be told to continue? absurd.
Most of my workflows have reference material, with standards set, why opus 5.0 is the only model that fails to follow those standards and inserts wildly long weird code comments is not a failure on the end-user, thats the model failing. I can be MORE explicit of course, but i shouldnt need to be, this is supposed to be 5.0, its a downgrade. I went back to 4.8 and all these issues vanished.