Your sessions. Anywhere.
Move the conversations you choose. Keep every version in view.
Session library
| Session / project | Source activity | Destination activity | Status / group |
|---|
Content lineage is checked in the preview. Divergent versions stay separate, and writes are backed up first.
Each Claude Code root is a separate profile. Sign in to its account through Claude.
Use CLAUDE_CONFIG_DIR for another account. Login tokens, MCP settings and source permissions are not copied. Desktop indexing is experimental.
Send encrypted packages to another device. The receiver reviews them before importing.
Incoming packages
Packages wait here until you unlock and preview them.
Run ClaudeSync on both machines. The destination needs HTTPS and a trusted certificate. You can also move encrypted packages as ordinary files.
Restore earlier files without discarding work created after a transfer.
The web UI controls your local C# server.
A browser does not silently read or overwrite arbitrary files. ClaudeSync’s server performs those operations on its own device under your user permissions.
Browser
Choose sessions, upload a selected package, or download an export.
C# server
Profile folders
Scan configured roots. Write only through a reviewed, backed-up import.
Download / export
The server reads selected sessions, encrypts a package and sends it to your browser. Your browser chooses where to save the download.
Upload / import
The file picker selects a package on the browser’s device. Uploading sends that file to the server; it does not grant access to the rest of the device.
Write / replace
Choose a writable destination profile, review the exact file changes and close Claude there. The server validates hashes, backs up and applies your choices.
The folder browser still shows the server machine’s folders. To write sessions on the second machine, run ClaudeSync there too and send it a package. A hosted website alone cannot rewrite your local session folders.
Configured profile access
These are application write policies. Actual operating-system permissions are checked when an operation runs.
Transport packages are encrypted. Local backups and the conflict vault contain plaintext session data in your private app data folder.