Set up Claude-Mem on this VM by following the exe.dev recipe at https://exe.dev/deploy/claude-mem.md?via=terminal from top to bottom. The 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. You are done when all of these are true. Check each one yourself: - 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://.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 Read the whole recipe, including the closed details. Follow "Set up by hand" first, skipping VM creation and SSH, then run the memory check in "See it remember" (both sessions). Don't run Restore, Update, or the sharing and token examples. Don't sign in to claude-mem or open the sign-in link the installer prints: this setup needs no account. If `~/.claude-mem/settings.json` already exists, merge the settings into it as written instead of replacing it. Do not open interactive `codex` or `claude`; tell the owner that Codex asks them to trust the hooks the first time they open it. Verify that `systemctl --user is-active claude-mem` says `active`, that `ss -ltn` shows `0.0.0.0:3777`, and that the second session mentions the Faroe Islands. Do not reboot. Finish by giving the owner the viewer URL with this VM's name. Finish with the URLs I should open.