Recall

Tool

Local-first TUI for searching AI coding session history across Claude Code, Codex, and OpenCode with hybrid FTS + sem...

Copy the install, test the workflow, then decide if it earns a permanent slot.

Why nowArchived

Strong idea surface, weaker maintenance signal. Steal the pattern before you commit.

DecisionKeep on the radar

Copy the install, test the workflow, then decide if it earns a permanent slot.

Trial costFast eval

You can test this quickly and remove it cleanly if it misses.

Risk98/100

GitHub health unknown. no security policy. Archived repo plus maintenance drag means copy patterns, not the whole tool.

What You Are Adopting

AI Agent

Multiple

Model

Claude

Build Time

Instant

One command inClean rollbackLow commitment

SandboxedInstalls to ~/.claude — isolated from your projects. One command to remove.

Fastest way to find out if Recall belongs in your setup.

Copy the install command, run a real test, and back it out cleanly if it slows you down.

Try now

git clone https://github.com/samzong/Recall ~/.claude/commands/recall-2

Run this first. You will know quickly if the workflow earns a permanent slot.

Back out

rm -rf ~/.claude/commands/recall-2

No messy cleanup loop. If it misses, remove it and keep moving.

Install Location

~/  └─ .claude/      ├─ commands/      │   └─ recall-2/ ← installs here      ├─ agents/      └─ settings.json

Local-first TUI for searching AI coding session history across Claude Code, Codex, and OpenCode with hybrid FTS + semantic retrieval

Submitted May 22, 2026