deja-vu
Local memory layer that indexes coding-agent session logs for search and MCP recall.
deja-vu is an open-source Go binary that turns existing Claude Code, Codex, OpenCode, Cursor, Gemini CLI, Grok Build, and aider histories into searchable memory. It exposes MCP recall, optional session-start auto-recall, secret redaction, and machine-to-machine sync without a hosted service or downloaded model.
Official resources
Selection advice
Quick comparison
deja-vu mines the session logs your coding agents already write. PAXM adapts memory writes and recall across providers, while Mem0 embeds memory inside application code.
| deja-vu | PAXM | Mem0 | |
|---|---|---|---|
| Best for | Searching and recalling past coding-agent sessions across harnesses | Writing and routing project memory across multiple agent clients | Embedding user memory in a shipped agent product |
| Storage model | Indexes local harness transcripts with redacted cache and optional sync | Local SQLite plus optional routed memory providers | SDK-managed memory with self-hosted and managed options |
| Integration style | CLI search, MCP recall, and install hooks into supported harnesses | CLI, MCP tools, skills, plugins, and lifecycle hooks | Python and TypeScript APIs inside application code |
| Tradeoff | Strong on retroactive session search; not a general application memory SDK | Broader write/routing model with less focus on mining existing logs | Application-friendly API with more hosting and provider setup |
Best for
- coding-agent session recall
- local-first privacy
- cross-harness MCP memory
- retroactive search over existing logs
Not ideal for
- teams that need a managed memory SaaS with hosted UI
- products that need an in-app memory SDK for end users
- workflows that never write local coding-agent transcripts
Core concepts
Minimal implementation shape
Install with `curl -fsSL https://raw.githubusercontent.com/vshulcz/deja-vu/main/install.sh | sh`, run `deja install --auto`, then search with `deja "jwt refresh rotation"` or ask the agent to use MCP `recall`.