​

CMEM Pro (manual / headless)

​

What the installer does

1. Runtime — Bun/uv if needed, IDE plugin files, worker deps.
2. Sign in — skipped for --provider claude, and for non-interactive runs without --provider (fresh install defaults to claude; an existing config keeps its provider). A non-interactive install that skipped sign-in prints an optional sign-in link as its last line; agents should show that link to the user rather than open it. Local installs contact cmem.ai once, at signup, to create the sign-in link, with a numbers-only usage summary (observation counts and token totals, no prompts, paths, or project names); nothing else is sent to cmem.ai. Otherwise the CLI does not ask for an email:
   • POST https://cmem.ai/api/installer/oauth/start with { source: "npx-installer", device_name: <hostname>, install_state: "fresh" | "update", usage_summary?: { window_days: 28, active_days, observations, memory_tokens, days: [{ d: "YYYY-MM-DD", obs, tokens }] } } (usage_summary is omitted when no local data can be read)
   • prints a device code XXXX-XXXX and opens authorization_url
   • polls https://cmem.ai/api/pro/trial/poll until authenticated
3. Provider — CMEM Pro is pre-selected. Choosing it opens checkout_url (trial/claim), polls until status: "ready", then writes settings and restarts the worker.

​

Settings the installer writes

​

Staged (sync + trial metadata)

​

Activated (this is what makes observations run)

{
  "CLAUDE_MEM_PROVIDER": "openrouter",
  "CLAUDE_MEM_OPENROUTER_BASE_URL": "https://cmem.ai/api/inference/v1",
  "CLAUDE_MEM_OPENROUTER_MODEL": "cmem-observer",
  "CLAUDE_MEM_OPENROUTER_API_KEY": "cm_pro_YOUR_MEMORY_KEY",
  "CLAUDE_MEM_PRO_MEMORY_KEY": "",
  "CLAUDE_MEM_PRO_MEMORY_BASE_URL": "",
  "CLAUDE_MEM_PRO_MEMORY_MODEL": ""
}

​

Manual recipe (you already have tokens)

1. From cmem.ai → Connect (or an installer pairing), copy setup_token, user_id, hub_url, and memory_key (if missing, use setup_token).
2. Merge staged + activated keys into ~/.claude-mem/settings.json. Placeholders only:

{
  "CLAUDE_MEM_CLOUD_SYNC_TOKEN": "cm_pro_YOUR_SETUP_TOKEN",
  "CLAUDE_MEM_CLOUD_SYNC_USER_ID": "YOUR_USER_ID",
  "CLAUDE_MEM_CLOUD_SYNC_HUB_URL": "https://YOUR_HUB_URL",
  "CLAUDE_MEM_CLOUD_SYNC_DEVICE_ID": "",
  "CLAUDE_MEM_CLOUD_SYNC_DEVICE_NAME": "my-machine",
  "CLAUDE_MEM_PRO_TRIAL_STATE": "active",
  "CLAUDE_MEM_PRO_TRIAL_ENDS_AT": "",
  "CLAUDE_MEM_PRO_PLAN": "trial",
  "CLAUDE_MEM_PRO_FALLBACK_AT": "",
  "CLAUDE_MEM_PROVIDER": "openrouter",
  "CLAUDE_MEM_OPENROUTER_BASE_URL": "https://cmem.ai/api/inference/v1",
  "CLAUDE_MEM_OPENROUTER_MODEL": "cmem-observer",
  "CLAUDE_MEM_OPENROUTER_API_KEY": "cm_pro_YOUR_MEMORY_KEY"
}

3. chmod 600 ~/.claude-mem/settings.json
4. Restart the worker so it is not holding old in-memory provider/sync state:

npx claude-mem restart

5. Verify (port is CLAUDE_MEM_WORKER_PORT or ~/.claude-mem/.worker.port):

curl -s "http://127.0.0.1:${CLAUDE_MEM_WORKER_PORT}/api/health"
curl -s "http://127.0.0.1:${CLAUDE_MEM_WORKER_PORT}/api/sync/status"

6. First real observation should store via model cmem-observer. Gateway success clears CLAUDE_MEM_PRO_FALLBACK_AT. A terminal gateway rejection (a spent allowance, an inactive subscription, or a refused key) sets that timestamp, memory falls back to the Anthropic plan, and the next session start relays the gateway’s own message and link.

​

What not to mix

​

Next steps

• Installation — interactive three-stage installer
• Cloud Sync — what the sync trio replicates
• OpenRouter provider — personal OpenRouter keys (not cmem.ai)