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
Memoree turns durable project history into scoped claims with immutable evidence. Ask once; get qualified memory or a bounded exact recovery packet—then let current source remain authoritative.
$ 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 0Original artifacts remain immutable evidence, not disposable chunks.
Current, disputed, superseded, and retracted are different things.
Every grounded claim resolves to the exact revision and byte span.
It is a small, inspectable contract between an agent and the work that came before.
Ambient project and task context is automatic. Broader workspace or personal search requires an explicit request and a reason.
Retrieval never invents an answer or widens scope. Its exact recovery packet stays explicitly unqualified, bounded, and cited.
Agents use repository tools for current code. The optional project index remains experimental until matched tasks prove that it improves quality and cost.
SQLite and a filesystem content store run on your machine. The daemon has no model provider or telemetry path; signed update checks require confirmation.
Optional project metrics retain only bounded numeric and categorical events. Randomized paired experiments test token and time claims; passive traces never pretend to be a control.
Conflicting claims remain visible with frozen evidence and lifecycle history, so a newer sentence cannot quietly rewrite the past.
The index is replaceable. The evidence is not.
START WITH ONE PROJECT