vshulcz/deja-vu
Related Servers
Alternatives to vshulcz/deja-vu
- AlicenseBqualityDmaintenanceA 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.61MIT
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-
- AlicenseAqualityBmaintenanceEnables MCP-capable coding agents to semantically search, store, and inspect a single local, cross-tool index of session histories and project docs. Agents can retrieve what other tools and prior sessions already discovered.31MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to search locally indexed past sessions from Claude Code, Codex CLI, Pi, and custom JSONL logs with citations, while redacting secrets before storage.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceTurns local Codex session transcripts into a searchable memory that MCP-compatible coding agents can query to retrieve relevant past sessions or exact commands and fixes.1MIT
- FlicenseNot gradedqualityCmaintenanceLocal-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.513MIT
TDQS
Scored across 1 tool
The eight modes are described with concrete trigger conditions (fix = you just hit an error, blame = before you edit a file), which helps a lot, but several overlap in practice: recall vs context vs orient vs how all answer 'find something from past sessions', and an agent must choose a mode parameter rather than a distinct tool. Because everything is one call with a mode switch, a wrong mode choice is invisible until results come back wrong.
There is only one tool, so cross-tool inconsistency is impossible, and the mode vocabulary is uniformly lowercase single-word verbs/nouns (recall, blame, fix, how, orient, remember, handoff). Minor friction: 'how' and 'context' are vaguer labels than the rest and 'handoff' takes a different argument shape (q: id or harness) than the term-based modes.
One tool is thin as a surface for eight genuinely different operations, forcing everything through a mode string and a free-form query rather than typed parameters. It is a defensible single-entry-point design, but it sits at the borderline the rubric calls out for 1-2 tool servers.
The lifecycle is well covered: discovery (recall, orient, how), deep dive (context), diagnostic (fix, blame), and write-back (remember, handoff), plus feedback markers. Gaps are modest — no way to list/inspect or forget/delete stored memories, and no way to enumerate sessions without a term to search on.