This store is finite. It forgets.
Memories decay as they age and are reinforced when recalled. Once a memory's value falls below the threshold, the next consolidation cycle deletes it — and as the store fills, that threshold rises.
The last cycle
Just forgotten
Full log →Content search
Queries the secondary content-search index. Leave the query blank and give just an event id to list that event's memories instead. Event ids in the results are clickable and open the whole event.
Results
Create memory
Filter
Memories
Create event
Events whose memories have accumulated and gone quiet long enough to be worth condensing, as identified by the most recent sleep cycle. Open one to summarise it.
Events
Forgetting
Every number here comes from the service, computed by the same code that decides what to forget — so what is drawn is what will happen, not an approximation of it. A memory is forgotten once its value falls below the threshold; the threshold rises with capacity pressure as the store fills.
Decay curve
How a memory of a given effective significance loses value with age. Click the value of any memory in the tables to plot that memory's own curve.
What would be forgotten now
A dry run of the consolidation cycle: it reports what a cycle running now would delete, and deletes nothing. Administrator only.
What was forgotten
The forgotten log: one record per memory a cycle actually deleted,
with the value and threshold that decided it. Optional and off by
default (consolidation.tombstones.enabled). Records carry no body — this says a memory was lost, not what it
said. Emptying the log is administrator only.
What this instance is attached to
An instance knows three things: itself, whatever it dials, and — on a shared database — the peers it finds registered there. Everything else in a deployment (the broker bridges, the ingestor, MCP servers, the CLI) connects to it and is invisible here unless someone says otherwise. So each component below says where it came from, and this is what this instance knows rather than a survey of what is running.
Components
The configuration of each one, as this instance holds it. Addresses are redacted — no password, key, or connection-string credential reaches this page.