mem-setup

1# Claude-Mem Setup (Claude app pairing)
2 
3Configure this plugin with the user's own cmem.ai credentials so hooks can
4capture and inject memory. Anyone can pair — credentials are per-user
5configuration, never hardcoded in plugin logic.
6 
7## What to collect
8 
9From **cmem.ai → Connect**, the user has three values:
10 
111. **sync token** (starts with `cm_`) — used as the bearer API key
122. **user id** (UUID)
133. **SyncHub URL** (`https://sync.cmem.ai`)
14 
15If the user pastes the whole Connect blurb, extract the three values from it.
16If any are missing, ask for the sync token at minimum — the other two are
17optional.
18 
19## Secret handling — non-negotiable
20 
21- Never echo the token back in conversation, put it in a shell argv, or log it.
22- Move it only via file writes (Write/Edit tool) and file reads.
23 
24## Steps
25 
261. Locate the installed plugin root (this skill's own plugin). Update its
27   `config.json`: set `apiKey` to the sync token, `userId`, and `syncHubUrl`.
28   Leave other settings unless the user asks (`inject` toggles). Project naming
29   is automatic (`cmem_work_*`) and is not configurable.
302. Claude app containers are ephemeral: edits to the installed copy last only for
31   this session. To make pairing permanent, repackage — zip the plugin
32   directory as `<plugin-name>.plugin` and send it to the user to re-install
33   (the cowork-plugin skill's packaging flow). Tell the user this is why.
343. If this machine also has a local claude-mem install (a `~/.claude-mem/`
35…