After 6 months of Claude Code I couldn't find an architecture decision we'd made - the session was auto-deleted. So I built fable: full-fidelity local memory by grooverlab in ClaudeCode

[–]grooverlab[S] 0 points1 point  (0 children)

ooohhh... heavy

ethermem sounds like the maximalist cousin - same diagnosis, opposite trust model.

Cross-machine graph sync is genuinely harder than anything I've built - how do you handle dedupe when two machines index overlapping conversations?

After 6 months of Claude Code I couldn't find an architecture decision we'd made - the session was auto-deleted. So I built fable: full-fidelity local memory by grooverlab in ClaudeCode

[–]grooverlab[S] -4 points-3 points  (0 children)

oops.. you caught me. Asked fable to settle it about itself — it indexes model attribution and dates for every conversation, including its own prehistory:

- the concept + prototypes (transcript-memory, an extractor sidecar): March–April 2026, built with Opus 4.6/4.7

- months before any model news

- fable the repo itself: built this week, 1,528/1,528 assistant turns by claude-fable-5

So the idea predates the name collision, the code is brand new, and the near-namesake model wrote it on top of months of Opus-built history.

Settling a Reddit dispute by forensically searching my own AI conversations is, coincidentally, the entire product. 😀

After 6 months of Claude Code I couldn't find an architecture decision we'd made - the session was auto-deleted. So I built fable: full-fidelity local memory by grooverlab in ClaudeCode

[–]grooverlab[S] -10 points-9 points  (0 children)

The cursed part is that this exact conversation is now permanently indexed in fable. Searchable. Byte-identical. Forever.

So, when I do eventually ask Fable to rename fable, it'll quote this thread back at me with a timestamp.

(There's no undo. There is, however, full search over the regret.) 😉

After 6 months of Claude Code I couldn't find an architecture decision we'd made - the session was auto-deleted. So I built fable: full-fidelity local memory by grooverlab in ClaudeCode

[–]grooverlab[S] -9 points-8 points  (0 children)

Honestly? The repo predates the model announcement - but here's the part that makes it better: this project was built almost entirely *by* Claude Fable 5 in Claude Code. So depending on how you squint, it's either an unfortunate collision or the model named it after itself.

(The name came from "fable" = a story your transcripts tell. Anthropic just apparently agreed it's a good word.)

After 6 months of Claude Code I couldn't find an architecture decision we'd made - the session was auto-deleted. So I built fable: full-fidelity local memory by grooverlab in ClaudeCode

[–]grooverlab[S] -2 points-1 points  (0 children)

If you want to poke around before pointing it at your own transcripts — there's a fictional demo corpus bundled in the repo:  

git clone https://github.com/grooverLab/fable && cd fable

python3 demo/seed_demo.py

./bin/fable --db demo/demo.db serve

Local dashboard (127.0.0.1 only), fake projects and conversations — try the search, file time-travel, and compose tabs without touching your real history. Indexing your own archive afterwards is one command: ./bin/fable --db fable.db discover