Retaining Cursor UI historical topic chat history when renaming or moving to different repo workspace

Feature request for product/service

Cursor IDE

Describe the request

Not sure if anyone in the community has run into this situation when working on repos in Cursor IDE… but if I decide to rename or relocate my repo to different workspace, apparently I lost access to the old chats screens.

I asked Cursor chat in how to go about in restoring this old chat, it came up with some suggestions (see attached)

It doesn’t sound like it is a straight forward way to simply copy and paste the old chats transcripts because the chat UIs database are stored in specific folder location using SQLite DB and it’s old workspace unique name is already hardcoded in the db. It sounds though by changing manually by hands would create problems in terms of the usability for the historical UI chats

I wonder if it’s good idea to suggest this feature that would be useful to anyone that moves their repos around their local system so they don’t have mess things with UI chat migration themselves.

Screenshot / Screen Recording

Operating System (if it applies)

MacOS

Hey, thanks for the feature request. This is a known and frequently requested thing. Chat history is stored locally and tied to the workspace path, so when you rename or move the folder, Cursor treats it as a new workspace and the old chats disappear from the sidebar. The data is still on disk. The request to preserve or migrate history on rename or move is already logged, but I can’t share an ETA yet.

About the screenshot. Your chat is right that manually merging SQLite databases is risky. It’s easy to damage the store and end up with an empty or corrupted chat list. I wouldn’t recommend that.

Safe workaround. If you change the folder back to the original name and path it had when the chats were created, the old chats should show up in the sidebar again, since workspace identity is based on the path. Renaming back is reversible, unlike editing the DB by hand.

Related threads where you can add a vote or details to help raise priority:

Let me know if restoring the original path doesn’t work in your case.

Thanks @deanrie

I’m sure restore original path would certainly work I revert things back to normal..

But my rationale thinking for this is purely file/folder organisation purposes. I’m moving things around on my local machine; keeping things organized between my repos are either PoC or learning projects only vs my repos are for actual side-projects that would create tangible value for me greatly. When I find that my PoC items are showing potential in becoming product I’d inclined to use more on a day to day basis, I would move or ‘upgrade’ them out of my PoC workspaces into side project workspaces.

That’s where I’m coming from.

No matter. Thanks for the links though. In the meantime, I don’t see the need to restore the old chats. Fortunately, I have downloaded the plugin to ask cursor to persist context of chats on machine so that next tiime I create or expand chat I will make sure to save it so I can ask Cursor to pick up the context where we left and continue conversations rather than starting over again.

The logic of upgrading PoC projects into full workspaces makes sense, it’s a normal workflow. That’s exactly why the request to keep history after a rename or move makes sense too. I’ll pass this along as feedback in that thread to help bump the priority.

Glad you found a working option with a plugin to persist context. As a temporary solution, it’s a handy way to pick up the conversation where you left off.

If anything else comes up on this topic, feel free to post in the thread. Good luck with your projects.