Quick Verdict
claude-mem 13.11 is an Apache-2.0 persistent-memory plugin for Claude Code. Lifecycle hooks capture coding-session observations, compress and index them, then retrieve relevant history in later sessions. It is useful when developers repeatedly explain repository structure, architectural decisions, and unfinished work to a coding agent. Core state can remain on the developer’s machine, but “local memory” does not mean every processing step is offline. If summarization or embeddings use an external model provider, related prompts, code fragments, and tool results follow that provider’s data path.
The project also offers optional CMEM cloud early access. Its current public commitment says customer data is not used for model training, while synchronization, retention, deletion, subprocessors, and account controls still require review under the live policy and contract. Because the plugin observes tool activity and influences future prompts, it has more privilege than an ordinary chat extension. Test it first on a non-sensitive repository and audit the installer, pinned version, local viewer, model credentials, and recorded memory.
Best For
- Daily Claude Code users who repeatedly resume long refactors or investigations.
- Developers prepared to maintain local state and review exactly what the plugin records.
- Teams with code classification, secret scanning, dependency review, retention, and deletion procedures.
- Maintainers who need searchable history for legacy repositories and architectural decisions.
- Not ideal for strict offline environments, one-off questions, or organizations that have not approved external model processing.
Key Features
- Cross-session memory: extracts observations and summaries for later retrieval.
- Local state: keeps the memory database and index on the developer device in the local setup.
- Lifecycle hooks: captures context around session start, prompts, tool use, and completion.
- Search and viewer: supports targeted retrieval and a local interface instead of replaying every raw log.
- Context compression: turns long activity records into shorter memories to reduce repeated background prompts.
- Optional CMEM cloud: provides an early-access hosted path without being required for the open-source core.
- Apache-2.0 core: permits inspection, modification, and redistribution without granting rights to third-party services or user content.
Use Cases
A practical use case is resuming a refactor after several sessions. The plugin can recall modules already changed, failed tests, and rejected approaches. It can also help maintainers search for why an adapter exists or where an earlier upgrade stopped. For memory inside an end-user AI application, compare Mem0; claude-mem focuses on developer coding sessions rather than a general application memory layer.
Do not let it capture .env files, production logs, private keys, customer records, or license-restricted code without explicit approval. Use a test repository to inspect stored fields, outbound model requests, local deletion, and any CMEM copies before expanding deployment.
Pricing
The claude-mem 13.11 core is free under Apache-2.0. Users still pay for configured model APIs, compute, storage, and operations. CMEM is a separate optional cloud service in early access, so future plans, SLA, and enterprise controls should not be treated as settled. Verify live prices, quotas, data regions, export, deletion, service termination, and support before adopting it.
Apache-2.0 permits commercial use of the project code. It does not grant extra rights to Claude, model outputs, dependencies, repository contents, customer data, or trademarks. Commercial teams must review those boundaries separately.
Pros
- Reduces repeated explanations across coding sessions.
- Apache-2.0 core and local state are inspectable.
- CMEM is optional rather than required for local operation.
- Integrates directly with Claude Code lifecycle events.
- Useful for long-running refactors, debugging, and repository conventions.
Cons
- Local storage does not make external model processing local.
- Automatic observation can retain secrets, logs, or customer data.
- CMEM is early access, with pricing and enterprise controls still subject to change.
- Install scripts and multiple runtime dependencies increase supply-chain exposure.
- Recalled memory can be stale or wrong and must be checked against source code.
- Apache-2.0 does not settle model, content, or dependency rights.
Alternatives
| Tool | Best for | Advantage | Limitation |
|---|---|---|---|
| Mem0 | AI applications that need user memory | Broader APIs and application integrations | Heavier than a Claude Code plugin |
| Context Mode | Coding agents overwhelmed by verbose tool output | Clear local compression and session continuity | Long-term semantic memory is not its primary focus |
| Claude Code | Teams preferring native project instructions | One fewer privileged plugin | Less automatic cross-session history |
| OpenCode | Developers wanting an open terminal agent | Flexible client and model choices | Memory must be designed separately |
FAQ
Is claude-mem 13.11 free and open source?
The core is free under Apache-2.0. External model APIs, infrastructure, and optional CMEM cloud service can still cost money.
Does all memory stay on the local machine?
Local state can stay on the device, but summaries, embeddings, or reasoning may be sent to the configured model provider. Review the complete configured data flow.
Does CMEM train models on customer data?
The current public commitment says no. That does not establish zero retention or zero subprocessors; early-access users should verify the current policy, deletion controls, and contract.
Can a company use it with private source code?
Only after approving plugin permissions, model providers, storage, access controls, and deletion. Do not record secrets, production data, or contract-restricted material by default.
Does Apache-2.0 make generated output commercially safe?
No. The license covers project code, not model terms, input materials, outputs, third-party components, or trademarks.
What should be checked before installation?
Confirm the official source and version, inspect the installer, pin dependencies, restrict the viewer’s bind address, scan memory for secrets, and test complete uninstall and deletion.
Bottom Line
claude-mem 13.11 adds a useful cross-session memory layer to Claude Code, and Apache-2.0 plus local state makes it more inspectable than a cloud-only black box. External model providers can still receive data, while optional CMEM introduces cloud account and retention boundaries. Validate capture, recall, deletion, and network requests on a non-sensitive repository, then compare it with Context Mode and Mem0 before production adoption.