Do you not have unit tests, or how does it introduce regressions? You can tell it how to run the test suite in CLAUDE.md

▲

quaheezle 3 hours ago | parent | next [-]

Opus 5 tries to modify the unit tests as a cover to its own regressions - thinking its own logic is correct and the test must be wrongly specified

▲

jvuygbbkuurx 2 hours ago | parent [-]

I found it eagerly reversing existing product decisions like changing a user given date into created date, since it thought creating something that is in the past is incorrect. This was not even related to the task at hand at all. I noticed this kind of stuff happens more with ultracode for some reason.

	▲	grim_io 2 hours ago \| parent [-]
		Any subagents-based workflow is prone to this, because of the fragmented context(by design).

▲

Aldipower 3 hours ago | parent | prev | next [-]

I detect the regression already in planning with Opus 5, so I do not let Opus 5 implement anything. But it is a waste of time and tokens! Does planning with Opus 5 works out for you?

▲

cbg0 2 hours ago | parent [-]

It sounds like you just need to correct the plan it lays out to avoid the regression? I'm just looking to debug with you, not defending the model. I've mostly used Opus 5 for code reviews & bugfixes.

▲

Aldipower 2 hours ago | parent [-]

Yeah fine. I mean my plan wasn't to difficult. For example this morning I started with Opus 5 to tackle a problem. During planning at some point Opus 5 detected _8_ regressions in it's own planning, after I directed it towards those potential regressions. So, in this very moment now, Fable 5 implements code already and the planning before with Fable, done with the same instructions, was flawless and quick. And I am sure, Opus 4.8 would be flawless either. Same harness, same claude.md, etc..

▲

cbg0 2 hours ago | parent [-]

Do you think it might be overthinking? Try it on medium effort.

	▲	Aldipower 2 hours ago \| parent [-]
		Probably, I ran it on xhigh. Worth a try.

▲

simiones 3 hours ago | parent | prev [-]

It is a well known fact that projects with unit tests never have regressions.

▲

cbg0 2 hours ago | parent | next [-]

I don't understand the need for the snarky comment, LLMs can run the test suite and avoid regressions.

	▲	simiones 2 hours ago \| parent [-]
		A change can introduce regressions in any large project even if 100% of unit tests pass. Unit tests test individual units, regressions can happen at many levels. Especially if we treat performance degradations as regressions.

▲

cyphar 2 hours ago | parent | prev [-]

[dead]