How to move a Cursor conversation into Claude
The direction people take when an editor has stopped being the right tool: the problem turned out to be a design question rather than an edit, and you want a model with room to think about it. The good news is that Cursor already wrote the conversation to your disk.
The four ways, worst to best
- 01
Describe the problem again in Claude
Starting clean is sometimes right, because a fresh framing can be worth more than the history. It is not right when the useful part is everything you already ruled out, which is exactly the case when you have been going back and forth in an editor.
- 02
Copy the chat out of the sidebar
Workable for a short exchange. Cursor's chat panel is narrow and long, so selecting a real conversation means scrolling through it while holding a selection, and code blocks come across with the interface attached.
- 03
Find the transcript on disk yourself
It is genuinely there. Cursor keeps its chat history in a local database, so unlike a browser assistant nothing needs exporting and nothing needs waiting for.
Reading it by hand means locating the right file, understanding a schema nobody documented for you, and pulling one conversation out of it, all for a conversation you wanted to move two minutes ago.
- 04
Hand it over in one keystroke
This is the case Sidq is easiest about, because the work is already done. Cursor writes to your disk, so Sidq has read it already, including everything from before you installed Sidq.
Press the shortcut, pick the conversation, paste into Claude. Nothing is uploaded: the reading happens between two programs on your own machine.
If you do this more than once a week
Sidq is free, with no card and no weekly count. It reads ChatGPT, Claude, Gemini, Grok and DeepSeek in your own browser, and Claude Code, Cursor, Windsurf and VS Code straight off the disk, including everything you did before you installed it.
Mac app. Free, no card, about a minute to set up.
More questions: how Sidq reads each assistant · what it costs