fable Recall
Your Claude already has a memory. fable unlocks it.
Quickstart · Why fable · Benchmarks · Roadmap · Discussions
 |
 |
 |
|
Every conversation you've ever had with Claude Code is already saved on your machine — every decision, every debugging hunt, every 2 AM breakthrough, word for word. Claude just isn't allowed to use it.
Mid-session, compaction builds a wall: everything behind it is locked away
to save tokens, and Claude carries on with a thin summary. /clear wipes
the slate. And after 30 days, Claude Code quietly deletes the files
themselves. Your project's real memory — locked, then destroyed, by
design.
Everyone else sells you a replacement memory: summaries, extracted facts, vector stores. fable does something different — it unlocks the real one.
pipx install git+https://github.com/grooverLab/fable
fable install # one command: register the MCP, install hooks, index your history
fable serve # browse your memory in a dashboard100% local · no API keys · no cloud · no daemons. Your conversations never leave your machine.
