deja-vu

★ 1.3k

agent-memory

★ 15

deja-vu vs agent-memory

Q: Which is better, deja-vu or agent-memory?

By GitHub stars, deja-vu has more community adoption, but the best choice depends on your specific use case.

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.; agent-memory: Agent-memory offers local, Git-native project memory for AI coding agents, leveraging Markdown as the single source of truth for durable, human-reviewable, and secret-safe knowledge. It facilitates structured memory updates and seamless integration with various agent runtimes, operating entirely locally without external cloud or vector database dependencies.

TL;DR

deja-vuMemory & Context · ★ 1.3k

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

Read deja-vu full review →

agent-memoryMemory & Context · ★ 15

Bootstrapping an AI agent's project memory from an existing codebase.

Read agent-memory full review →

Side-by-Side Comparison

Field

deja-vu

agent-memory

Features

deja-vu

01Fast, Retroactive Session Search

02Automatic AI Agent Memory Recall

03Cross-Machine Memory Synchronization

04Seamless Agent Context Handoff

05Automated Sensitive Data Redaction

agent-memory

01Git-native, Markdown-based memory with version control.

02Human review gate for durable changes via diffs.

03Automated scanning and rejection of secrets/PII on write.

04Fully local operation without cloud or vector database dependencies.

05Verifiable Task Protocol (VTP-1) for cryptographic task lifecycle.

06Federated memory for referencing shared, read-only 'landscape' stores.

Use Cases

deja-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.

agent-memory

↳Bootstrapping an AI agent's project memory from an existing codebase.

↳Recording and reviewing durable architectural decisions and conventions.

↳Discovering peer solutions and operational context via federated memory.

↳Ensuring safe, non-breaking cross-service contributions by agents.

↳Cryptographically verifying autonomous agent task execution and settlement.

FAQ

What is the difference between deja-vu and agent-memory?

Both deja-vu and agent-memory are in the Memory & Context category. deja-vu has 1.3k stars, while agent-memory has 15 stars.

Which is better, deja-vu or agent-memory?

The best choice depends on your use case. Choose deja-vu if Reusing solutions from past agent conversations to avoid re-debugging or re-implementing., and agent-memory if Bootstrapping an AI agent's project memory from an existing codebase..

Is deja-vu free or open source?

Yes, deja-vu is open source on GitHub (MIT).

Is agent-memory free or open source?

Yes, agent-memory is open source on GitHub (Apache-2.0).

Cloud Infrastructure

Deploy on DigitalOcean

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

Claim $200 Free Credit

→

Alternatives to deja-vu →Alternatives to agent-memory →deja-vu details →agent-memory details →

TL;DR

Side-by-Side Comparison

Features

Use Cases

FAQ

Deploy on DigitalOcean

Related