Save every session.Recall any conversation.Continue where you left off.

Every conversation, word-for-word, on your own machine — searchable long after the transcripts are gone.

Local only · no account · no cloud
Try "recall why we chose this retry policy"
recall chat transcripts (search · read · continue) · ← context on demand for agents

Your agent starts every session from zero —
until you say the word.

The word is recall. Say it in a prompt and your agent goes and gets exactly what it needs: a whole conversation by session id, any message by keyword or meaning, or the session that wrote the code behind a commit.

recall — example prompts
ASK YOUR AGENT
Recall — we solved this before.
Recall <session-id> and continue.
Recall why this line exists.
The installed skill teaches Claude Code and Codex when and how to search.
VERBATIM HISTORY

/compact summarizes.
recall quotes.

Auto-memory saves what you knew to keep. recall finds what you didn't know you'd need.

Verbatim, not summaries.User and assistant turns, word-for-word, in a local index that survives Claude Code's default 30-day transcript cleanup.
Search words and meaning.SQLite FTS5 finds exact phrases; local semantic embeddings find the same idea under different wording.
From code back to conversation.recall --blame traces a commit or line to the Claude Code conversation that produced it.
Pull, not push.Nothing enters context until your agent asks, and recall makes no LLM calls of its own.
recall — real commands, no replay
# search
$ recall "why did we choose this retry policy?"
# read, centered on the matched message
$ recall <session-id> <message-id>
# trace code back to its conversation
$ recall --blame src/paths.ts:82-84
CONTINUATION

Stop writing handoffs.
The UUID is the handoff.

A session id is more than an identifier. It's a handoff you didn't have to write.

Recall <session-id> and continue the release.

/resume dies with the transcript; recall doesn't. A read, not a replay — and it can pull facts from other sessions.

More than 292,000 messages indexed on my machine · this page was researched with recall
WHY NOT A SCRIPT?

Your weekend script becomes
a product you maintain.

I wrote the first version as a script. Then came transcript-format drift, subagent sessions, embeddings, concurrent writers, WAL, and integrity repair.

No daemon, no cron, no cloud.
A Stop hook and a SQLite file.
Memory, lazily evaluated.
Recall v0.3.0
Context retrieval (on demand) · Claude Code · Codex
github.com/TheSylvester/crispy-recall