Losing a 3 day long conversation with AI in the composer due to a forced restart is a major time suck. Basically have to start over. It would be great to have a way to select a previous conversation and pick back up where I left off. Checkpoints are great! But they don’t solve a lost conversation.
Thanks for the quick reply!
A couple of the ways that i’m losing the history:
-
Ai will start putting code in the chat window instead of updating the files. Typically I can only get this fixed if I reset the composer. When I reset, I lose all of the history of the previous conversation.
-
Several accidental resets when trying to minimize the composer panel. So misclicks.
Maybe a better way for me to phrase it would be “recover a composer.”
Is there currently a way to recover a conversation that I had in a composer after reset? As of now, the history only shows the newly reset composer.
Ah, okay, thanks for sharing, we need to fix that.
Awesome! Great job by the way.
- AMAZING PRODUCT!
- Lightning fast iteration from your team
- Great customer support.
I know things are changing quickly for you fellas, but y’all pulled it off! Just wanted to drop a note of enthusiasm. Great momentum!
1 Like
I don’t see a history option in composer. I’m using v0.41.3
Hey, you need to undock the panel, and then the history will become available. We definitely need to improve the UX.
Ah ok. I see it now, thanks @deanrie
It seems the composer history doesn’t survive a restart of the app though like the chat history does.
This would be save so much headache if it did.
1 Like
Bump this too, it’s the most important issue to fix.
I tried all possible paid LLMs and auto code generators this month and Cursor provides the most consistent results while iterating continuously. Until you close the app or reset the composer by mistake that is, which is unbelievably annoying and a true detractor in continuing my subsciption for now, as we all have to sleep sometimes :).
Good job in improving the app over time btw, I’ve tried it before and dropped out due to similar usability issues, as it tended to make code worse prior to Sonnet while requesting file changes. Please fix this issue and let us resume our passion projects when we need to.
Best regards,
Andy