Addressing 2) first: That's good, I totally misunderstood then, and guess I'll need to try it to understand what's new since I thought that kind of tabbing had been there a while.
Back to 1): The type of bug I see most often is where conversation history seems incomplete, and I have trouble rolling back to or even finding a previous point that I am certain existed.
Git shares some features but I think Git was not made for the type of conversational rapid-prototyping LLMs enable. I don't want to be making commits every edit in some kind of parallel-git-state. Cursor's rollback and branching conversations make it easy to backup if a given chat goes down the wrong path. Reapply is tedious since it has to be done one edit at a time - would be nice if you could roll-forward.
I haven't put much thought into what else would be useful, but in general the most value I get from Cursor is simplifying the complex state of branching conversations.
FWIW, my workflow with git is to stage changes I want to keep after every prompt. Then I can discard changes in the working area after a bad prompt or stage individual changes before discarding from the working area. Works really nice for me.
Back to 1): The type of bug I see most often is where conversation history seems incomplete, and I have trouble rolling back to or even finding a previous point that I am certain existed.
Git shares some features but I think Git was not made for the type of conversational rapid-prototyping LLMs enable. I don't want to be making commits every edit in some kind of parallel-git-state. Cursor's rollback and branching conversations make it easy to backup if a given chat goes down the wrong path. Reapply is tedious since it has to be done one edit at a time - would be nice if you could roll-forward.
I haven't put much thought into what else would be useful, but in general the most value I get from Cursor is simplifying the complex state of branching conversations.