Claude's built-in memory sucks
recall. fixes that.

Claude does have built-in memory across its surfaces. In Claude Code there's CLAUDE.md (instructions you write) and auto memory (notes Claude writes to ~/.claude/projects/<project>/memory/MEMORY.md based on what it decides was worth remembering). Claude.ai and Cowork have their own memory layers with the same shape. The catch is consistent: 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 — get distilled into gist. And on Claude Code, 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 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 in Claude Code, Claude 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. For Claude.ai and Cowork, we'll ship a custom connector that does the same job through Anthropic's connector framework.

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.

That's the goal. v1 ships for Claude Code first because the install path is the cleanest (one terminal command, no browser toggles). Claude.ai and Cowork follow — they require a custom connector instead of an MCP server, which is a different shape of integration but the same core idea. The order of what we ship next depends on which surface our early-access folks actually live in. Tell us in the form.

Not in v1. We're going deep on Claude's ecosystem first because that's where the memory shape is consistent enough to actually fix. Tools outside the Claude family are on the roadmap if v1 ships and the signal lands there. Tell us in the form which AI tools 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.