Memory Across Multiple Session

Hello everyone,

Could anyone offer guidance on how to configure Cursor so it retains memory across multiple sessions? I often spend hours fixing a specific part of my application. I try to committ often, when I remember. However, once I move on to a new task, that same section of code sometimes reverts to an unintended state, and I have to prompt Cursor again to address it—essentially repeating the same work. The problem I have with this is that I tell it, we just fixed it can you follow the next step but its in a different session.

It would be incredibly helpful if Cursor could preserve a record of previous fixes and missteps across sessions. Having that persistent context would not only boost my productivity but also make the process more creative and robust. If anyone has insights or suggestions—perhaps a feature or setting I’m missing—I would greatly appreciate it. Thank you!

Hey, we’ve recently added the ability to @ old composer sessions into a new one, so you can restore any lost context from old sessions.

This may have limitations on how much information it can learn from very long or context-full conversations, but give it a try and let us know how you get on!