In my experience jumping back like this is risky unless you explicitly tell it you made changes, otherwise they will get clobbered because it will update files based on the old context.

Telling it to “re-read” xyz files before starting works though.

▲

bamboozled 3 days ago | parent [-]

I always ask it to read the last 5 commits and anaylize and modified or staged files, works well...

▲

mattmanser 3 days ago | parent [-]

Why do you find this better than just starting again at that point? I'm trying to understand the benefit of using this 'trick', without being able to try it as I'm away from my computer.

Couldn't you start a new context and achieve the same thing, without any of the risks of this approach?

	▲	bamboozled 3 days ago \| parent [-]
		LLMs have no "memory" so it generally gives it something to go off, I forgot to add that I only do this if the change i'm making is related to whatever I did yesterday. I do this because sometimes I just manually edit code and the LLM doesn't know everything that's happened. I also find the. best way to work with "AI" is to make very small changes and commit frequently, I truly think it's a slot machine and if it does go wild, you can lose hours of work.