​

Cloud Sync (cmem.ai Pro)

​

What syncs

• Observations — the compressed memories claude-mem generates from your sessions.
• Session summaries — the per-session overview records.
• User prompts — the prompts you typed. A prompt over 200 KB uploads as its first 200 KB plus a truncation note; the full prompt stays on the device that captured it.

​

How the push lane works

• Debounced: write bursts coalesce; the flusher runs ~1.5 s after the last write (250 ms while the speed layer is connected), and only one flush runs at a time.
• Batched: ops drain in requests of up to 500 ops / 4,000,000 encoded bytes. Each individual canonical body is capped at 256,000 encoded bytes.
• Timeboxed: every request has a 30 s timeout — a dead network can never hang the worker.
• Retrying: a failed upload leaves rows NULL and retries on the next write plus a capped exponential backoff (30 s → 10 min). The write path is never blocked — sync failures cost nothing but delay.
• Idempotent: the hub dedupes on origin identity, so a retried push can never create duplicates.

​

How the pull lane works

• Session start: the worker pulls immediately before injecting context (bounded to 1.5 s, so a dead network can’t stall your session), which means memory written on another machine is there the moment you start working.
• Steady state: a short poll every 30 s while a session is active, every 5 min when idle, suspended entirely after an hour of no activity. Every push response also reports the log head, so an active device learns about remote writes without waiting out the timer.
• Applied like native writes: pulled rows keep their original timestamps, carry their origin device, index into full-text and vector search through the same paths native writes use, and are stamped so they can never be echoed back up.

​

Live updates (optional)

​

Requirements and setup

1. A cmem.ai Pro sync token and user id (from cmem.ai → Connect).
2. A sync hub URL in CLAUDE_MEM_CLOUD_SYNC_HUB_URL: https://sync.cmem.ai, which the installer writes for you (source in services/sync-api/). A hub URL pinned to the older Cloudflare Workers hub is moved to it automatically.

​

Settings

​

Status endpoint

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

{
  "configured": true,
  "deviceId": "2f6b1c9e-7d41-4c1a-9b0e-3d5f8a2c6e10",
  "pending": { "observations": 0, "summaries": 0, "prompts": 2, "mutations": 0, "tombstones": 0 },
  "quarantine": { "count": 0, "latestReason": null },
  "lastFlushAt": 1783981042731,
  "lastError": null,
  "hub": {
    "checkedAt": 1783981042800,
    "reachable": true,
    "epoch": "1783981042000",
    "headSeq": "42",
    "projectedSeq": "42",
    "error": null
  }
}

• pending — rows (and queued mutation ops) still waiting to upload. Counts near 0 mean the hub’s log has everything this device wrote.
• lastFlushAt — epoch ms of the last successful flush, null before the first.
• lastError — message from the most recent failed flush, null when healthy. It never contains the token.
• hub — the most recent authenticated SyncHub probe. Treat hub.reachable: true as the connectivity check; lastError: null alone is not enough. Sequence and epoch fields remain decimal strings.

{ "configured": false }