recall context <id> | claude

Your old Claude Code session, piped into a new one. Local SQLite with FTS5. Native MCP server. Works offline forever. Built by a Claude Code power user, for Claude Code power users.

npm install -g @clauderecallhq/cli

recall start && recall open

The three commands you will actually use

Start the daemon and indexer.

recall start

Find a past session.

recall search "auth race condition"

Hand a past session to a fresh Claude Code conversation as starting context.

recall context <session-id> | claude

Compose them. The middle command produces session ids that the third one consumes. That is the whole workflow.

Native MCP server

Recall ships an MCP server with read tools (search, get session, list projects, get thread) and write tools (apply tags, create thread). Claude Code agents can call them directly mid-session. Audit log on by default; rate-limited; no outbound network.

Why local-first matters here

• Daemon binds to 127.0.0.1 only. There is no outbound network call after install.
• SQLite database lives at ~/.recall/. Grep-friendly. Portable.
• Three-layer durability invariant: SQLite row, history column, plain-text mirror on disk. Source JSONLs are never modified.
• Works offline on a plane, in a SCIF, on a locked-down laptop.
• Dead-man clause: a future version can never delete your past.

The category, briefly

Anthropic ships a memory tool with Claude Code. CLAUDE.md is the convention. Simon Willison's llm CLI logs every prompt to SQLite. None of those is a session-shaped index across every project. Claude Recall is.

Pricing

Free tier indexes and lists. Pro is one-time, less than two coffees, and unlocks search, context re-injection, the MCP server, and every future personal feature. Pro license is validated once, then works offline forever.