Déjà Vu for Codex Local Session History Search
Look up decisions, errors, and commands from coding sessions already saved on your machine. The Codex plugin uses the local deja index and can query retained sessions from Codex, Claude Code, and the other supported clients.
中文Install in Codex 插件，检索本地 Codex 和 Claude Code 会话
A Codex CLI with plugin support and a local `deja` binary that can read the test user’s session directories. Windows binaries are available through Scoop or winget. Building this pinned source uses Go 1.25. The keyword example needs no external embedding service.
- Install the `deja` binary using a method in the upstream README, such as `winget install vshulcz.deja-vu` on Windows. Go 1.25 is required for a source build of this revision.
- In Codex CLI, run `codex plugin marketplace add https://github.com/vshulcz/deja-vu`, then `codex plugin add deja-vu@deja-vu`. Start a fresh test session.
- Run `deja index` in a test user environment with synthetic sessions. Use `deja recall` from a terminal to check the same local index directly.
Example task
Create a session for a fictitious project under a dedicated test user. In that session write down that `demo-receipt.txt` exports the test label `fixture-copper-452`. Close that session, update the index, then run this command from the same demo project.
deja recall "fixture-copper-452"What to check
The query finds a previous demo session and includes the synthetic label in the context. If the history is missing, verify that you are using the same local user and the test session was indexed.
Original SKILL.md on GitHub · Updated
Frequently asked question
Does the plugin upload my coding history to cloud storage?
The documented default builds a local index. Ordinary keyword lookup needs neither an LLM call nor a cloud account. Since it reads logs accessible to the OS user, a dedicated test account is useful for checking just synthetic history.