deja-vu — Claude Code plugin: session recall and setup
deja-vu searches local transcripts from earlier coding-agent sessions and brings back relevant context. Use it when a task depends on work done before.
MIT ★ 1,645 updated 2026-10-24
/plugin marketplace add vshulcz/deja-vu
/plugin install deja-vu@deja-vuWhat deja-vu does
deja-vu builds an index from transcripts already written to disk by forty-three coding agents, including sessions created before installation. Retrieval runs locally with BM25; it uses neither a model nor embeddings, and credentials are redacted while the index is built.
The bundle contains an MCP server, the deja-history skill, the /deja command, plus hooks for session start, each prompt, context compaction, tool calls, failures, and session end. The listed platforms are Claude Code and Codex.
The native binary is separate from the bundle. Install it with brew install deja-vu or npm i -g @vshulcz/deja-vu. A separate deja install setup can coexist with the plugin because these hooks step aside when the same hooks are already wired by the installer.
What it helps with
- recover a decision from an earlier session
- search another coding agent’s session history
- restore context from before installation
- connect the current task with earlier transcripts
Example prompts for the agent
- Run
/dejaand find the earlier session that fixed this authentication error. - Use
/dejato tell me what we changed in this project and why. - Recall the previous session about this error and summarize its conclusion.
How to install deja-vu
Plugin marketplace
/plugin marketplace add vshulcz/deja-vu/plugin install deja-vu@deja-vuStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about deja-vu
How do I install deja-vu in Claude Code?
Run /plugin marketplace add vshulcz/deja-vu, then run /plugin install deja-vu@deja-vu. Install the separate binary with brew install deja-vu or npm i -g @vshulcz/deja-vu.
What does deja-vu do?
It searches a local index of transcripts from coding-agent sessions and returns matching context. Retrieval uses BM25 without a model or embeddings.
Does deja-vu need a separate binary?
Yes. The binary is outside the plugin bundle; install it with brew install deja-vu or npm i -g @vshulcz/deja-vu.
Source text
claude-plugin · MIT
# deja for Claude Code The plugin bundle Claude Code, Qwen and OpenClaw install from this repository's marketplace. Cursor has its own, in [`cursor-plugin/`](../cursor-plugin/). Copilot CLI installs it too but takes only the skill (no hooks, no MCP server); `deja install copilot-auto` wires those: ```sh claude plugin marketplace add vshulcz/deja-vu && claude plugin install deja-vu@deja-vu ``` It carries deja's MCP server, the `deja-history` skill, the `/deja` command and the session-start, per-prompt, pre-compact, pre-tool, post-failure and session-end hooks — the same wiring `deja install --auto` writes, packaged the way those harnesses install things. [deja](https://github.com/vshulcz/deja-vu) indexes the session transcripts forty-three coding agents already write to disk, including sessions from before it was installed, and answers from them locally: BM25 over the transcripts, no model and no embeddings, credentials redacted as the index is built. The binary is not in the bundle — plugins carry files, not native binaries: ```sh brew install deja-vu ``` or ```sh npm i -g @vshulcz/deja-vu ``` Having both this bundle and `deja install` is fine: the hooks here stand down when the installer has already wired the same ones, so nothing is recalled twice. Details, the harness matrix and the benchmarks are in the [repository README](../README.md). Security policy: [SECURITY.md](../SECURITY.md). MIT, same as deja.
© vshulcz · MIT · vshulcz/deja-vu