/deja
Search this machine's past AI coding sessions (deja-vu)
> /plugin marketplace add vshulcz/deja-vu > /plugin install deja-vu@deja-vu
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/deja
Context preview
What this command does when you run it.
Search this machine's past AI coding sessions (deja-vu)
Command definition
deja.mdname: deja description: Search this machine's past AI coding sessions (deja-vu)
Search the user's own past sessions across every AI coding tool on this machine, then answer from what you find.
Run the recall tool with the user's words as the query — the most specific tokens win (an exact error string, a function name, a file path, a flag). If a result looks right but is too short to act on, follow up with recall_context using a term from it.
If the deja MCP tools are unavailable, fall back to the CLI:
deja "$ARGUMENTS"
Answer with what actually happened in those sessions — when it was, which project and tool, what was decided or fixed. Say plainly if nothing matched rather than filling the gap from general knowledge.
Your agents already solved this. deja finds it — it indexes the sessions your coding agents already wrote to disk, months of history from before you installed it, and recalls them automatically at session start across seventeen harnesses. 84.9% hit@1 on LongMemEval-S, no LLM, no embeddings. One zero-dep binary, fully local.