cloud-sync

# Cloud Sync (cmem.ai Pro) The installed worker syncs through SyncHub. There is one client, one durable operation log, and no separate sync daemon. This skill checks status or writes the three connection values issued by **cmem.ai → Connect**. **Security rule:** never print the sync token, put it in argv, or log it. Confirm only its length. Preserve every unrelated setting and keep `~/.claude-mem/settings.json` mode `0600`. ## 1. Check status Resolve the worker port and query the always-registered status route: ```bash 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" ``` - `configured: true` and `hub.reachable: true` → the worker completed an authenticated `GET /v1/sync/status` against SyncHub. Report `deviceId`, pending counts, `lastFlushAt`, `lastError`, and the Hub head/checkpoint; stop unless the user asked to replace the connection. - `configured: true` and `hub.reachable: false` → report `hub.error` and say the SyncHub connection is not verified. A zero pending count or `lastError: null` is not success because an empty queue perform...