hi, could you send a recording of persistence not working?
I will try to record, but it usually happens unexpectedly
does this happen more often when you have a lot of composer chats? around how long would you estimate each of your composers are on average?
all of my chats are long, 15- 20 back and forths… I haven’t tried to track it. I have 5 entries now, and they are pretty short, maybe 2-4 rounds
another issue is that it often will output large chunks of files, like 100-200 LOC… no matter how many times in my .cursorrules I try to prevent it…
“Whenever generating code, always automatically apply it to the relevant location and try to minimize the amount of code that you put in the chat window”
I editted a previous question - just want to change to another model. and it drop all message from there to forth, leaving only that editted question left. this is really bad
i’ll say it until its addressed
cursor conversation rules work at best 50% of the time
I
1 Like
Please fix the Composer History issue. My suggestion is to have a setting to allow an automatic backup to be made in some project folder. In case the Composer History is lost (it has happened to me 3 times), there would be a way to restore it.
2 Likes
I’m really interested in this history issue. Not trusting my logs will persist really gets in the way moving quickly with Cursor and building apps to the level of complexity I want.
I’ve been working with a small team on a tool (SpecStory Cursor Extension) that makes it possible to save Composer history. We export the history as Markdown, and also display it in a browser view with a shareable URL. This all towards the goal of being able to work freely with the chat & Composer — to make use of this both for myself, and for maintaining a useful context.
(More here: Built a Cursor Extension to save and share chat and composer history)