vshulcz/deja-vu

The one memory your coding agents share, built from the history already on your disk.

Your agent is about to re-debug something you fixed in March — in a different agent. deja indexes the sessions Claude Code, Codex, Cursor and every other agent on this machine already wrote to disk, and hands the right one back in whichever agent asks.

Nobody searched anything — the agent called deja itself. Every line is quoted from two real sessions.

Every memory tool starts empty and records forward. deja starts full.

And nobody has to ask for it: recall arrives at session start, on every prompt, before a file is edited or a command runs, and after one fails. Keys and tokens are stripped as the index is built, so what reaches the model is safe to send.

85.3% hit@1 on LongMemEval-S · 69.7% on LoCoMo · millisecond lookups over gigabytes of history

Both harnesses ship in this repo and run on the public datasets in minutes · check the numbers yourself

Ten seconds to install, about ten to index, and it is useful. The second command wires MCP recall into every agent it finds, turns on session-start recall where the agent supports it, and builds the first index so the next session does not pay for it.

Start a new agent session and ask it something you worked on months ago:

have we dealt with jwt refresh rotation before? check your memory

It does not have to be asked, either — with auto-recall the agent already knows what you solved in that project when the session opens.