Agent-Memory vs deja-vu
Persistent memory for coding agents compared
Agent-Memory and deja-vu help coding agents reuse context from earlier work across sessions and tools. Agent-Memory captures session activity in the iii engine, while deja-vu indexes existing agent history stored on disk and provides local search and recall.
Agent-Memory: Persistent Memory for AI Coding Agents on iii
Agent-Memory adds persistent, searchable memory to coding agents through the iii engine, sharing context across Claude Code, Cursor, Gemini CLI, Codex CLI, and other MCP or HTTP clients. It captures session activity and retrieves relevant context for later work.
deja-vu: Search Coding-Agent History for Reusable Memory
deja-vu is a Go-based local memory tool that indexes existing session history from Claude Code, Codex, Cursor and 39 more coding agents. It provides search, MCP recall and hooks without requiring an LLM, so agents can reuse earlier decisions and fixes.
| Agent-Memory | deja-vu | |
|---|---|---|
| Language | — | Go |
| License | Apache-2.0 | MIT |
| Stars | 9 | 1.2k |
| Forks | 4 | 128 |
| Last analyzed | Nov 1, 2026 | Oct 19, 2026 |
Key differences
- Agent-Memory captures prompts, tool activity, and session events through hooks; deja-vu indexes existing session files, with incremental updates.
- Agent-Memory combines keyword, vector, and graph retrieval with memory tiers; deja-vu offers lexical search without an LLM and optional semantic recall through an embeddings endpoint.
- Agent-Memory runs on Node.js 20 or later and the iii engine; deja-vu is a Go binary, with Go 1.25 and Node.js 18 or later listed as requirements.
- Agent-Memory is licensed under Apache-2.0; deja-vu is licensed under MIT.
- Agent-Memory includes a web viewer, team memory, provenance, and snapshots; deja-vu includes terminal search, credential-pattern redaction, handoff, and index transfer.
- Agent-Memory is described as quiet, with no commits in the last 90 days; deja-vu has frequent commits and releases, though contributions to both projects are concentrated among a small number of people.
Choose Agent-Memory if you…
- need to capture session activity automatically and retrieve it through keyword, vector, and graph search.
- want memory organized into tiers, with a web viewer and team memory features.
- use the iii engine and can plan around its Node.js runtime and engine compatibility requirements.
Choose deja-vu if you…
- want to index existing session history across many coding agents without requiring an LLM for search and recall.
- need a local CLI or terminal interface, MCP recall, and hooks for bringing prior context into sessions.
- want tools for credential-pattern redaction, session handoff, or moving an index between machines.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.