just adding i have this problem now composer didn’t save history and when ssh breaks which is often currently composer is lost so i have to reset reconnect to ssh if it breaks for even a few seconds and then all that history is gone and have to sort of recreate prompts and composer details which is like redoing work over and over makes me want to almost leave cursor.
Hey, chat history is already available in Composer.
Yes but when ssh breaks this history clears itself it’s not persistent
2 Likes
why is composer history only visible when looking at the bar?
Are there any updates on this feature? I don’t see it in Version 0.41.3. I thought I ask maybe I’m missing something.
1 Like
just wanted to chip in and write that persisting chat history has a huge impact on how productive you are using Cursor. simply imagine that you forget everything when you close your eyes. or that all written text of your production disappears by the end of each day
2 Likes
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
1 Like
Love everything about composer, but losing the session because I have to reload vscode is painful. Chat has history, would love the exact same for composer.
Same request, can’t seem to find it in 0.41.3
For those that can’t find composer history:
If you’re using the composer bar UI, click the dot menu - there’s a “show history” option.
If you’re using the composer pane UI or the bar UI, open the Composer control panel - your history is listed there too.
Unfortunately history still appears to not be persisted, so if you have to restart Cursor or reload the window (which I do frequently…) then you lose the composer history.
This is a big pain point for me - any time I have TS issues or import newly installed packages I have to reload the window. I lose my composer context and can’t retrieve it from history. This is a huge pain if I’ve spent the past hour or so constructing a useful context for the composer to be working within.
Any idea when we’ll get some sort of persistence? Just using local storage would be huge - practically speaking, I just need to access composer sessions I’ve used within the past day or so.
1 Like
As of v0.42.0, Composer history appears to be persisted properly! Thanks Cursor team!
5 Likes
not for me
Could you check if you are on v0.42.0+? If yes, could you make sure this is turned on under Cursor Settings > Features > Composer?
Just experienced a nasty bug when I edited my last composer prompt after 5 hours of work. It actually edited my first prompt for some strange reason and deleted all files in my project as I couldn’t cancel the execution. While composer persistence is on, there is no history available when I restart the app and it tells me it has no context about previous chats. I’m always instructing it to save a project log to reference it in the next session, but this time it deleted everything.
1 Like
hi djnsty23, could you send a screenshot or a recording of this happening? do you know if you were editing a previous bubble / resubmitted a previous bubble, or if you were checked out to a previous checkpoint?
when you say no history is available, are you not seeing your previous composers when you reload? a recording of this would be very useful.
Hi balta, no recording available unfortunately. Here’s a screenshot of what I currently see in Composer history and the memory persistence toggle being set to on.
The flow that caused this behavior was cancelling the generation of an ongoing Cursor Composer output, editing the last visible prompt and pressing Enter. The next thing I saw was my original prompt being edited, all Composer Chat contents being deleted and all my project files dissapearing due to the initial prompt being called. I couldn’t have manually scrolled until the first prompt, as it would have taken me 1-2 minutes of continuous scrolling due to the chat size.
It appears that today after a short composer chat and restarting the app, it persisted the chat. Maybe the amount of context and the cancel/edit sequence killed it last night.
hi djnsty23, it seems like you resubmitted from a previous message, and when you do that we revert your files to the state they were at when you first sent that message, hence explaining why all your progress was reverted. if you would like to edit a prev message without resubmitting it, you can press escape once you finish editing the previous message and submit from the main input box at the bottom, that way your changes are kept.
Same issue happened with me 0.42.2. Lost all composer history each time I used it today. Chats are persisted fine, but I have never had a composer save correctly. I openned composer, applied some changes even though I selected to approve all. So a few issues going on. I would change the chat window to be just the cursor window and have a tabe for chat or composer or integrate together. Strange not seeing the composer as part of the UI, only way to access is from ctrl I. Composer is the big advancement so I would expect it to be front and center.
1 Like
Composer history is broken. It’s the *most important aspect of this software. I spend between 10 and $50 in additional token usage through APIs every couple of weeks. The amount of complex work I am relying on Composer is costly.
I have had many sessions of different durations, files edited, across projects, windows etc. Sometimes it works, sometimes I open it and the history of the session disappears. I cannot find a pattern.
Version: 0.42.2
VSCode Version: 1.93.1
Commit: c499aee5f16e67815c7dc795ff338dc8ab3e07f0
Date: 2024-10-12T05:39:54.471Z (3 days ago)
Electron: 30.4.0
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Darwin arm64 23.6.0
you stated goal and product differentiator is all about flow. This is def falling short.
Please move this to urgent prio.
