context-memory
Persistent, searchable context storage across Claude Code sessions using SQLite + FTS5.
Table of Contents
- Why?
- Features
- Architecture
- Installation
- Uninstalling
- Requirements
- Commands
- How It Works
- Usage Examples
- Trigger Phrases
- Web Dashboard
- CLI Tools
- Database Management
- Testing
- Contributing
- License
- Author
Why?
Claude Code sessions are ephemeral - every conversation starts from zero. Close the terminal and everything you discussed, decided, and solved is gone. The only way to get that context back is to re-explain it or hope Claude reads the right files.
context-memory fixes this.
- "How did we fix that auth bug last week?" - Instead of re-debugging,
/recall authenticationpulls up exactly what you did, what you decided, and why. - Decisions have context - You chose JWT over sessions for a reason. Three months later, you can't remember why. Your past sessions can.
- Code patterns survive sessions - That elegant retry pattern you built? It's saved with the language, file path, and description of what it does.
/recall retry pattern --detailedbrings it back. - Projects you haven't touched in months -
/recall --projectscopes to whatever you're working in. Instant refresher on where you left off. - Cross-project learning - Solved a CORS issue in one project? When it hits another,
/recall CORSfinds it regardless of which project it came from. - Sub-50ms search - It's SQLite with FTS5 and tuned PRAGMAs (WAL mode, 64MB cache, in-memory temp store). Searching thousands of sessions feels instant.
- Two words to save everything -
/rememberand Claude does the rest: summarizes, extracts topics, identifies key code, stores it all. Add a note if you want, or don't.
