For Claude Code

When the session ends, Claude Code still knows

The chat can die. The archive does not. Encrypted portable memory for CLAUDE.md, .claude/, and the settings that make the agent yours.

The next session forgets the repo

Claude Code closed. Compaction ran. You cloned the project on a new laptop. CLAUDE.md is the agent. .claude/ is the local brain. ~/.claude/ is the global one. Leave them on the old disk and the next session starts polite and empty.

A transcript is not a restore. The chat is not the memory.

What we snapshot in Claude Code

First-class adapter. Extract and restore — the files go back where they came from.

• CLAUDE.md Root instructions plus nested CLAUDE.md files, path-marked so restore writes each one back.
• .claude/ Project settings, settings.local.json, todos.md, and .claude/memory/.
• ~/.claude/ Global settings and global CLAUDE.md. MCP for Claude Code lives in ~/.claude/settings.json.

This is a full extract and restore. We put CLAUDE.md, project .claude/, and ~/.claude/ back on disk. Review paths after a machine switch. We do not invent conversation replay Claude Code does not store as files.

Each snapshot is a SaveState Archive, encrypted with AES-256-GCM before it leaves the machine. You hold the passphrase.

Pro is the path a stranger can take

The CLI is open source. The product you can buy today is SaveState Pro — $9/month:

• Scheduled auto-backups
• Cloud storage (10GB)
• All platform adapters
• Search across snapshots
• Web dashboard
• Email alerts on backup failures

Need shared snapshots and an audit log? Team is $29/month.

Wire SaveState as Claude Code MCP

Below the fold, one file: ~/.claude/settings.json. Full setup lives in the MCP guide.

{
  "mcpServers": {
    "savestate": {
      "command": "npx",
      "args": ["-y", "@savestate/cli", "mcp"],
      "env": {
        "SAVESTATE_MCP_PASSPHRASE": "your-passphrase-here"
      }
    }
  }
}

Also: Cursor · Clawdbot · When the chat dies