Mnemo

Pick up any Claude Code session on any machine.

Mnemo syncs your Claude Code conversations across computers as encrypted, deduplicated, append-only snapshots — then lays them back down so claude --resume finds them, no matter where each project lives on each machine.

Why

You start a conversation with Claude Code on your laptop. The next day you’re at your desktop, and that session is gone, pinned to the other machine’s filesystem. Mnemo carries it across.

It’s a clean-room successor to tawanorg/claude-sync, rebuilt around three guarantees the naive “just mirror the folder” approach gets wrong:

• It can’t lose your data. Every sync is an immutable, additive snapshot. A file missing locally never deletes anything remote — deletion happens only through an explicit, retention-bounded prune.
• It follows your layout across machines. Sessions are keyed by a path-tokenized project identity, not a raw absolute path, so ~/Code/foo matches across machines regardless of OS or username.
• It syncs sessions, not config. Your conversations, memory, plans, and history — never your MCP servers, skills, agents, plugins, or settings. A hard boundary, not a toggle.

How it works

A thin, Claude-aware layer over restic. restic handles the hard, dangerous parts — AES-256 encryption, content-defined dedup, immutable snapshots, integrity checks, retention. Mnemo adds the project-identity keying and the lay-down logic that makes sessions resumable anywhere.