Skip to content
Tech News
← Back to articles

Show HN: Recall – Local project memory for Claude Code

read original more articles
Why This Matters

Recall offers a significant advancement for developers using Claude Code locally by providing a fully private, cost-effective way to maintain persistent project memory. It addresses the cold-start problem without incurring additional costs or risking data privacy, making it especially valuable for users seeking efficient and secure AI-assisted coding. This innovation enhances productivity and privacy in the evolving landscape of AI development tools.

Key Takeaways

Recall — fully-local project memory for Claude Code

Claude Code starts every session cold. Recall keeps a local log of your sessions and condenses it into a resume-ready summary — entirely on your machine. No API key, no external model, nothing sent anywhere. It's built for people running Claude Code locally on a subscription: the only AI in the loop is Claude Code itself; the summarization is done by a classical Python summarizer.

Why Recall

Free on your subscription. It solves the cold-start problem — no more re-explaining the project each session — without a metered summarizer running up a bill. The summary is a local algorithm, not an LLM call, so persistent memory costs you nothing beyond the subscription you already pay for.

It solves the cold-start problem — no more re-explaining the project each session — without a metered summarizer running up a bill. The summary is a local algorithm, not an LLM call, so persistent memory costs you nothing beyond the subscription you already pay for. Saves your usage credits. Two ways: (1) the summary is built locally, so capturing and updating your memory spends zero model tokens; and (2) resuming from a compact context.md (~1–2K tokens) instead of re-explaining the project from scratch each session means far fewer tokens spent per session — stretching your subscription's usage limits (or, on the API, lowering billed credits).

Two ways: (1) the summary is built locally, so capturing and updating your memory spends model tokens; and (2) resuming from a compact (~1–2K tokens) instead of re-explaining the project from scratch each session means far fewer tokens spent per session — stretching your subscription's usage limits (or, on the API, lowering billed credits). Nothing leaves your machine. Your transcripts (code, paths, sometimes secrets) are never sent to any API. Most "memory" tools pipe your context to a model endpoint; Recall makes a privacy guarantee they can't.

Your transcripts (code, paths, sometimes secrets) are never sent to any API. Most "memory" tools pipe your context to a model endpoint; Recall makes a privacy guarantee they can't. Zero-friction. No pip install , no local model to run, no key to configure, works offline. It starts working the moment the plugin loads.

Two files, written into your project under .recall/ :

history.md — the log. Append-only. Every session is captured here as it happens (your prompts, Claude's replies, the files touched and commands run).

— the log. Append-only. Every session is captured here as it happens (your prompts, Claude's replies, the files touched and commands run). context.md — the summary. Overwritten by the local summarizer — the condensed "where are we right now" you load into the next session: goal, summary, next steps / open threads, files touched, and where you left off.

... continue reading