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 supported harnesses, including Claude Code, Codex, OpenCode, Cursor, DeepSeek Harness, Oh My Pi, Zed, and Copilot CLI. It can expose recall through MCP, inject relevant context around prompts and tool failures where hooks exist, and optionally keep multiple machines synchronized.
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.
Checked October 14 against the official stable v0.22.1 release. Historical release chapters retain their original scope; publisher fixes are not independent runtime validation.
- 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 exposes search and recall through the CLI or supported integrations. History parsing, automatic hooks and MCP support vary by harness; format coverage is not proof every integration has the same capabilities.
Historical release context: this section describes the earlier release. The current release checkpoint appears on this page. The September 22 release adds deja secrets to find transcript credential locations without printing secret values, supports --year on recap, tests and stats, expands blame and harness coverage, and updates OpenCode 2.0 compatibility. Finding a secret location is not proof it has been rotated or removed; review and remediate the owning credential separately.
The repository says indexing and search stay local and include secret redaction. Version 0.15.7 says the recall kill switch and policy now bind every recall path. 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 documents history discovery across supported harnesses, but MCP and automatic-recall support differ by client. It ships Windows builds while describing macOS and Linux as the battle-tested platforms. Teams should verify session-path coverage, project and store exclusions, redaction behavior, index storage, sync boundaries, and whether lexical recall is sufficient for their history volume.
The October 6 release adds proactive recall of past decisions before code, configuration, dependency and schedule changes. It fixes over-filtered own-session results and directory matching, and adds TRAE, CodeBuddy, WorkBuddy and Muse Code formats. The index schema advances to 67 and rebuilds once after upgrading. TRAE IDE’s encrypted chats are not indexed; its hooks require the app setting to be enabled.
The October 12 stable release reads a session back with the code its edit calls changed, adds deja resume --app for Codex in the ChatGPT app, and expands TUI searching and filters. Index version 70 triggers a rebuild. Release notes also describe crash/concurrency, denied-edit, redaction and harness-reader fixes. These are publisher-described changes, not proof every client or privacy boundary works in your installation.
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
Common questions about 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 release documents formats including Claude Code, Codex, OpenCode, Cursor, Hermes, TRAE, CodeBuddy, WorkBuddy and Muse Code. History parsing, MCP and automatic recall differ by client; TRAE IDE encrypted chats are not indexed.
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.