Early access opening. Get on the list →

Claude Code's memory sucks
recall. fixes that.

Claude Code's built-in memory only lasts the session you're in.
Recall plugs in with one command and pulls your exact words
from any past session, the moment Claude needs them.

JM RK SP DC +
Real demand from Claude Code users. See the evidence ↓
~/billing-pipeline — claude-code
Claude Code v2.1.76
Opus 4.7 (1M Context) · ~/billing-pipeline
recall mcp loaded · 1,402 sessions indexed
Why did we pick Postgres over Mongo for billing? recall_search(query: "postgres mongo billing") Recalled 1 memory · 0.6s Postgres won on ACID for the billing pipeline. From your 2026-03-15 architecture-review session:
we tried MongoDB but the lack of ACID for the billing pipeline killed us. Postgres has PostGIS for the location queries we need, plus the team already knows it. Migration spike: ~3 days.
PR #47 landed March 22 — the 3-day migration estimate came in close to plan.
PROBLEM

We didn't make this up.

Public posts from Claude Code users. The built-in memory keeps biting them. The OSS attempts (mem0, Letta, MemGPT, markdown-files) keep falling short. Click any tile to read the source.

GitHub
issue #25695 · closed

"This is the single most frustrating experience in Claude Code."

github.com/anthropics/claude-code/issues/25695
GitHub
issue #14227 · feature request

"Claude Code is a goldfish."

github.com/anthropics/claude-code/issues/14227
GitHub
issue #27298 · power outage

"Every Claude Code session starts amnesiac. A power outage lasting 2 minutes killed 6 active Claude Code sessions mid-work. All context, gone."

github.com/anthropics/claude-code/issues/27298
YHacker News
saberience · OSS attempts

"I have tried probably 10-20 other open source projects (mem0, Letta, MemGPT, others) and still nothing works better than simply keeping my own library of markdown files."

news.ycombinator.com/item?id=46426624
YHacker News
austinbaggio · Show HN

"I got tired of Claude Code forgetting all my context every time I open a new session."

news.ycombinator.com/item?id=46426624
r/ClaudeAI
community thread

"Lost a full afternoon. Four hours debugging a database migration with Claude Code, then the session compacts and I'm explaining the schema again from scratch."

reddit.com/r/ClaudeAI
DEVDEV Community
3 ways to fix Claude Code's memory

"Each Claude Code session begins with a fresh context window. Two mechanisms try to carry knowledge across — neither holds for real projects."

dev.to/gonewx/i-tried-3-different-ways
Blog
Du'An Lightfoot

"Claude can't remember what you discussed five minutes ago."

duanlightfoot.com/posts/claude-code-compacting
MMedium
Claude Forgot My Entire Project

"Hours into building something intricate, the assistant responds as if meeting you for the first time. All of it simply, gone."

medium.com/@nbhyxq/claude-forgot-my-entire-project
DEVDEV Community
Claude's Alzheimer's Feature

"It does not remember anything between chats or sessions. Every session. Every time."

dev.to/kim_bouwman_1e15b489fb1f3
GitHub
issue #2545 · open

"Instructions given 30 minutes earlier are completely forgotten. Configuration settings are repeatedly asked for despite being provided."

github.com/anthropics/claude-code/issues/2545
XDA Developers
persistent memory take

"Claude Code starts every session with zero context and there is no memory of previous sessions, previous work, or accumulated understanding."

xda-developers.com/claude-code-persistent-memory
FEATURES

Everything you need to stop
repeating yourself to Claude.

One MCP server. One install command. A memory layer that works the way you already work.

Verbatim recall.

Your exact words come back, not a paraphrase. Original passage with date and source session inline in Claude's response.

Every project, one memory.

Anything you said in any past Claude Code session — surfaceable in any current one. No more silos between repos.

Calls Recall on its own.

Claude decides when to look back. You don't search; the model does. The right quote surfaces mid-response.

Local-first.

Reads from your disk. Writes to your disk. Zero bytes uploaded. Your conversations never leave your machine.

One command install.

npx recall init writes the MCP config to your CLI settings. No browser extension. No connector toggle. About 60 seconds.

Hybrid retrieval.

Semantic plus keyword search across every chunk. The right match surfaces whether you remember the exact phrase or just the topic.

HOW IT WORKS

From install to verbatim recall
in 4 steps.

No browser extension. No per-conversation toggle. No friction tax.

Run npx recall init

Recall writes the MCP config to your CLI settings. ~60 seconds.

Ingest your local sessions

Reads ~/.claude/projects history. Stays on your machine. ~5 min.

Use Claude Code normally

Nothing in your workflow changes. The integration is invisible until needed.

Claude calls Recall

Verbatim quote surfaces in the response, attributed to its date and session.

$ npx recall init

For Claude Code · ~/.claude/projects

SIDE BY SIDE

Same prompt. Two different Claude Codes.

Same model. Same project. The right side just has Recall installed.

Claude Code · default
~/billing — claude-code
Why did we pick Postgres over Mongo for billing? memory_recall() No matches · session memory only · 0.1s I don't have context from previous sessions. Could you share the relevant files or paste the discussion thread?
Claude Code · with recall.
~/billing — claude-code
Why did we pick Postgres over Mongo for billing? recall_search(query: "postgres mongo billing") Found in 2026-03-15 architecture-review · 0.6s Postgres won on ACID. From your 2026-03-15 architecture-review:
we tried MongoDB but the lack of ACID for the billing pipeline killed us. Postgres has PostGIS for the location queries we need.
PR #47 landed March 22.

Same model. Just one of them remembers what you said.

Get early access Free · Replies read by the founder
QUESTIONS

What you might be wondering.

Why not just use Claude Code's built-in memory?

Claude Code's built-in memory only lives inside the current session. Close the terminal and the next one starts amnesiac. Compaction is lossy — file paths, line numbers, the actual decisions you made get summarized away. Recall reads from your local Claude Code session files and surfaces your exact words from any past session, mid-response, without you having to ask.

Why not mem0, Letta, MemGPT, or just markdown files?

People keep trying these. They keep going back to markdown. The OSS attempts ship with great READMEs but break the moment your project gets real — they paraphrase your words instead of quoting them, they index half your codebase, they need maintenance you don't have time for. Recall is built for one job: pull your exact words from past Claude Code sessions, mid-response, with zero ongoing care. We're going narrow before going wide.

What's an MCP server, and why does it matter here?

MCP (Model Context Protocol) is the standard Anthropic shipped for letting Claude call external tools. When you install Recall as an MCP server, Claude Code learns it has a `recall_search` tool. From then on, whenever Claude thinks you've said something relevant before, it calls that tool itself — you don't have to remember to invoke anything. One install, then it's invisible.

What about my data privacy?

Local-first. Recall reads your Claude Code session files from your disk (`~/.claude/projects`) and writes its index to your disk. Your conversations never leave your machine. No telemetry, no upload, no server-side storage of your code or chats.

Does it work in Claude.ai (the web app)?

Not in v1. Web Claude.ai requires a browser extension and a per-conversation connector toggle, which kills the "one install, works forever" promise we're committing to. We may add it if v1 ships and signal continues.

Does it work with OpenClaw, Codex, ChatGPT, Cursor, Aider, or Windsurf?

Not in v1. We're going deep on Claude Code first. OpenClaw and Codex are next on the roadmap if v1 ships and the signal lands there. Tell us in the form which CLI you actually use — that's how we sequence what to add next.

Is this built yet?

Almost. The pieces are there — we're just gauging how much it would matter to you before we cut a v1. The more interest we see this week, the faster we ship. We genuinely believe this should exist; we want to make sure you do too.

When will it be ready?

Soon. Once we hear from enough early-access folks, we move fast — the integration is straightforward by design. You'll be the first to know.

What's it going to cost?

We're still figuring it out. Likely a subscription since indexing has ongoing costs (server + embedding API), but we want it priced so individual developers actually use it. If you have strong opinions, tell us in the form.

Who's behind this?

X-Arc — a small lab that ships focused AI tools (open-source: brain-cli, agent-memory, design-discipline). Recall is the next one, built only if you say it should be.

EARLY ACCESS

Get on the list.

Join the early-access list and we'll let you know the moment Recall is ready for Claude Code. The first 15 names also unlock a 15-minute call with the founder to shape what we build.

Which CLI do you use most?*

v1 ships for Claude Code. The other CLIs follow if signal lands there.

Free · No spam · Replies read by the founder