deja vu changelog

version

0.24.1 → 0.24.2

version

0.24.0 → 0.24.1

file

absent → published

https://vshulcz.github.io/llms.txt

+ # deja-vu+ > deja-vu (`github.com/vshulcz/deja-vu`, CLI `deja`) is an open-source local memory and session-history search tool for coding agents, built as a single Go binary from the session transcripts agents already write to disk. deja indexes what Claude Code, Codex, Cursor, opencode, Gemini CLI, Qwen Code, Crush, Zed and thirty-five more agents wrote on this machine — including the months before it was installed — and answers from them over MCP, hooks, the command line, or a full-screen search in the t+ Two things distinguish it from memory tools that record forward: it starts full, because the history is already on disk, and recall arrives without being asked — at session start, on each prompt, before an edit or a command, after a command fails, and on the way back from a compaction, where deja keeps the task, files and commands the summary drops. Credentials are stripped as the index is built.+ Install is one command (`curl -fsSL https://raw.githubusercontent.com/vshulcz/deja-vu/main/install.sh | sh`, or `brew install deja-vu`), followed by `deja install --auto` to wire the agents found on the machine.+ Run `deja` with no arguments in a terminal and it opens a full-screen search over every agent's history: results as you type, the session read at the match, then `r` to resume it in its own agent or `o` to continue it in another with what it asked, decided and left open. The box takes filters (`codex:`, `yesterday`, `in:<project>`), `/` finds a word inside an open session, and a Deleted tab holds sessions their agent deleted that deja still has, and puts one back where the agent can reopen it. W+ ## Start here+ - [Getting started](https://vshulcz.github.io/deja-vu/guide/getting-started.html): install, wire an agent, and the first query+ - [Why agents forget](https://vshulcz.github.io/deja-vu/guide/forgetting.html): what ends with a session and what survives on disk+ - [Does my agent remember previous conversations](https://vshulcz.github.io/deja-vu/guide/does-my-agent-remember.html): what Claude Code, Codex and Cursor keep between sessions, and what they do not+ - [Where history lives](https://vshulcz.github.io/deja-vu/guide/where-sessions-are-stored.html): the conversation history file each of the forty-three agents writes, and its format+ - [Credentials in transcripts](https://vshulcz.github.io/deja-vu/guide/credentials-in-transcripts.html): coding agents record command output verbatim, so keys and connection strings sit in plaintext transcripts; how to find them with deja secrets and what to do+ - [Session files on disk](https://vshulcz.github.io/deja-vu/guide/session-files-on-disk.html): how to delete Claude Code sessions, how large ~/.claude/projects gets, what is inside a session file, and what deleting one costs+ - [Delete Cline task history](https://vshulcz.github.io/deja-vu/guide/delete-cline-task-history.html): distinguish the modern CLI session store from the VS Code extension task tree and remove only the conversation data you intend to delete+ - [Delete Roo Code task history](https://vshulcz.github.io/deja-vu/guide/delete-roo-task-history.html): Find Roo Code history across editor hosts and custom storage. Delete one task or all tasks, understand what is lost, or keep the history searchable.+ - [Delete Zed agent thread history](https://vshulcz.github.io/deja-vu/guide/delete-zed-thread-history.html): Find Zed agent threads in threads.db, delete one through the history view, or remove the built-in agent database with Zed closed. Know what is lost.+ - [Delete Kiro session history](https://vshulcz.github.io/deja-vu/guide/delete-kiro-session-history.html): the CLI writes a transcript and header pair per session and the IDE a directory per session under ~/.kiro/sessions; remove the right one, and check the globalStorage and TUI copies that tree does not cover+ - [Delete Kimi Code session history](https://vshulcz.github.io/deja-vu/guide/delete-kimi-code-session-history.html): one directory per session under ~/.kimi-code/sessions; remove the whole directory, since state.json alone still lists a session+ - [Delete Junie session history](https://vshulcz.github.io/deja-vu/guide/delete-junie-session-history.html): each session is a directory under ~/.junie/sessions; remove the session directory, and understand that index.jsonl retains metadata and logs+ - [Delete Goose session history](https://vshulcz.github.io/deja-vu/guide/delete-goose-session-history.html): since 1.10.0 every session is a row in sessions.db; remove one with goose session remove, and delete the legacy JSONL files goose no longer manages yourself+ - [Delete Windsurf Cascade history](https://vshulcz.github.io/deja-vu/guide/delete-windsurf-cascade-history.html): one encrypted .pb file per conversation under ~/.codeium/windsurf/cascade; find the file, delete one or all, and leave the rules, MCP config and settings beside it alone+ - [Delete Qwen Code chat history](https://vshulcz.github.io/deja-vu/guide/delete-qwen-code-chat-history.html): one JSONL file per session under ~/.qwen/projects/<project>/chats, plus its sub-agent logs; delete one or all and leave settings alone+ - [Delete Amp thread history](https://vshulcz.github.io/deja-vu/guide/delete-amp-thread-history.html): one JSON file per thread under ~/.local/share/amp/threads, so deleting one conversation is deleting one file; the thread in your Amp account is separate+ - [Delete Continue session history](https://vshulcz.github.io/deja-vu/guide/delete-continue-session-history.html): one JSON file per session plus a sessions.json list the history view reads; remove the entry with the file, or the session stays listed and cannot be deleted from Continue+ - [Delete pi session history](https://vshulcz.github.io/deja-vu/guide/delete-pi-session-history.html): each session is a single JSONL file under ~/.pi/agent/sessions; delete one file or a whole project directory, or use deja delete with dry-run preview+ - [Delete old Claude Code sessions](https://vshulcz.github.io/deja-vu/guide/delete-old-claude-sessions.html): `find ~/.claude/projects -mtime +30 -delete` or `cleanupPeriodDays`, and why age frees far less disk than size+ - [Delete Codex CLI sessions](https://vshulcz.github.io/deja-vu/guide/delete-codex-sessions.html): one rollout, one day, or all of ~/.codex/sessions, and why ~/.codex/history.jsonl keeps your prompts regardless+ - [Delete CodeBuddy and WorkBuddy session history](https://vshulcz.github.io/deja-vu/guide/delete-codebuddy-sessions.html): one JSONL per session under ~/.codebuddy/projects and the sub-agent directory beside it; WorkBuddy keeps its own copies in its own homes+ - [Delete Antigravity conversation history](https://vshulcz.github.io/deja-vu/guide/delete-antigravity-history.html): a conversation is six things under ~/.gemini/antigravity, not just its brain directory; use the app's Delete, then VACUUM conversation_summaries.db, which still holds the deleted text+ - [Delete Cursor chat history](https://vshulcz.github.io/deja-vu/guide/delete-cursor-chat-history.html): where the chats live in state.vscdb, why deleting the file resets more than chats, and what the CLI writes separately+ - [Cursor state.vscdb too large](https://vshulcz.github.io/deja-vu/guide/cursor-state-vscdb-too-large.html): which chats fill a 30–125 GB state.vscdb, shrinking it safest first, and keeping the chats you delete searchable+ - [Delete Gemini CLI chat history](https://vshulcz.github.io/deja-vu/guide/delete-gemini-cli-history.html): chats under ~/.gemini/tmp, mapping a project id back to a directory, and what the prompt log keeps+ - [Delete opencode session history](https://vshulcz.github.io/deja-vu/guide/delete-opencode-session-history.html): one SQLite database, what its tables hold, and why deleting rows does not free the space+ - [Delete VS Code Copilot Chat history](https://vshulcz.github.io/deja-vu/guide/delete-copilot-chat-history.html): where the conversations are kept and what goes with them+ - [Delete Copilot CLI session history](https://vshulcz.github.io/deja-vu/guide/delete-copilot-cli-session-history.html): one directory per session under session-state, found by the id in events.jsonl rather than the directory name+ - [Delete Kilo Code task history](https://vshulcz.github.io/deja-vu/guide/delete-kilo-code-task-history.html): task JSON under the extension's storage, and the CLI's separate SQLite store+ - [CLI reference](https://vshulcz.github.io/deja-vu/guide/commands.html): every command and flag+ - [Agents & MCP](https://vshulcz.github.io/deja-vu/guide/agents.html): the deja MCP tool and its modes, and what each harness supports+ ## Problems it answers+ - [The agent lost the context you had](https://vshulcz.github.io/deja-vu/guide/lost-context.html): after a crash, a clear, or a restart+ - [The context window is full](https://vshulcz.github.io/deja-vu/guide/context-window-full.html): what compaction keeps (77% of decisions, 0.2% of commands, measured) and what to do instead

Showing the first 40 of each.

version

0.23.5 → 0.24.0

version

0.23.3 → 0.23.5

version

0.23.2 → 0.23.3

version

0.23.1 → 0.23.2

description

deja-vu: local memory over the session histories of forty-two coding agents. → deja-vu: local memory over the session histories of forty-three coding agents.

version

0.23.0 → 0.23.1

version

0.22.2 → 0.23.0

description

deja-vu: local memory over the session histories of forty-one coding agents. → deja-vu: local memory over the session histories of forty-two coding agents.

version

0.22.1 → 0.22.2

version

0.22.0 → 0.22.1

description

deja-vu: local memory over the session histories of thirty-eight coding agents. → deja-vu: local memory over the session histories of forty-one coding agents.

version

0.21.7 → 0.22.0

description

deja-vu: local memory over the session histories of thirty-five coding agents. → deja-vu: local memory over the session histories of thirty-eight coding agents.

version

0.21.6 → 0.21.7

version

0.21.5 → 0.21.6

version

0.21.4 → 0.21.5