Your agents already solved this. deja finds it — retroactive search and MCP recall over the session logs your coding...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health 85/100. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Multiple
Model
Claude
Fastest way to find out if deja-vu belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add deja-vu -- npx deja-vuRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove deja-vuNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ deja-vu ← registers here
Your agents already solved this. deja finds it — retroactive search and MCP recall over the session logs your coding agents already wrote. Cross-agent, SSH-portable, one zero-dep binary, fully local.
Source: GitHub repository
Source check: July 18, 2026
Upstream commit: July 18, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.