Open source · latest release

Your AI coding sessions, anywhere you work.

Move conversations between Cursor, Claude Code, Codex, Copilot CLI, Cline and Continue — and between machines — so the context you built up comes with you.

Windows, macOS and Linux · CLI · VS Code extension · Free (MIT)

The MoveZ desktop app showing 7 sessions detected across Cursor, Claude Code, Codex and Copilot
Supported tools64 read & write
EncryptionAES-256GCM, client-side
Platforms3Windows · macOS · Linux
Telemetry0No accounts, no cloud

Works with

See details

Features

Take your context with you.

Switching editors or laptops shouldn't mean starting every conversation from scratch.

Transfer between tools

Copy a Cursor session into Claude Code, Codex or Copilot CLI in one step. Each tool's format is converted for you.

One step

Move to a new machine

Export a portable .cbz bundle and import it anywhere, with paths remapped from D:\Projects to ~/work.

.cbz

Encrypted end to end

Bundles and sync payloads are sealed with AES-256-GCM before they leave your machine. Your key never does.

AES-256-GCM

Self-hosted sync

Push and pull between machines through your own server. It only ever stores ciphertext.

Optional

Desktop, CLI or editor

A desktop app for Windows, macOS and Linux, a single-file CLI, and a VS Code / Cursor extension.

3 ways

Project config comes too

Optionally bundle CLAUDE.md, AGENTS.md, .cursorrules and .mcp.json.

Optional

How it works

Three steps. In the app or the terminal.

  1. 01

    Pick your sessions

    MoveZ finds the conversations every installed AI tool has stored on this machine.

  2. 02

    Transfer or bundle

    Send them straight to another tool, or pack them into an encrypted .cbz for another machine.

  3. 03

    Keep working

    Open the target tool. The full history is there, under the right project.

From
Cu
Cursorapi-gateway
Sessions
12
Turns
486
Route
CuCursor ClClaude Code
Path remap
D:/Projects → ~/work
Encryption
AES-256-GCM
Bundle
work.cbz
Transfer
The MoveZ migration wizard with Cursor as source and Claude Code selected as target
zsh
# copy Cursor sessions into Claude Code
$ movez transfer --from=cursor --to=claude-code
Transferred 2 session(s) from cursor to claude-code

# back up to an encrypted bundle
$ movez export --tool=claude-code --output=work.cbz --encrypt
Exported 3 session(s) to: work.cbz

# restore on the new laptop, fixing paths
$ movez key:import --file=movez.key
$ movez import --input=work.cbz --tool=claude-code \
    --from-path="D:/Projects" --to-path="~/work"
Imported 3 session(s) to claude-code

The app

Every session, readable and searchable.

Compatibility

Supported tools.

Cu

Cursor

~/.cursor/projects + state.vscdb

Read · Write
Cl

Claude Code

~/.claude/projects/*.jsonl

Read · Write
Cx

Codex CLI

~/.codex/sessions/…/rollout-*.jsonl

Read · Write
Co

Copilot CLI

~/.copilot/session-state/<id>/

Read · Write
Cn

Cline

VS Code extension task history

Read
Ct

Continue

~/.continue/sessions/*.json

Read

Windsurf isn't supported yet: it stores Cascade conversations in an encrypted format.

Privacy

Local-first. Private by design.

Your conversations are yours. MoveZ runs on your machine and talks to nothing you didn't configure.

Telemetry
None. No accounts, no network calls except your own sync server.
Encryption
AES-256-GCM, client-side. The server stores ciphertext only.
Your key
Lives at ~/.movez/key and moves only when you run movez key:export.
License
MIT, with tests for every format it reads and writes.

Download

Get MoveZ

Free and open source. The desktop apps bundle PHP and the CLI.

The macOS app isn't code-signed yet. The first time, right-click it and choose Open.

FAQ

Questions.

Does the AI remember the conversation after a transfer?

You get the full conversation history in the target tool. Cursor also keeps an internal model state that can't be recreated, so there the history is visible but the model won't automatically pick it up — start a new chat and reference the old one.

Do I need a server?

No. Transfers and .cbz bundles work entirely offline. The self-hosted sync server is optional, for pushing and pulling between machines without copying files.

How do I move my encryption key to another machine?

Run movez key:export on the first machine and movez key:import on the next, or pipe one into the other over SSH. movez key:fingerprint confirms both machines hold the same key.

Is it free?

Yes. MoveZ is open source under the MIT license.