deja-vu: recall over the sessions Codex and 23 other agents already wrote to disk

[vshulcz]

deja-vu is a small Go binary that reads the session files your coding agents already keep on disk — Codex's ~/.codex/sessions rollouts, Claude Code, Cursor, opencode, Amp, and about twenty others — into one local index, and gives Codex recall over all of it. So the fix you found in Claude Code last month comes back in Codex today, with the date and the session it came from. No model, no key, nothing leaves the machine.

For Codex specifically:

• deja install codex wires the MCP server (deja tool with recall / context / blame / fix / how / remember modes).
• deja install codex-auto adds hooks to ~/.codex/hooks.json: a project digest on SessionStart, the matching session on every prompt, and after a compaction what was thrown away — measured on codex 0.149.0 by reading what actually reaches the model.
• There is also a plugin (codex-plugin/ in the repo) with the same hooks and a skill, for the marketplace install path.

What it does differently from the memory tools that record forward: it starts full. On a machine with 19k sessions already on disk it indexes in about 30 seconds; the comparison with agentmemory, MemPalace, Hugging Face's funes and others, on the same corpus, is here: https://vshulcz.github.io/deja-vu/guide/day-zero.html

Repo: https://github.com/vshulcz/deja-vu — Codex guide: https://vshulcz.github.io/deja-vu/guide/memory-for-codex.html

Happy to hear what breaks. Codex is the harness where I'd most like more eyes on the hook payloads.