mem-search

1# Claude-Mem Search
2 
3Search the user's persistent Claude-Mem memory on cmem.ai. Memory contains
4timestamped observations synthesized from past sessions across all their
5agents (Claude Code, the Claude app, Codex, and others).
6 
7## How to search
8 
9Run the bundled CLI (no dependencies, uses the plugin's configured API key):
10 
11```bash
12node "${CLAUDE_PLUGIN_ROOT}/scripts/cmem-hook.mjs" search "your query" --limit 20
13```
14 
15## Progressive search method
16 
17Follow claude-mem's Index → Timeline → Transcript discipline — cheap passes
18first, expensive detail only for confirmed hits:
19 
201. **Index pass** — run 1–3 broad keyword searches (project names, file names,
21   error strings, feature names). Skim titles/summaries only.
222. **Narrow pass** — re-search with the most specific terms found in step 1
23   (IDs, exact phrases) and a smaller `--limit`.
243. **Answer** — synthesize from the observations returned. Quote timestamps
25   when the user asks "when".
26 
27Do not dump raw search output at the user; extract the relevant observations
28and answer in plain language.
29 
30## Diagnostics
31 
32If searches return nothing or error:
33 
34```bash
35node "${CLAUDE_PLUGIN_ROOT}/scripts/cmem-hook.mjs" status
36```
37 
38Report the status output plainly: a MISSING api key means the plugin needs the
39user's cmem.ai key added to its configuration; a 404 on `/api/hooks/context`
40just means the newer Pro endpoint isn't deployed — search still works via
41`/api/mcp`.
42 
43## Notes
44…