How to move a Claude Code conversation into Cursor

Between two editors, which is what happens when you switch tools mid-project or when a team standardises on one. Both of these write their transcripts to your own disk, so this is the one move where nothing has to be exported, waited for, or reconstructed.

The four ways, worst to best

1. 01

   Start again and re-establish the context

   The default, and the most expensive one. A Claude Code session that was worth continuing usually contains a long chain of decisions about a specific codebase, and re-establishing that by hand is most of an afternoon.

2. 02

   Scroll back and copy what looks important

   Sound in principle. In practice you are deciding what mattered while looking for it, and the thing that turns out to matter is usually a constraint mentioned once, early, which is exactly what scrolling misses.

3. 03

   Point Cursor at the transcript files

   Claude Code keeps its sessions as plain files on your disk, so you can genuinely open one and hand it over. This works and it is the reason the last option is possible at all.

   What it costs is that a raw session file is a machine's record rather than a conversation: tool calls, results, and internal blocks nobody typed, interleaved with what you actually said.

4. 04

   Hand it over compiled

   Sidq reads the same files and compiles them before they go anywhere: the harness blocks stripped, the exchange kept word for word, and where a session is longer than the destination can hold it carries what matters and names what it left, in the file, where the next assistant reads it.

   Nothing is summarised and nothing is uploaded. Both of these assistants are on your disk already, so the whole move happens on your machine.

More questions: how Sidq reads each assistant · what it costs