Memory survives the chat

What you lose when the thread dies

Claude Code closed. Composer crashed. The gateway restarted. The next thread starts blank — unless the memory is yours.

Claude Code — the session is gone

Compaction ran. You closed the terminal. You cloned the repo on a new laptop. The thread that knew this week’s constraints is not in the new window.

What dies with the session: the working context, the todos.md you were mid-list on, the local .claude/memory/ that never made it to the other machine. CLAUDE.md is still a file. The session is not.

A transcript is not a restore. The next session starts polite and empty.

Cursor — Composer forgot you

The tab is gone. Cursor crashed. You switched machines. The Composer thread that knew the refactor, the MCP stack, the rules you argued into place — gone with the window.

What dies with the thread: the conversation. ~/.cursor/mcp.json and .cursor/rules/*.mdc may still sit on the old disk. The composer that used them does not come back with the next window.

A Composer export is not a restore. The chat is not the memory.

Clawdbot — the gateway came back a stranger

The process died. The gateway came back. Without the workspace, the next process has no soul, no memory, no skills, no routing.

What dies with the gateway: SOUL.md, MEMORY.md, the skills/ that made it useful, the session JSONL under the agents directory. Restart is not restore. It answers like it just met you.

The archive survives

The future state is not a longer chat. It is an encrypted archive you search and restore.

• Claude Code First-class. Full extract and restore of CLAUDE.md, project .claude/, and ~/.claude/. We put the files back. We do not invent conversation replay Claude Code does not store as files.
• Cursor Community adapter. MCP servers, composer-rules, and project rules restore. Composer history is extracted into the archive so you can search it. Restore never writes back into Cursor’s live SQLite.
• Clawdbot First-party. SOUL.md, MEMORY.md, skills, gateway config, and sessions — extract and restore. Credentials stay out unless you opt in.

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

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.

For one tool: Claude Code · Cursor · Clawdbot · When the chat dies