{
  "manifest_version": "1",
  "slug": "claude-mem",
  "title": "Claude-Mem",
  "headline": "Run Claude-Mem on a remote server",
  "description": "Self-host Claude-Mem on an always-on exe.dev VM: persistent memory for Claude Code, Codex and T3 Code, a private viewer, and no API key or account.",
  "category": "ai-agents",
  "tags": [
    "claude-mem",
    "claude mem",
    "claude code memory",
    "persistent memory",
    "codex memory",
    "t3 code",
    "mcp memory",
    "coding agent memory"
  ],
  "url": "https://exe.dev/deploy/claude-mem",
  "markdown_url": "https://exe.dev/deploy/claude-mem.md",
  "upstream": {
    "website": "https://claude-mem.ai",
    "source": "https://github.com/thedotmack/claude-mem",
    "docs": "https://docs.claude-mem.ai",
    "license": "Apache-2.0"
  },
  "example_vm_name": "my-claude-mem",
  "time": "10 minutes",
  "stack": [
    {
      "name": "Claude-Mem worker",
      "detail": "Claude-Mem 16 on Bun, run by a systemd user service; serves the hooks, search and the viewer",
      "port": 3777,
      "data": "~/.claude-mem"
    },
    {
      "name": "Observer",
      "detail": "Claude Haiku 5.5 through exe.dev's LLM integration; writes the memories"
    },
    {
      "name": "Vector search",
      "detail": "Chroma (chroma-mcp, started by the worker with uvx)",
      "data": "~/.claude-mem/chroma"
    },
    {
      "name": "Claude Code and Codex",
      "detail": "preinstalled; Claude-Mem's hooks record their sessions",
      "data": "~/.claude, ~/.codex"
    },
    {
      "name": "Your project",
      "data": "~/project"
    }
  ],
  "access": [
    {
      "url": "https://my-claude-mem.exe.xyz:3777/viewer",
      "who": "private",
      "what": "the memory viewer, behind exe.dev login"
    },
    {
      "url": "ssh my-claude-mem.exe.xyz",
      "who": "private",
      "what": "your agents, settings and upkeep"
    }
  ],
  "delivers": [
    "Claude-Mem 16 installed for Claude Code and Codex, its worker a service on port 3777 that comes back after a reboot",
    "The observer writing memories through exe.dev's LLM integration, with no API key, Claude login or claude-mem account",
    "A second Claude Code session that recalls what the first one did",
    "The memory viewer at `https://\u003cvm\u003e.exe.xyz:3777/viewer`, behind exe.dev login",
    "Daily snapshots of the memory database in `~/.claude-mem/backups/auto`, and Claude-Mem's telemetry off"
  ],
  "deployable": true,
  "deploy": {
    "new_vm_url": "https://exe.dev/new?prompt=Set%20up%20Claude-Mem%20on%20this%20VM%20by%20following%20the%20exe.dev%20recipe%20at%20https%3A%2F%2Fexe.dev%2Fdeploy%2Fclaude-mem.md%3Fvia%3Ddeploy%20from%20top%20to%20bottom.%0A%0AThe%20recipe%27s%20example%20VM%20name%20is%20my-claude-mem.%20This%20VM%27s%20name%20is%20the%20output%20of%20%60hostname%60%3A%20use%20it%20wherever%20the%20recipe%20writes%20my-claude-mem.%20Skip%20the%20step%20that%20creates%20the%20VM%3B%20you%20are%20on%20it.%0A%0AYou%20are%20done%20when%20all%20of%20these%20are%20true.%20Check%20each%20one%20yourself%3A%0A-%20Claude-Mem%2016%20installed%20for%20Claude%20Code%20and%20Codex%2C%20its%20worker%20a%20service%20on%20port%203777%20that%20comes%20back%20after%20a%20reboot%0A-%20The%20observer%20writing%20memories%20through%20exe.dev%27s%20LLM%20integration%2C%20with%20no%20API%20key%2C%20Claude%20login%20or%20claude-mem%20account%0A-%20A%20second%20Claude%20Code%20session%20that%20recalls%20what%20the%20first%20one%20did%0A-%20The%20memory%20viewer%20at%20%60https%3A%2F%2F%3Cvm%3E.exe.xyz%3A3777%2Fviewer%60%2C%20behind%20exe.dev%20login%0A-%20Daily%20snapshots%20of%20the%20memory%20database%20in%20%60~%2F.claude-mem%2Fbackups%2Fauto%60%2C%20and%20Claude-Mem%27s%20telemetry%20off%0A%0ARead%20the%20whole%20recipe%2C%20including%20the%20closed%20details.%20Follow%20%22Set%20up%20by%0Ahand%22%20first%2C%20skipping%20VM%20creation%20and%20SSH%2C%20then%20run%20the%20memory%20check%20in%0A%22See%20it%20remember%22%20%28both%20sessions%29.%20Don%27t%20run%20Restore%2C%20Update%2C%20or%20the%0Asharing%20and%20token%20examples.%20Don%27t%20sign%20in%20to%20claude-mem%20or%20open%20the%0Asign-in%20link%20the%20installer%20prints%3A%20this%20setup%20needs%20no%20account.%20If%0A%60~%2F.claude-mem%2Fsettings.json%60%20already%20exists%2C%20merge%20the%20settings%20into%20it%20as%0Awritten%20instead%20of%20replacing%20it.%20Do%20not%20open%20interactive%20%60codex%60%20or%0A%60claude%60%3B%20tell%20the%20owner%20that%20Codex%20asks%20them%20to%20trust%20the%20hooks%20the%20first%0Atime%20they%20open%20it.%20Verify%20that%20%60systemctl%20--user%20is-active%20claude-mem%60%20says%0A%60active%60%2C%20that%20%60ss%20-ltn%60%20shows%20%600.0.0.0%3A3777%60%2C%20and%20that%20the%20second%20session%0Amentions%20the%20Faroe%20Islands.%20Do%20not%20reboot.%20Finish%20by%20giving%20the%20owner%20the%0Aviewer%20URL%20with%20this%20VM%27s%20name.%0A%0AFinish%20with%20the%20URLs%20I%20should%20open.%0A",
    "terminal": "curl -fsSL https://exe.dev/deploy/claude-mem/prompt.txt | ssh exe.dev new --prompt=/dev/stdin",
    "prompt": "Set up Claude-Mem on this VM by following the exe.dev recipe at https://exe.dev/deploy/claude-mem.md?via=deploy from top to bottom.\n\nThe recipe's example VM name is my-claude-mem. This VM's name is the output of `hostname`: use it wherever the recipe writes my-claude-mem. Skip the step that creates the VM; you are on it.\n\nYou are done when all of these are true. Check each one yourself:\n- Claude-Mem 16 installed for Claude Code and Codex, its worker a service on port 3777 that comes back after a reboot\n- The observer writing memories through exe.dev's LLM integration, with no API key, Claude login or claude-mem account\n- A second Claude Code session that recalls what the first one did\n- The memory viewer at `https://\u003cvm\u003e.exe.xyz:3777/viewer`, behind exe.dev login\n- Daily snapshots of the memory database in `~/.claude-mem/backups/auto`, and Claude-Mem's telemetry off\n\nRead the whole recipe, including the closed details. Follow \"Set up by\nhand\" first, skipping VM creation and SSH, then run the memory check in\n\"See it remember\" (both sessions). Don't run Restore, Update, or the\nsharing and token examples. Don't sign in to claude-mem or open the\nsign-in link the installer prints: this setup needs no account. If\n`~/.claude-mem/settings.json` already exists, merge the settings into it as\nwritten instead of replacing it. Do not open interactive `codex` or\n`claude`; tell the owner that Codex asks them to trust the hooks the first\ntime they open it. Verify that `systemctl --user is-active claude-mem` says\n`active`, that `ss -ltn` shows `0.0.0.0:3777`, and that the second session\nmentions the Faroe Islands. Do not reboot. Finish by giving the owner the\nviewer URL with this VM's name.\n\nFinish with the URLs I should open.\n",
    "prompt_url": "https://exe.dev/deploy/claude-mem/prompt.txt"
  },
  "published": "2026-11-21",
  "updated": "2026-11-21",
  "verified": "2026-11-19",
  "related": [
    "claude-code",
    "codex",
    "t3code",
    "herdr",
    "agent-secrets",
    "openclaw"
  ]
}
