How DeepSeek Harness loads deja-vu
DeepSeek Harness installs deja-vu as a plugin. The plugin exposes six tools: deja_recall, deja_session, deja_blame, deja_fix, deja_how and deja_remember. It also provides the /deja command. Automatic recall is optional and can add search results to the runtime context. Recall can occur at session start, before a file is edited or a command runs, and after a command fails.
deja-vu’s data and index
deja-vu reads session files written by supported coding agents on the local machine, including Claude Code, Codex, Cursor, VS Code Copilot Chat, opencode, OpenClaw, Hermes, Kimi, Cline and Zed. The index includes sessions from before installation. Search uses a local BM25 index; the README states that deja-vu uses no LLM, no vector embeddings and no network connection. The README also says keys and tokens are stripped while the index is built.
Commands
Running deja without arguments opens an interactive search over indexed history. It initially searches sessions related to uncommitted changes, then recent sessions in the current project. Search filters include an agent prefix such as codex:, time filters such as today, yesterday, week and month, and in:<project>. deja brief prints a text summary. Setting DEJA_TUI=0 disables the interactive interface and selects text output.
The terminal search can open a session at a match, move between matches, resume it in its original agent, or continue it in another agent. It can also show deleted sessions retained by deja-vu and restore one. The README documents deja sync ssh laptop for moving an index between machines and deja handoff --to codex for continuing work in another agent.
Platforms and access
The README describes the standalone Go binary as available on macOS, Linux and Windows. deja-vu reads local agent history and exposes that indexed material through DeepSeek Harness tools and terminal commands, so installation grants those surfaces access to the session data available on the machine.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub