Claude Memory — Persistent Memory for Claude Code That Never Forgets

Free alternative to Mem.ai, Notion AI Memory, Rewind AI, and Personal AI

Give Claude Code photographic memory. Every decision, every learning, every client detail — captured automatically, recalled instantly, backed up forever. Zero manual work.

What You Get

Feature	What It Does	How It Works
Auto-Capture	Saves decisions, learnings, errors, client info silently	Detects patterns in conversation, stores via MCP
Session Recall	Loads relevant context when you start a new session	Semantic search over recent memories + cloud fallback
Cloud Backup	Never lose a memory, even after local compaction	Supabase sync every 5 minutes, never deletes
Semantic Search	Find memories by meaning, not just keywords	SQLite-vec embeddings (all-MiniLM-L6-v2, 384d)
Session Summaries	Auto-saves outcomes when you wrap up	/session-end captures decisions, open items
Cloud Recall	Search cloud for memories deleted locally	/cloud-recall searches Supabase when local is empty

The Problem: Claude Code Forgets Everything

Every time you start a new Claude Code session, you start from scratch. Past decisions vanish. Client details disappear. Architectural choices you made yesterday are gone.

The built-in MCP Memory Service tries to help, but its consolidation pipeline destroys your data:

What Happens	Data Lost	Timeline
Compression	50-70% of content stripped	Ongoing
Forgetting	Low-quality memories permanently deleted	30-90 days
Clustering	Similar memories merged, originals destroyed	Ongoing

Claude Memory fixes all of this. Auto-capture + cloud backup = total recall, forever.

Quick Install

curl -fsSL https://raw.githubusercontent.com/itsjwill/claude-memory/main/install.sh | bash

Or clone and run locally:

git clone https://github.com/itsjwill/claude-memory.git
cd claude-memory
./install.sh

That's it. Claude will start capturing memories automatically on your next session.

How It Works

1. Auto-Capture (Zero Effort)

Claude detects and captures these patterns silently — no action needed:

Trigger	Example	Memory Type
Decisions	"Let's go with PostgreSQL"	decision
Learnings	"I learned that..."	learning
Errors Fixed	"The bug was caused by..."	gotcha
Client Info	"Their email is..."	client
Preferences	"I prefer tabs over spaces"	preference
References	"API key is in .env"	reference
Patterns	"We always use..."	pattern

2. Manual Capture

/capture "Important architectural decision about the database"
/capture "Client prefers weekly updates" --type preference --tags client,process

3. Session Summaries

User: "Thanks, that's all for now"
Claude: [silently saves session summary with outcomes, decisions, open items]

4. Session Recall

Every new session, Claude automatically searches for:

• Current project context
• Recent activity (last 7 days)
• Related decisions and learnings
• Cloud backup (when local results are sparse)

You pick up exactly where you left off. No context loss.

5. Search Memories

memory_search(query="database decisions", limit=10)
memory_list(tags=["client"])