Every AI you use.
One memory you own.

Let your AI install memex for you

Already chatting with Claude Code, Cursor, Cline, Continue, or Zed? Any of them can do the whole install in 2 minutes — clone, wire the MCP config, turn on auto-capture. Just paste this prompt into the agent. It will show you each command before running, ask for confirmation on anything risky, and tell you when to restart.

Install memex on this machine. Memex is a local-first AI memory tool — it captures my Claude Code and Cowork conversations into a searchable SQLite index that any MCP-compatible agent can query. Repo: https://github.com/parallelclaw/memex-mvp

Do these four steps in order. Show each command before you run it. Stop and ask if anything fails or looks wrong.

1. Clone and install
   - Suggest a parent directory (default: ~/Documents). Confirm with me.
   - cd into that directory
   - git clone https://github.com/parallelclaw/memex-mvp
   - cd memex-mvp
   - npm install
   Verify: server.js exists; npm install completed without fatal errors.

2. Wire memex into my MCP client
   - You're running inside one of: Claude Code, Cursor, Cline, Continue, Zed.
     Tell me which one you've inferred and which config file you'll edit.
     Common locations:
       Claude Code  → ~/.claude/config.json (or platform-specific equivalent)
       Cursor       → ~/.cursor/mcp.json
       Cline        → VS Code settings.json (cline.mcpServers)
       Continue     → ~/.continue/config.json
       Zed          → ~/.config/zed/settings.json (context_servers)
     If unclear, ask me.
   - Read the existing config (if present). Show me a diff before saving.
   - MERGE this entry into mcpServers — never overwrite other servers I have:
     {
       "mcpServers": {
         "memex": {
           "command": "node",
           "args": ["<absolute path to memex-mvp/server.js>"]
         }
       }
     }
     Use the absolute path from step 1 (run pwd inside memex-mvp).
   - If the config file doesn't exist, create the parent directory and write a minimal valid file with just memex.
   Verify: re-read the file after save; confirm memex entry is present and the path is absolute.

3. Turn on live auto-capture (recommended)
   - From the memex-mvp directory: npx memex-sync install
   - Then npx memex-sync status — should print "daemon installed", "running (PID …)", "watching N sessions".
   Verify: status output shows a non-zero PID.

4. Tell me what to do next
   - Tell me to fully quit and reopen the MCP client (Cmd+Q on macOS) so it picks up the new memex tools.
   - After restart, suggest I ask: "show me what memex has in memory"
     — that triggers memex_overview and confirms everything works end-to-end.

Safety rules — read these before starting:
- If `node` or `npm` aren't installed, stop and tell me to install Node.js (recommend nvm.sh). Don't try to install Node yourself.
- Never run rm, sudo, or anything destructive without explicit confirmation from me.
- Show every command before running it. If I say "no" or "stop", halt and explain.
- If a step fails, do NOT auto-retry or auto-fix — tell me what failed and ask how to proceed.
- When editing my MCP config, always preserve existing entries. If you can't merge cleanly, abort and tell me.

Begin by greeting me, asking which directory to clone into, and confirming which MCP client I'm using.