deja-vu

项目详情摘要

Your coding agents stop re-debugging what you already fixed. Claude Code, Codex, Cursor and 35 more agents already save every session to disk. deja indexes all of it, months back, and hands the part that matters to whichever agent is working now. English | 简体中文 | 繁體中文 | 日本語 | 한국어 | Español | Português | Français | Deutsch | Русский | Türkçe | हिन्दी Nobody searched anything — the agent called deja itself. Two real runs against a synthetic corpus: nobody's history is published. macOS and Linux; ten seconds to install, about ten to index · Windows, Homebrew, npm and the rest Recall 97.2% R@5 on LongMemEval-S MemPalace publishes 96.6%, agentmemory 95.2% Tokens half the tokens of agentmemory on a task this machine had already solved Index time 17.6 s to index 19,195 sessions the next of seven tools takes 72 s I maintain deja-vu, so every driver, the corpus and the scoring rule are in this repository · the head-to-head, and how to re-run a row you doubt · every run Docs · Benchmarks · How it compares · Building it into your tool Found it useful? Star deja-vu on GitHub . Highlights **Starts full.** Months of history from before you installed it are searchable on day one: `deja "connection pool exhausted"` over gigabytes. **One memory, every agent.** A fix found in Codex comes back in Claude Code, Cursor or opencode; all forty-one agents read the same index. **Nobody has to ask.** Recall arrives at session start, before a file is edited or a command runs, and after a command fails. **Survives compaction.** Over 43 measured compactions the summary kept 77% of the decisions and 0.2% of the commands; deja hands back the rest (how). **Indexes the work, not just the talk.** The files each turn opened, the commands with their exit status, th