deja-vu — Coding Agent Memory & Session Search

● Active

io.github.vshulcz/claude-codex-cursor-agent-memory-deja-vu

Local memory & session search across fifty-two coding agents: Claude Code, Codex, Cursor.

Category
AI & Agents
Version
0.25.0
Registry
active
Published
11/21/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Looks healthy: deja-vu — Coding Agent Memory & Session Search is maintained, open source.

Maintained
Active
Last commit today (Nov 20, 2026), 12 open issues.
Official registry
Active
Published as io.github.vshulcz/claude-codex-cursor-agent-memory-deja-vu in the official MCP registry, version 0.25.0.
Source
Open source, MIT
Public repository under the MIT licence, 1,640 stars, 184 forks.
Runs
On your machine
A local mcpb package started by your client; it can reach whatever your user account can.
Credentials
None declared
The registry entry declares no required environment variables.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.

On GitHub

read Nov 21, 2026
Stars
1.6k
Forks
184
Last push
Nov 20, 2026
License
MIT

Goagent-memoryclaude-codeclaude-code-hooksclaude-code-memoryclinecodexcodex-memorycursorcursor-mcpdsh-plugingemini-cli-extensionkimi-codellm-memorymcpmemoryopenclawopencodeqwen-codesession-historyzed-extension

From the README

Shared local memory, session history search, cross-agent handoff, and code recovery across 51 coding agents. Local inverted index in a single Go binary — zero LLM calls, 0.7–0.8 ms in-process lookups, ~4% index footprint. English | 简体中文 | 繁體中文 | 日本語 | 한국어 | Español | Português | Français | Deutsch | Русский | Türkçe | हिन्दी · Website · Live demo · Docs · Benchmarks · Architecture Overview Coding agents already persist transcripts to local JSONL and SQLite stores (~/.claude, ~/.codex, Cursor state.vscdb, OpenCode, Gemini CLI, Hermes, and the remaining supported harnesses). deja indexes those transcripts in place into an append-only inverted index under ~/.cache/deja and exposes history through a terminal TUI, CLI, MCP server, and lifecycle hooks. • Works retroactively from day one. Existing transcripts across all fifty-one agents are searchable immediately without capture daemons or API keys. • Survives /compact and context resets. Captures pre-compaction tasks, settled decisions, files, and verification commands and injects a bounded recovery packet on the next turn (details). • Cross-agent handoff (deja handoff). Transfers goal, standing constraints, touched files, passed checks, and open work between harnesses. • Code recovery and attribution (deja restore, deja blame, deja origin).…

Read the full README on GitHub →

The most-starred AI & Agents servers in the index, with their live-check result.

ServerStarsLast pushLive check
Ruflo81,994Nov 2026Local / not checked
Claude Flow81,985Nov 2026Local / not checked
CodeBurn11,880Nov 2026Local / not checked
Kaneo9,825Nov 2026Local / not checked
Ha MCP7,958Nov 2026Local / not checked

deja-vu — Coding Agent Memory & Session Search: questions people ask

Is deja-vu — Coding Agent Memory & Session Search a remote or a local MCP server?
According to its entry in the official MCP registry, deja-vu — Coding Agent Memory & Session Search ships as a local package (mcpb) that your client starts on your machine.
Is deja-vu — Coding Agent Memory & Session Search safe to use?
Looks healthy: deja-vu — Coding Agent Memory & Session Search is maintained, open source. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: On your machine; credentials: None declared. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is deja-vu — Coding Agent Memory & Session Search still maintained?
Active: the repository's last commit today. Last push Nov 20, 2026, 1,640 GitHub stars, MIT licence. Read from GitHub on Nov 21, 2026.
How do I add deja-vu — Coding Agent Memory & Session Search to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
  1. Deja VuLocal memory & session search across fifty-two coding agents: Claude Code, Codex, Cursor.★ 1.6k
Browse all AI & Agents →

Add the badge to your site

Show visitors that deja-vu — Coding Agent Memory & Session Search is listed here — it’s also the link we check for a free listing.

deja-vu — Coding Agent Memory & Session Search — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-vshulcz-claude-codex-cursor-agent-memory-deja-vu?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="deja-vu — Coding Agent Memory & Session Search — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![deja-vu — Coding Agent Memory & Session Search — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-vshulcz-claude-codex-cursor-agent-memory-deja-vu?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).