For Codex

When the Codex thread dies, the memory is yours

The chat can die. The archive does not. Encrypted portable memory for Codex CLI and OpenAI Codex — searchable from inside the model.

The next Codex thread is blank

The session ended. You switched machines. The thread is gone. Codex still talks — it does not remember last Tuesday unless the memory lives outside the chat.

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

What Codex gets from SaveState

No fake adapter. Codex talks to the same encrypted archive every other MCP client uses. One command wires it.

• Product SaveState — encrypted portable memory layer
• Client Codex CLI / OpenAI Codex
• Wire codex mcp add savestate -- npx -y @savestate/cli mcp
• Search savestate_search_snapshots across every snapshot, even from Cursor or Claude Code
• Memory savestate_memory_store / _search / _delete against the local store
• Encryption AES-256-GCM, scrypt KDF. You hold the passphrase

Passphrases stay in the local process. Setup detail lives in the MCP guide.

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

One command. Full setup lives in the MCP guide.

codex mcp add savestate -- npx -y @savestate/cli mcp

Same JSON every other client uses:

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

Also: Cursor · Claude Code · MCP · When the chat dies