Built-in memory keeps a summary of what mattered. You keep redoing the explanation.
Recall keeps the decisions, the trade-offs, and the why behind every call you made — so every session picks up where you left off.
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.
"This is the single most frustrating experience in Claude Code."
github.com/anthropics/claude-code/issues/25695 GitHub"Claude Code is a goldfish."
github.com/anthropics/claude-code/issues/14227 GitHub"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"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"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"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"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"Claude can't remember what you discussed five minutes ago."
duanlightfoot.com/posts/claude-code-compacting MMedium"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"It does not remember anything between chats or sessions. Every session. Every time."
dev.to/kim_bouwman_1e15b489fb1f3 GitHub"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"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-memoryThe decisions you weighed. The context you built. The lines you'd otherwise be retyping for the third time. All of it, where it should be — inside Claude's next answer.
When Claude cites you, it's a direct quote with the date and the session it came from. No telephone-game between past you and present you.
The decision you made on the billing repo last month surfaces when you're working on the dashboard today. Context follows the thought, not the folder.
Claude figures out when something past matters. The right line shows up inside the answer — no "/recall this", no command to type, no search bar to open.
Nothing leaves your machine. The candid trade-offs, the half-formed ideas, the things you'd never paste into a server log — they stay where they belong.
Install on a coffee break. From then on, every Claude Code session knows everything you ever told it — without you doing a single thing differently.
By topic, by keyword, by half-remembered phrase. You don't have to remember exactly what you said — Recall does.
No browser extension. No per-conversation toggle. No friction tax.
Recall writes the MCP config to your CLI settings. ~60 seconds.
Reads ~/.claude/projects history. Stays on your machine. ~5 min.
Nothing in your workflow changes. The integration is invisible until needed.
Verbatim quote surfaces in the response, attributed to its date and session.
$ npx recall init
For Claude Code · ~/.claude/projects
Same model. Same project. The right side just has Recall installed.
Same model. Just one of them remembers what you said.
Get early access Free · Replies read by the founderClaude Code does have built-in memory — two systems, actually. CLAUDE.md files (instructions you write yourself) and auto memory (notes Claude writes to ~/.claude/projects/<project>/memory/MEMORY.md based on what it decides was worth remembering). Both load at session start. The catch: auto memory is paraphrased. Claude reads your conversation, decides what mattered, and writes a summary. Your actual words — the line numbers, the architecture caveats, the gotchas you discovered — get distilled into gist. Only the first ~200 lines of MEMORY.md load each session, so older notes get pushed out. Recall reads the raw session transcripts on disk and surfaces your verbatim quotes — not Claude's summary of them — mid-response, the moment Claude needs them.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.