What is the core difference between claude-mem and Claude Code’s MEMORY.md approach?

[claude-mem](https://github.com/thedotmack/claude-mem) externalizes memory as “queryable storage + layered retrieval”: it auto-captures tool events, compresses with AI, indexes, and injects context on demand. In contrast, [MEMORY.md](https://code.claude.com/docs/en/memory) is a file-based convention where a fixed slice is loaded at session start and topic files are curated manually. The tradeoff is automation and searchability: claude-mem uses SQLite/FTS plus optional vectors and progressive disclosure to keep token costs controlled while staying highly retrievable, whereas MEMORY.md optimizes for human-maintained readability. If you care about replayable incident reproduction across many sessions, database-backed memory behaves more like infrastructure.

Why SQLite + FTS instead of appending summaries into one big document?

The issue with a big document is not storage, but retrieval, layering, and observability. SQLite lets you model sessions, observations, and summaries as indexable records, and FTS turns keyword recall into fast queries instead of scrolling and guesswork. It also creates hard boundaries for progressive disclosure: you can filter by time, session, or tool type before deciding what to inject. That keeps memory usable as volume grows, instead of becoming heavier and less reliable over time.

Do I have to enable Chroma vectors? When does it help?

No. [Chroma](https://www.trychroma.com) is valuable for semantic recall when you remember intent but not exact keywords. Enable it if you frequently search across paraphrases or want to build reusable memory snippets for recurring problem patterns. If your dominant recall path is explicit signals like error codes, filenames, or commands, FTS is often sufficient and more predictable to operate.

claude-mem deep dive: persistent memory, alt to MEMORY.md

Pain Points vs Innovation

✕Traditional Pain Points	✓Innovative Solutions
Across reconnects and multi-day work, critical context gets scattered across terminal output, issues, and personal notes, which is low-signal and hard to replay.	claude-mem captures lifecycle tool events reliably, compresses them into structured memory, and persists them so memory becomes queryable data instead of fragile chat residue.
A single memory file is either too short to keep details or too long to load safely every session, and without indexing it is painful to retrieve by symptom or task.	Hybrid retrieval combines full-text search with optional vectors, and progressive disclosure pulls only what fits the token budget; a local viewer makes the memory stream observable for tuning and debugging.

Deployment Guide

1. Install the plugin inside Claude Code

bash

1> /plugin marketplace add thedotmack/claude-mem2> /plugin install claude-mem

2. Restart Claude Code to activate hooks

bash

1exit  # then reopen Claude Code

3. Review settings and tune context injection

bash

1cat ~/.claude-mem/settings.json

4. Query your project history via the mem-search skill

bash

1Ask a natural-language query, e.g., "What bugs did we fix last session?"

5. Open the local Viewer UI to inspect the memory stream (optional)

bash

1open http://localhost:37777

Use Cases

Core Scene	Target Audience	Solution	Outcome
Multi-day continuity	solo developers	capture tool traces and decisions, then inject the right summaries next session	less rework and faster context recovery
Team handoff & review	engineering leads	compress sessions into searchable memory and inspect quality via the viewer	cheaper handoffs and more repeatable regression
Agent workflow audit	platform engineers	persist tool calls and outcomes and use hybrid search to find abnormal paths	better observability, faster debugging, fewer mistakes

claude-mem

What is it?

Pain Points vs Innovation

Architecture Deep Dive

Deployment Guide

1. Install the plugin inside Claude Code

2. Restart Claude Code to activate hooks

3. Review settings and tune context injection

4. Query your project history via the mem-search skill

5. Open the local Viewer UI to inspect the memory stream (optional)

Use Cases

Limitations & Gotchas

Frequently Asked Questions