cloud-sync

Files (1)

• SKILL.md

SKILL.md (first lines)

# 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 and points
the user to the installer's cmem.ai sign-in, which writes the connection.

**Security rule:** never ask the user to paste the sync token into this chat,
and never put it in a command you write, print it, put it in argv, or log it. A
secret pasted into a chat lands in the transcript, which claude-mem itself can
capture and sync. The installer writes the token to
`~/.claude-mem/settings.json` (mode `0600`) without it ever passing through
this conversation.

## 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 performs no push.
- `configured: false` → continue.
- Connection refused, 404, or 503 immediately after restart → retry every
  three seconds for about 30 seconds before diagnosing the worker.

## 2. Connect through the installer

Ask the user to run this in their own terminal:

```bash
npx claude-mem install
```

and to choose **CMEM Pro** when the installer asks. The installer signs them in
through the browser (they approve a device code), then writes the sync token,
user id and SyncHub URL into `~/.claude-mem/settings.json` itself and restarts
the worker. Nothing secret is typed into this chat.

If the user cannot run the installer interactively (CI, a remote box), point
them to the headless setup guide, https://docs.claude-mem.ai/cmem-pro-headless,
and let them apply its manual recipe in their own terminal or editor. Do not
collect the values yourself.

The worker mints and persists a device id on first start and defaults the device
name to the hostname.

## 3. Verify

Once the installer finishes, poll the status route every five seconds for up to
30 seconds. If the worker was not restarted, restart it first:

```bash
curl -s -X POST "http://127.0.0.1:${PORT}/api/admin/restart"
```

Success means `configured: true`, `hub.reachable: true`, and `lastError: null`.
The local route always makes an authenticated, read-only SyncHub status probe,
even when every pending count is zero; it never uses a legacy cmem.ai Pro status
route and never appends or advances sync state. Pending counts describe only
writes made after the SyncHub launch baseline; setup does not migrate a
pre-launch local corpus.

If `hub.reachable` is false, report `hub.error`. If `lastError` is non-null,
report it too, and suggest running `npx claude-mem install` again to refresh the
connection. Never include the token.

## 4. Report

Report device id, pending counts, last successful flush, Hub reachability and
checkpoint, and any Hub/flush error. End with this privacy note:

> Cloud sync uploads your observation narratives and full prompt text to your
> cmem.ai account.

From thedotmack/claude-mem, Apache-2.0.

More from thedotmack/claude-mem