cloud-sync

1# Cloud Sync (cmem.ai Pro)
2 
3The installed worker syncs through SyncHub. There is one client, one durable
4operation log, and no separate sync daemon. This skill checks status and points
5the user to the installer's cmem.ai sign-in, which writes the connection.
6 
7**Security rule:** never ask the user to paste the sync token into this chat,
8and never put it in a command you write, print it, put it in argv, or log it. A
9secret pasted into a chat lands in the transcript, which claude-mem itself can
10capture and sync. The installer writes the token to
11`~/.claude-mem/settings.json` (mode `0600`) without it ever passing through
12this conversation.
13 
14## 1. Check status
15 
16Resolve the worker port and query the always-registered status route:
17 
18```bash
19PORT="${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)}"
20curl -s "http://127.0.0.1:${PORT}/api/sync/status"
21```
22 
23- `configured: true` and `hub.reachable: true` → the worker completed an
24  authenticated `GET /v1/sync/status` against SyncHub. Report `deviceId`,
25  pending counts, `lastFlushAt`, `lastError`, and the Hub head/checkpoint;
26…