CodeariaAcademy
GitHub repositorycommit this monthDevelopmentAutomation

claude-mem

102k

Automatic memory between Claude Code sessions. One command to install, then it stays out of the way.

We have not run it ourselves: described from the docs and the repository.

In numbers

Claude Code lifecycle points
layers of memory search
licence, fine for commercial products
required Node.js version

What it is

claude-mem is a Claude Code plugin that carries context across sessions. A terminal session ends and everything you explained about the project goes with it: the next morning you start over with what the stack is, what you did yesterday and why that file must not be touched. This plugin closes exactly that gap.

It records on its own which files were opened, what got fixed and what you decided, and at the start of the next session it feeds back whatever is relevant. The most interesting part is that token cost was thought through in advance: instead of dumping everything it finds into the context, the search works in layers and hands over full detail only for the entries you picked. No cloud, the whole memory stays on your machine.

How it works

hooks
Attaches to session start, prompt submitted, tool call, stop and session end, and records observations at those points.
summaries
At the end of a session it compresses the record into short summaries and feeds the relevant ones into the next session.
SQLite + Chromalocal
SQLite as an ordinary file on disk and a Chroma vector database for search by meaning, without exact wording.
web UIlocal
A local HTTP service with a web interface for browsing the memory, plus a separate skill for questioning it in plain language.
3-layer search
A compact list of results first, then a timeline around whatever looks interesting, and only then full detail on the picked entries.

Know before installing

npm install -g claude-mem completes without errors but installs only the library: the hooks are never registered and the memory never works. Install through npx claude-mem install or from the plugin marketplace; the plugin pulls in Bun and uv itself.
Observations are written to disk in the clear. Weigh that if you work with someone else's credentials or with personal data.

Comments