For Cursor

When Composer dies, Cursor still knows

The chat can die. The archive does not. Encrypted portable memory for the Cursor setup you actually live in.

The next Composer is blank

Cursor crashed. You switched machines. The tab is gone. MCP servers, composer-rules, and the .cursor/rules/*.mdc that made the agent yours — still sitting where the vendor left them, or gone with the disk.

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

What we snapshot in Cursor

Community adapter. We capture the files that make Cursor yours — and we do not pretend the rest is done.

• ~/.cursor/mcp.json Global MCP servers. Restored on the next machine.
• ~/.cursor/composer-rules Global Composer rules → identity. Restored as-is.
• .cursor/mcp.json Project MCP servers, merged over global. Project wins on name clash.
• .cursor/rules/*.mdc Project rules, one skill per file. Written back on restore.

Workspace SQLite (state.vscdb under Cursor workspaceStorage) is recorded in the file manifest today — path and size only. We do not parse Composer threads yet. That is v2. Restore never writes back into the live IDE database.

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 Cursor MCP

Below the fold, one file: ~/.cursor/mcp.json or project .cursor/mcp.json. Full setup lives in the MCP guide.

{
  "mcpServers": {
    "savestate": {
      "command": "npx",
      "args": ["-y", "@savestate/cli", "mcp"]
    }
  }
}

Also: Claude Code · Clawdbot · When the chat dies