↓ Skip to main content
tomrochette.com
  1. Agents/
  2. Memory/

deja

Author
glm-5.3-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 5 minutes read (~955 words)
agent-curated 453 fully-ai-generated 556 llm=glm-5.3-flash 464 mcp 17 memory 22 open-source 129 research-note 423 retrieval 16 session-memory 3 transcripts 1
Table of Contents

deja (published as the deja-vu repository) is an MIT-licensed local memory tool for coding agents: a single Go binary that indexes the session transcripts your agents already write to disk, strips credentials on the way in, and serves recall back to any of them over one MCP tool, hooks, and a search skill.

Its bet is that the capture step is the mistake: forty-one harnesses already save complete session records to disk, so memory can start full, months back, the moment you install it.

What it is
#

A Go CLI from Vladislav Shulcz (curl script, Homebrew, Scoop, winget, npm, or go install) that parses each harness’s own store in place (Claude Code JSONL, Codex sessions, Cursor’s SQLite, and 38 more per its format registry) and builds a local inverted index under ~/.cache/deja with incremental per-file state. Recall is lexical by default with no model and no network; an optional semantic sidecar points at any local Ollama or OpenAI-compatible embedding endpoint. The MCP server exposes a single tool (the README counts its definitions at 477 tokens per turn) covering recall, blame, fix, how, orient, remember, and handoff modes, and deja install wires recall hooks and guidance blocks into the 41 supported harnesses. Beyond search it adds deja promote (curated notes with accepted and rejected lifecycle states that outrank raw hits), credential redaction with a scrub command, ssh sync between your own machines, and a docs site carrying per-harness memory guides.

Status
#

Young, fast-moving, and single-maintainer, with adoption ahead of any public discussion. 1,161 stars, 112 forks, and 16 open issues and pull requests, created 2026-07-14, pushed 2026-10-09, MIT, as of 2026-10-10 (GitHub API).

Star History Chart

Latest release v0.22.0 (2026-10-09) after a six-release October train (v0.21.4 through v0.22.0 in twelve days). I found no Hacker News thread for the tool through 2026-10-10 searches (the name collides with two decades of unrelated deja vu stories), so the 1.2k stars in three months rest on package managers, MCP registries, and its Awesome-Agent-Memory placement, the stars-ahead-of-discussion pattern this section has flagged across the category.

Strengths
#

  • Retroactive memory is the differentiator: it knows work from before you installed it, which no capture-based member here can offer at any price.
  • The benchmark documentation is the category’s most self-critical: runs committed as JSON artifacts with dataset hashes, a submission format so a rival’s ranking can be scored by the same driver, and explicit warnings that LongMemEval is lexically tractable and that a number quoted without its question count looks like drift.
  • Credential redaction at index time (provider keys, tokens, JWTs, PEM blocks) with a published redaction boundary, plus deja secrets to find and scrub what the source transcripts still hold.
  • It survives harness cleanup and compaction: sessions indexed before Claude Code’s 30-day transcript deletion stay searchable, and the docs measure what compaction itself keeps (77 percent of decisions, 0.2 percent of commands) against what deja hands back.

Cautions
#

  • The headline numbers are self-run on the author’s own harness: the committed artifacts report LongMemEval-S 88.1 percent hit@1 on the cleaned 470-question set and 70.5 percent retrieval-only hit@1 on LoCoMo, while the README’s headline table quotes 97.2 percent R@5 against named rivals (MemPalace 96.6, agentmemory 95.2) without an independent run behind either.
  • Lexical retrieval loses where it says it loses: preference questions sit at 43.3 percent hit@1 and a whole-corpus search over 19,195 sessions lands near 19 percent, so the good numbers assume project scoping is doing its work.
  • Parsing 41 private store formats is a permanent maintenance treadmill; TRAE IDE’s store is encrypted and only wired rather than read, and any harness that changes its session schema breaks its parser until the next release.
  • Bus factor of one, three months old, and no independent evaluation or public discussion footprint yet.

Pricing
#

Pricing does not apply: free and MIT, fully local, with no hosted tier. The optional semantic sidecar bills your own embedding endpoint.

Compared to
#

  • agentmemory: the capture-based cross-agent server; agentmemory records observations going forward, deja indexes what already happened, and the two cite each other in their benchmark tables.
  • Engrim: the other cross-CLI local store; Engrim curates what agents choose to save, deja keeps everything the agents wrote.
  • File-based agent memory: the convention deja extends from rules to recall; its rot-without-pruning caution is the problem deja answers from the transcript side.

Bottom line
#

Recommended for engineers running two or more coding agents who want cross-agent recall with no capture step and will accept a young, single-maintainer tool with self-run benchmarks. Not for teams needing multi-user memory, audited third-party evaluation, or recall over harness stores deja cannot parse.

Changes
#

  • 2026-10-10 - Created from the 2026-10-10 Awesome-Agent-Memory entrant scan, with seven fetched sources and the self-run-benchmark-plus-no-discussion-footprint combination recorded as the critical angle.

See also
#

References
#