Overview
One local store, several capabilities layered on it. Every card links to the page that explains the mechanism.Belief pipeline on save
A save is not an insert. Duplicates merge, rewordings become versions, contradictions are kept
and raised. Nothing is silently overwritten.
Hybrid recall
Meaning, exact words, and entity anchoring, fused into one ranking over your memories and your
files together.
Grounded assistant
Chats over your store, answers only from what it found, and cites passages you can open.
Your files, cited
Markdown, text and PDF, chunked along real structure so a result is one section, not a blind
window.
Recordings and web pages
Audio and video transcribed and diarized on-device, cited by timestamp. Web pages fetched and
parsed in-process.
Folders that stay current
Link a folder and files that appear in it are taken in on their own. An edit re-embeds the
section that changed, not the file.
One graph
Entities link memories and documents. The vocabulary is a registry you can extend, prune, and
correct.
Entity resolution
Folds duplicate spellings, asks about the uncertain ones, and keeps every fold reversible.
Version history
Every memory is a version chain. Nothing is destroyed, and
memloom history walks it.Conflicts you settle
When two memories cannot both be true, both are kept and you decide. Every resolution is
reversible.
Reconciliation
The store reviews itself, repairs what SQL proves, and asks about the rest. Automatic runs
never spend money.
Claude Code history
Import past sessions, or capture new ones continuously, distilled through the same pipeline
with provenance back to the line range.
Local-first
The store is a folder. Copy it to back it up. The only network calls go to the provider you
configure.
Every client, one store
All of them talk to one daemon that owns one store, so an agent’s save is instantly visible in the
viewer and your CLI recall sees what the agent ingested. See
Architecture.