Claude-Mem explained: what a coding agent remembers
Claude-Mem quickstart: one host, one provider
Choose the documented installer path and test recall without importing sensitive work
What you will learn
- Pick an install route
- Make provider choice explicit
- Verify with two sessions
Before you start
- A synthetic two-session project
- One supported host
- A deliberate memory provider choice
Use two synthetic sessions and an explicit deletion check before team adoption
Key takeaways
- The CLI installer and plugin marketplace are distinct routes.
- Global npm install does not register hooks.
- Recall requires a later-session check.
Pick an install route
For the CLI route the README documents `npx claude-mem install`. Claude Code also offers `/plugin marketplace add thedotmack/claude-mem` followed by `/plugin install claude-mem`.
The README warns that `npm install -g claude-mem` installs the SDK or library only; it does not register host hooks or start the worker. Decide which host you are testing before running an installer.
Make provider choice explicit
The interactive installer can invite browser sign-in and provider selection. An explicit `--provider`, `CLAUDE_MEM_ONLINE_OPTIN=false`, or non-interactive run can skip that sign-in path.
Avoid sending a private repository or real credentials through a first trial. Record provider, local data directory and any remote endpoint selected by the installer; hosted trial claims are not a substitute for current terms.
Verify with two sessions
Use a synthetic project. Let the first session establish one checkable decision, close it and start a second session to search or inspect the retrieved observation.
A successful install message checks setup, not memory quality. We did not execute these steps, so the chapter gives a reproducible acceptance test rather than a claimed result.
Decision guide
| Criterion | Option A | Option B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Implementation steps
- 1
Pin the package and select one host.
- 2
Choose the provider and keep the test data synthetic.
- 3
Verify one fact in a second session.
Copy-ready example
npx claude-mem install --help
# After choosing a host and provider, test one synthetic two-session taskFrequently asked questions
Can I avoid browser sign-in?
The pinned README documents an explicit provider or online opt-out; inspect current installer behavior before use.
Does installation prove memory works?
No. Test capture and recall with a fact you can verify.
Sources
- Claude-Mem / README.mdSource checked 2026-10-08
- Claude-Mem / package.jsonSource checked 2026-10-08
- Claude-Mem / plugin/.claude-plugin/plugin.jsonSource checked 2026-10-08