Deja Vu
Deja Vu is an open-source Go command-line tool that indexes local coding-agent session histories and lets users search or recall prior work across Claude Code, Codex, and OpenCode. It can also expose recall through MCP and inject relevant context at session start.
Coding-agent sessions often repeat investigations because useful context is buried in old transcripts. Deja Vu makes those histories searchable without requiring a hosted memory service, but users still need to understand local-data boundaries, secret redaction, optional sharing or sync, and platform maturity.
The vshulcz/deja-vu repository, documentation, and releases describe install, search, MCP, recall, privacy, redaction, sharing, sync, and platform support. Community launch discussion can surface practical questions about recovering prior agent work, but it is not independent security proof.
- Search earlier Claude Code, Codex, and OpenCode sessions.
- Recall prior debugging or implementation decisions at session start.
- Expose local agent-history search through MCP.
- Share a deliberately selected session after reviewing redaction and network boundaries.
Deja Vu scans supported local session histories, builds a lexical index, and lets users search prior conversations from the terminal. Its MCP server and session-start integration can surface relevant earlier work before a coding agent repeats the same investigation.
The repository says indexing and search stay local and include secret redaction. Sharing, statistics, and sync are explicit features with different data boundaries, so teams should review each command before enabling it and should not equate local search with every optional networked workflow.
Deja Vu ships Windows builds, but its documentation says macOS and Linux are the battle-tested platforms. Teams should also verify session-path coverage, repository exclusion needs, redaction behavior, index storage, and whether lexical recall is sufficient for their history volume.
Session recall is part of the state and handoff layer around coding agents.
Historical sessions are useful evidence only when their provenance and boundaries remain visible.
Local history, MCP access, redaction, sharing, and sync need explicit permission boundaries.
Deja Vu FAQ
Page-level questions for Deja Vu.
Does Deja Vu upload coding-agent sessions?+
The repository says indexing and search run locally without network access. Optional sharing, statistics, or sync commands have separate network boundaries, so review the exact command and redaction behavior before using them with sensitive histories.
Which coding agents does Deja Vu support?+
The project documents local history support for Claude Code, Codex, and OpenCode. Verify the current repository documentation if your client changes its session path or storage format.
Does Deja Vu work on Windows?+
The project publishes Windows builds, while describing macOS and Linux as the battle-tested platforms. Windows users should verify local session discovery, path handling, MCP startup, and redaction before relying on it for routine recall.