Pages of the deja-vu documentation that changed, newest first. https://vshulcz.github.io/deja-vu/ 2026-10-12T00:00:00Z vshulcz https://vshulcz.github.io/deja-vu/ 2026-10-12T00:00:00Z

The most accurate, cheapest and fastest memory for coding agents: Claude Code, Codex and 39 more agents, built from the sessions already on your disk.

https://vshulcz.github.io/deja-vu/ 2026-10-12T00:00:00Z

The most accurate, cheapest and fastest memory for coding agents: Claude Code, Codex and 39 more agents, built from the sessions already on your disk.

https://vshulcz.github.io/deja-vu/guide/agents.html 2026-10-12T00:00:00Z

How deja gives coding agents a searchable memory over MCP: one tool with recall, context, blame, fix, how, orient, remember and handoff modes.

https://vshulcz.github.io/deja-vu/guide/claude-mem-alternative.html 2026-10-12T00:00:00Z

No model, worker or sign-in: deja-vu indexes the sessions Codex, Cursor, opencode and 32 other agents already keep, including those from before install.

https://vshulcz.github.io/deja-vu/guide/codex-history.html 2026-10-12T00:00:00Z

Where Codex CLI keeps session history, why grep misses sessions older than a week, jq and sqlite3 recipes, and search across every Codex session.

https://vshulcz.github.io/deja-vu/guide/commands.html 2026-10-12T00:00:00Z

Every deja subcommand: search, ctx, blame, fix, how, secrets, remember, forget, stats, last, sources, install, embed, sync, doctor, bench and update.

https://vshulcz.github.io/deja-vu/guide/compare.html 2026-10-12T00:00:00Z

deja-vu next to claude-mem, agentmemory, MemPalace, Mem0, Letta, CASS, ctx and agentsview: what each captures, where it keeps it, how it scores.

https://vshulcz.github.io/deja-vu/guide/context-window-full.html 2026-10-12T00:00:00Z

Compaction keeps 77% of decisions and 0.2% of commands — measured. What to do instead of paying for a window that grows until it breaks.

https://vshulcz.github.io/deja-vu/guide/credentials-in-transcripts.html 2026-10-12T00:00:00Z

Agents write every command output to plaintext transcripts. One machine held 84 credentials in 42 sessions. How to find yours, and what to do about them.

https://vshulcz.github.io/deja-vu/guide/delete-kiro-session-history.html 2026-10-12T00:00:00Z

Kiro keeps CLI and IDE sessions in two different trees under ~/.kiro/sessions. Where each one is, how to remove one session or all, and what else Kiro keeps.

https://vshulcz.github.io/deja-vu/guide/export-conversations.html 2026-10-12T00:00:00Z

How to export a conversation from Claude Code, Codex, Cursor or opencode — as markdown, as JSON, or as one local HTML page.

https://vshulcz.github.io/deja-vu/guide/find-a-session.html 2026-10-12T00:00:00Z

How to search chat history across every coding agent on the machine, by the token you remember rather than the topic you half-remember.

https://vshulcz.github.io/deja-vu/guide/getting-started.html 2026-10-12T00:00:00Z

Install deja and index your coding-agent history in one command, then search it and wire it into your agents over MCP.

https://vshulcz.github.io/deja-vu/guide/getting-started.html 2026-10-12T00:00:00Z

Install deja and index your coding-agent history in one command, then search it and wire it into your agents over MCP.

https://vshulcz.github.io/deja-vu/guide/lost-context.html 2026-10-12T00:00:00Z

A crash, a cleared window or a restart takes the agent's context but not the transcript — how to get the work back and stop paying for it next time.

https://vshulcz.github.io/deja-vu/guide/memory-for-amp.html 2026-10-12T00:00:00Z

Amp keeps every thread on the server and starts each one empty. A plugin under ~/.config/amp/plugins puts this machine's own history before the model.

https://vshulcz.github.io/deja-vu/guide/memory-for-antigravity.html 2026-10-12T00:00:00Z

Antigravity records every conversation and starts each one from nothing. deja injects matching history before each model call and indexes every agent.

https://vshulcz.github.io/deja-vu/guide/memory-for-cherrystudio.html 2026-10-12T00:00:00Z

Cherry Studio writes its agent sessions under its own app data. deja reads them, and hands the same memory to every other agent on the machine.

https://vshulcz.github.io/deja-vu/guide/memory-for-cline.html 2026-10-12T00:00:00Z

Cline's hook files cannot carry context, so deja comes as a plugin: a rule resolved as instructions are built, a message builder, runtime hooks and /deja.

https://vshulcz.github.io/deja-vu/guide/memory-for-dsh.html 2026-10-12T00:00:00Z

