Guides
Memory graph
How the Memory layer stores what users say, how to see it in the dashboard, and what leaves the gateway.
The Memory layer keeps what each user has told the agent as a temporal graph of facts. This page covers what a fact is, how to see the graph, and the privacy switches.
#A fact
Each fact has a subject, a predicate and an object ("Priya", "lives in", "Pune"), the turn it came from and a creation date. When a newer fact replaces an older one for the same thing, the older one is not deleted. It is marked as superseded with the date, so the graph can answer both "where does she live now?" and "where did she live before?". A fact that keeps being repeated is counted as seen again instead of being stored twice.
#Per user
Memory is separated by a scope, normally one end user. The scope decides whose memory a request reads and writes, and one scope's facts never reach another's prompt. Set how requests are grouped with -memory-scope (or the "Whose memory" setting in the Memory layer).
#Seeing it
Open Memory in the dashboard and pick a user. Each fact is a node, joined to the others by its subject and object. Facts that are no longer true are hidden until you switch on Show old facts. Select a fact to see its date and, if you have chosen to send it, the user's original wording.
This is the control plane's copy of the graph. The gateway's memory directory stays the source the layer reads from.
#What leaves the gateway
Reporting facts is off by default, because facts are what people said, not metadata.
| Flag | Effect |
|---|---|
-report-memory | Send each user's facts to the control plane so the dashboard can draw the graph. Needs -api-url and -memory-dir. |
-report-memory-quotes | With -report-memory, also send the user's original wording of each fact. Off by default. |
rakuvo serve -listen 127.0.0.1:8081 \ -memory-dir ./memory -memory-model gpt-4o-mini \ -api-url https://your-rakuvo-api -report-memoryFacts go to POST /v1/ingest/memory with a gateway key. They are read back with GET /v1/memory/graph: without a scope it lists the users that have a graph, and with ?scope=<user> it returns that user's facts.
#What the layer measured
On held-out LoCoMo it scored 68.9% against 58.4% for embedding search. See The layers for the other benchmarks and for where it is weaker, such as counting facts across many sessions.