cloud-sync

Cloud Sync (cmem.ai Pro)

The worker syncs memories itself: every write nudges a background flusher that drains unsynced rows to cmem.ai. There is no daemon to install or babysit. This skill is a thin front-end — check status, and on first run collect credentials, retire the old standalone client, and restart the worker so it picks them up.

Security rule for this entire skill: NEVER print the sync token, never put it in a command-line argument (argv is visible to other processes), and never log it. It travels only inside heredoc-fed stdin scripts or files that already hold it. When confirming, report its length — not its value.

1. Check status

Resolve the worker port (env → ~/.claude-mem/settings.json → per-UID default 37700 + (uid % 100), matching how the worker picks its own port; re-run this in any fresh shell before the curls in step 5):

PORT="${CLAUDE_MEM_WORKER_PORT:-$(node -e "const fs=require('fs'),p=require('path'),os=require('os');const uid=(typeof process.getuid==='function'?process.getuid():77);const fallback=String(37700+(uid%100));try{const s=JSON.parse(fs.readFileSync(p.join(os.homedir(),'.claude-mem','settings.json'),'utf-8'));process.stdout.write(String(s.CLAUDE_MEM_WORKER_PORT||fallback));}catch{process.stdout.write(fallback);}" 2>/dev/null)}"
curl -s "http://127.0.0.1:${PORT}/api/sync/status"

Responses:

• {"configured": true, "deviceId": ..., "pending": {"observations": N, "summaries": N, "prompts": N}, "lastFlushAt": ..., "lastError": ...} → go to step 2.
• {"configured": false} → go to step 3.
• 404 / 503 / connection refused → the route registers late during worker startup, so a request right after a restart can miss it. Retry every 3s for ~15s before concluding anything. If 404 persists, the running worker predates cloud sync — restart it with the command in step 5, wait, and retry.

2. Already configured → report and stop

Report the three pending counts, lastFlushAt, and lastError (null means healthy). Pending counts near 0 mean the cloud copy is current. Done — do not run the setup steps below.