claude-mem: memory that carries across sessions
Each new Claude Code session starts fresh. claude-mem remembers what happened before (decisions, fixes, files touched) so you can pick up where you left off and ask about past work.
What’s inside: skills, hooks, MCP server. Published by: a third party, thedotmack/claude-mem.
How it works
Hooks watch the session: they capture your prompts and Claude’s tool use, and a local background worker turns them into short "observations" stored in a database on your machine.
At the next session start, a hook injects a summary of recent relevant work. Its MCP tools (search, timeline, get_observations) let Claude look further back when you ask.
Install
/plugin marketplace add thedotmack/claude-mem
/plugin install claude-mem@thedotmackclaude plugin marketplace add thedotmack/claude-mem
claude plugin install claude-mem@thedotmackSkip the first line if you already added the thedotmack marketplace. Reload the VS Code window or restart claude afterwards. New to plugins? See the install guide in this series.
How to use it
It runs in the background. Ask about past work in plain words. Skills such as mem-search, timeline-report, make-plan and do are there when you want them.
- How did we fix the login redirect last time?
- What did we decide about caching last week?
- Give me a timeline report of this project
Good use cases
- Picking work back up after a break
- Recalling why something was built a certain way
- Long-running projects with many sessions
When not to use it
Facts every contributor needs. Put those in the repo (a CLAUDE.md, docs or code comments) where everyone can see them, not in your personal memory.