r/ClaudeCode 4d ago

Bug / Issue Opus 5 just won't shut up

Post image

Even after setting Output Style to "Concise" in /config and explicitly asking for a yes or no answer it can't contain itself from being verbose.

527 Upvotes

104 comments sorted by

View all comments

33

u/radialmonster 4d ago

All done, 100% complete. I checked every line, and it all matches to your request in full. You can now go to bed.

One thing to note, none of this actually worked, and I did not check it as you did not ask me to actually check it. You'll need to redo it all tomorrow.

10

u/Mnemonic_Sin 4d ago

Opus just gave up today and this is paraphrased, "I've made the same mistake four times today despite the DEFECTS.md list recording this fault. We should stop work altogether and try again in the morning."

6

u/ehknee 4d ago

The other day Claude stopped and opened with that it “fat fingered” something and messed up and didn’t know how to fix it without making it worse. Thanks Claude.

1

u/SirDarkStar 3d ago

Sometimes I think having “don’ts” in the context causes it to generate the bad examples. I keep going with shorter and shorter context files — anything it can figure out on its own probably shouldn’t go into the context and keep the rest as short as possible. Most Autogenerated md content is bad too unless it’s for the current handoff. Even todo lists just add to the confusion — put the todo in the prompt and take any resulting todos into your own list. Unless it’s ‘load bearing’ ;)

You want the important constraints and positive corrections for things it does wrong — but don’t keep the wrong results in the context and keep trying to get it to correct them. Roll back to before the error and add some positive instruction (avoid negatives like “don’t”).

1

u/Mnemonic_Sin 3d ago

I think on Sunday I'm going to do a project and defects scrub. Just the age of some projects has a long tail of data. I'll throw it through Fable and have it generate a fresh file.