How to give dsh recall over the sessions every coding agent on the machine already wrote — the plugin, the tools, and how it behaves beside the CLI install.

https://vshulcz.github.io/deja-vu/guide/memory-for-hermes.html 2026-10-12T00:00:00Z

Hermes searches its own sessions and keeps MEMORY.md. deja adds the other forty agents: a plugin on pre_llm_call, the MCP tools, and a skill.

https://vshulcz.github.io/deja-vu/guide/memory-for-opencode.html 2026-10-12T00:00:00Z

How to give opencode recall over the sessions every agent on the machine already wrote — the plugin, the four moments it fires, and the CLI install.

https://vshulcz.github.io/deja-vu/guide/privacy.html 2026-10-12T00:00:00Z

deja is local by design: no network path in indexing or search unless semantic search is on, credentials redacted at index time, and forget/exclude controls.

https://vshulcz.github.io/deja-vu/guide/resume-a-session.html 2026-10-12T00:00:00Z

Find the session across every agent on the machine, then reopen it in the tool that owns it — or take the digest instead of the whole conversation.

https://vshulcz.github.io/deja-vu/guide/search.html 2026-10-12T00:00:00Z

deja search syntax: exact and phrase queries, natural language with stop words, fuzzy typo tolerance, confidence tiers, and optional local semantic recall.

https://vshulcz.github.io/deja-vu/guide/token-cost.html 2026-10-12T00:00:00Z

What memory costs in tokens, measured — and why recall is the answer to too many tokens rather than another source of them.

https://vshulcz.github.io/deja-vu/guide/delete-amp-thread-history.html 2026-10-10T00:00:00Z

Amp keeps each thread as its own JSON file, so deleting a conversation is deleting one file. Where the files are, how to remove one or all, and what you lose.

https://vshulcz.github.io/deja-vu/guide/delete-cline-task-history.html 2026-10-10T00:00:00Z

Cline has separate CLI and VS Code extension histories. Find the right store and remove one conversation without deleting unrelated task state.

https://vshulcz.github.io/deja-vu/guide/delete-codex-sessions.html 2026-10-10T00:00:00Z

How to delete Codex CLI sessions — one rollout, one day, or all of ~/.codex/sessions — and why ~/.codex/history.jsonl keeps your prompts regardless.

https://vshulcz.github.io/deja-vu/guide/delete-continue-session-history.html 2026-10-10T00:00:00Z

Continue keeps one JSON file per session plus a sessions.json list the history view reads. How to remove one session or all, and why the list has to go too.

https://vshulcz.github.io/deja-vu/guide/delete-copilot-chat-history.html 2026-10-10T00:00:00Z

Where VS Code Copilot Chat keeps conversations, how to remove one or all of them, and what goes with them.

https://vshulcz.github.io/deja-vu/guide/delete-cursor-chat-history.html 2026-10-10T00:00:00Z

How to delete Cursor chat history — where the chats live in state.vscdb, why deleting the file resets more than chats, and what the CLI writes separately.

https://vshulcz.github.io/deja-vu/guide/delete-gemini-cli-history.html 2026-10-10T00:00:00Z

Where Gemini CLI keeps chats under ~/.gemini/tmp, how to map a project id back to a directory, what to delete and what the prompt log keeps.

https://vshulcz.github.io/deja-vu/guide/delete-kilo-code-task-history.html 2026-10-10T00:00:00Z

Kilo Code keeps each task as JSON under the VS Code extension's storage, and its CLI keeps a separate SQLite store.

https://vshulcz.github.io/deja-vu/guide/delete-old-claude-sessions.html 2026-10-10T00:00:00Z

find ~/.claude/projects -mtime +30 -delete drops them, cleanupPeriodDays does it on a timer — and why age frees far less disk than size.

https://vshulcz.github.io/deja-vu/guide/delete-opencode-session-history.html 2026-10-10T00:00:00Z

opencode keeps every session in one SQLite database. What the tables hold, how to remove a session, and why deleting rows does not free the space.

https://vshulcz.github.io/deja-vu/guide/delete-roo-task-history.html 2026-10-10T00:00:00Z

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.

https://vshulcz.github.io/deja-vu/guide/harnesses.html 2026-10-10T00:00:00Z

The forty-one coding agents deja indexes today, where each stores its history, and how to add a new one.

https://vshulcz.github.io/deja-vu/guide/recover-a-deleted-session.html 2026-10-10T00:00:00Z

A Claude Code session missing from --resume: where the file went, the four reasons it moved rather than vanished, and what is actually recoverable.

https://vshulcz.github.io/deja-vu/guide/session-files-on-disk.html 2026-10-10T00:00:00Z

One session: delete its .jsonl under ~/.claude/projects. A whole project: claude project purge. On a timer: cleanupPeriodDays. What /clear and --resume do.