No accidental global recall.
Ambient project and task context is automatic. Broader workspace or personal search requires an explicit request and a reason.
LOCAL / CITED / AGENT-NATIVE
Your agent can remember.
It can show the receipt.
Memoree turns durable project knowledge into scoped claims with immutable evidence. Ask what it knows; get an honest answer, exact references, and every contradiction still attached.
$ curl --proto '=https' --tlsv1.2 -sfL https://memoree.dev/install.sh | sh
$ memoree recall "why SQLite?"
presence claims
claim SQLite is authoritative;
indexes stay rebuildable.
status current
evidence art_01K…@arev_01K…#418-492
source docs/architecture.md
──────────────────────────────────
scope project:memoree
broadened false
conflicts 0CLAIMREVISIONBYTES
01Keep the source
Original artifacts remain immutable evidence, not disposable chunks.
02State the claim
Current, disputed, superseded, and retracted are different things.
03Return the reference
Every grounded claim resolves to the exact revision and byte span.
THE MEMORY CONTRACT
Useful memory is not a pile of embeddings.
It is a small, inspectable contract between an agent and the work that came before.
“None” means none.
Recall reports claims, artifacts_only, or none. It does not invent an answer or silently widen scope.
Your memory stays yours.
SQLite and a filesystem content store run on your machine. The daemon has no model provider, telemetry path, or hidden update check.
Revision is not erasure.
Conflicting claims remain visible with frozen evidence and lifecycle history, so a newer sentence cannot quietly rewrite the past.
ONE SMALL LOCAL SYSTEM
ARTIFACTsource bytes
→REVISIONimmutable digest
→CLAIMgrounded statement
→RECALLanswer + references
The index is replaceable. The evidence is not.
START WITH ONE PROJECT