AgentIndex icon
AgentIndex
remem logo
remem
★ 34
vs
deja-vu logo
deja-vu
★ 1.3k

remem vs deja-vu

remem: `remem` is a local-first memory solution for AI coding agents like Claude Code and OpenAI Codex, preventing repetitive explanations by automatically capturing and injecting project context. It distills, searches, and stores project decisions, bug fixes, and preferences locally using SQLite, accessible via CLI, hooks, and a REST API.; deja-vu: Deja-vu is a zero-dependency, local-first binary that indexes and makes searchable the historical sessions of various AI coding agents. It acts as a universal memory layer, allowing agents to recall past solutions and context efficiently, even from before its installation.

01

TL;DR

remem logo
rememMemory & Context · ★ 34

Avoiding repetitive project explanations to AI coding agents.

Read remem full review →
deja-vu logo
deja-vuMemory & Context · ★ 1.3k

Reusing solutions from past agent conversations to avoid re-debugging or re-implementing.

Read deja-vu full review →
02

Side-by-Side Comparison

Field
remem logoremem
deja-vu logodeja-vu
Category
Memory & Context
Memory & Context
Stars
★ 34
★ 1.3k
License
MIT
MIT
Install Command
curl -fsSL https://raw.githubusercontent.com/majiayu000/remem/main/install.sh | env REMEM_NO_CONFIG=1 sh && ~/.local/bin/remem install --target codex
curl -fsSL https://raw.githubusercontent.com/vshulcz/deja-vu/main/install.sh | sh
Updated
2d ago
1d ago
Open Source
Yes
Yes
Website
↗ Visit
↗ Visit
GitHub
↗ GitHub
↗ GitHub
Tags
AI Agent Memory, Context Management, Coding Assistant
AI Agent Memory, Session Search, Code Assistant
03

Features

remem logoremem
01Automatic memory capture and injection for coding agents.
02Searchable history of project decisions, bug fixes, and rationale.
03Local-first memory storage with SQLite and SQLCipher encryption.
04Accessible via CLI, coding agent hooks, MCP tools, and REST API.
05Single Rust binary with no external database dependencies.
deja-vu logodeja-vu
01Fast, Retroactive Session Search
02Automatic AI Agent Memory Recall
03Cross-Machine Memory Synchronization
04Seamless Agent Context Handoff
05Automated Sensitive Data Redaction
04

Use Cases

remem logoremem
↳Avoiding repetitive project explanations to AI coding agents.
↳Searching and recalling past project decisions and bug-fix rationale.
↳Maintaining an auditable and project-scoped history of engineering memory.
↳Reducing the need for manual upkeep of large memory documentation files.
deja-vu logodeja-vu
↳Reusing solutions from past agent conversations to avoid re-debugging or re-implementing.
↳Debugging complex issues by accessing comprehensive past debugging sessions and design decisions.
↳Maintaining persistent context across different AI agents and development machines.
↳Sharing sanitized session digests with colleagues for onboarding or knowledge transfer.
↳Understanding file change history and decision-making via session blame.
FAQ

FAQ

What is the difference between remem and deja-vu?
Both remem and deja-vu are in the Memory & Context category. remem has 34 stars, while deja-vu has 1.3k stars.
Which is better, remem or deja-vu?
The best choice depends on your use case. Choose remem if Avoiding repetitive project explanations to AI coding agents., and deja-vu if Reusing solutions from past agent conversations to avoid re-debugging or re-implementing..
Is remem free or open source?
Yes, remem is open source on GitHub (MIT).
Is deja-vu free or open source?
Yes, deja-vu is open source on GitHub (MIT).
Cloud Infrastructure
Ad

Deploy on DigitalOcean

Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.

Claim $200 Free Credit
→

Related

Alternatives to remem →Alternatives to deja-vu →remem details →deja-vu details →