Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
While you work, an observer (a second agent) watches what your agent reads, edits and runs, and writes short notes about what mattered. Those notes are called observations. When a session ends, the observer writes a summary. When the next session starts, your agent gets a compact index of the observations that matter for this project and fetches full details only when it needs them.
So the next session starts where the last one left off: no re-explaining the codebase, no re-discovering decisions.
Memory injection starts on your second session in a project.
The first session seeds memory as you work. To front-load a whole repo in one pass instead, run /learn-codebase (~5 minutes on a typical repo, optional).
Your memory lives in ~/.claude-mem on this machine: the SQLite database, vector index, logs and settings. npx claude-mem uninstall removes it.
What leaves the machine:
npx claude-mem telemetry disable, or set DO_NOT_TRACK=1.thedotmack/claude-mem
ea45a39
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.