vshulcz/deja-vu
Related Servers
Alternatives to vshulcz/deja-vu
- AlicenseBqualityCmaintenanceA fully local persistent memory layer for LLM coding agents (Claude Code, Codex, Gemini CLI, OpenCode). A shell wrapper intercepts tool invocations, fires hooks on every tool call, then runs a 3-layer pipeline (extract → compress to ≤500-token digest → merge into project memory doc) at session end. The next session gets prior context injected automatically.65 npmMIT
Related Servers
- FlicenseNot gradedqualityBmaintenanceLocal semantic search over Claude Code sessions and shell command history, exposed to Claude Code as an MCP tool. Everything is indexed into one vector space and runs entirely on your machine.2-
- FlicenseNot gradedqualityBmaintenanceLocal-first memory for AI coding agents. Indexes your Claude Code, Codex, Cursor, Cline and Gemini CLI history by repo/branch/worktree and hands a context capsule (decisions, touched files, next steps) to the next agent over MCP.-
- AlicenseBqualityCmaintenanceProvides local, agentic semantic recall over Claude Code session history, enabling the agent to search past discussions semantically, expand turns, and grep transcripts.512MIT
- AlicenseNot gradedqualityDmaintenanceLocal memory search for Codex and Claude Code conversations. It keeps history on your machine, builds a local graph index, and returns compact evidence from past sessions.5MIT
- AlicenseAqualityAmaintenancePersistent local memory for Claude Code that indexes every session's JSONL file verbatim into SQLite + ChromaDB. Exposes 17 MCP tools for semantic recall, deterministic file replay, and fuzzy "do you remember when..." queries across your entire session history — no API calls, nothing leaves the machine.17234 PyPI14MIT
- AlicenseAqualityCmaintenancePersistent memory + FTS5 full-text search for Claude Code conversation history. Indexes ~/.claude/projects/ JSONL into SQLite, exposes 10 MCP tools (store/recall/search memories, browse sessions, get summaries) plus prompts. Includes a web UI for visual exploration1042 npm93MIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong tool. The internal modes are clearly described with specific triggers and use cases.
With a single tool named 'deja', there is no naming convention to violate. The name is short, memorable, and fits the server's purpose.
One monolithic tool is too few for the broad scope advertised—search, context, blame, fix, how-to, and memory storage are all crammed into a single tool. Separating these into distinct tools would make the surface clearer and more flexible.
The tool covers the full lifecycle of personal coding session memory: search (recall), deep-dive (context), historical reasoning (blame), error recovery (fix), command lookup (how), and durable storage (remember). No obvious gaps exist for the stated domain.