I wanted to move my Cursor chats to another workspace and keep working in them. I started with a fork of Cursor Chat Transfer and spent the past week reworking it after running into problems with imports and large exports.
The result is Cursor Chat Transit:
You select a source workspace, export the chats you want to a ZIP, then import it into the destination workspace. For another computer, copy the archive over first. After importing, quit and reopen Cursor to load the added chats.
I’ve tested importing conversations from two separate archives and could continue them afterward. Supported chat data includes images, plans, and canvases alongside the messages.
Importing the same unchanged snapshot again doesn’t create another copy. If the conversation has changed since the previous export, importing it creates a separate chat.
Large exports were a headache during development. I changed the archive format to use smaller files inside a ZIP so the extension doesn’t have to keep the entire export in memory. There’s also a sidebar showing operation progress and logs.
To install, download the VSIX from GitHub Releases, then open Extensions in Cursor and choose “Install from VSIX…” from the menu:
You’ll also need the sqlite3 command-line tool installed. The README covers setup.
This is manual export/import, with no automatic sync. It relies on Cursor’s internal storage format, so updates can affect compatibility. Some older chats can be transferred but may still be too old for Cursor to continue.
Credit to ibrahim317 for the original Cursor Chat Transfer project.
If you try it, I’d like to know whether your chats transfer and can be continued, along with the Cursor version you’re using. You can reply here or open a GitHub issue. Please leave private conversation data out of reports.