> But it's getting so unstable. It generates code, I see it doing that, and then it throws the code away and gives me the previous version of something 1:1 as a new version.

I've had the same experience. Totally unreliable.

▲

actsasbuffoon 5 days ago | parent | next [-]

I regularly have this happen:

1. Ask Claude to fix something

2. It fails to fix the issue

3. I tell it that the fix didn’t work

4. It reverts its failed fix and tells me everything is working now.

This is like finding a decapitated body, trying to bring it back to life by smooshing the severed head against the neck, realizing that didn’t bring them back to life, dropping the head back on the ground, and saying, “There; I’ve saved them now.”

	▲	johnisgood 5 days ago \| parent [-]
		Gosh, can't we get back to Sonnet 3.5 or whichever was the version around a year ago? It worked so well for me.

▲

jononor 5 days ago | parent | prev [-]

This happens to me a lot. Almost once per session now, and not even when things are complicated. The model also thinks it has done the changes. So it seems a UI/state bug, not on the model side.

	▲	mh- 5 days ago \| parent [-]
		I believe this is an issue with tool calling, similar to my complaint above about it refusing to use its search tool (or claiming that it did when I can see that it did not.)