Ask Pi to remember a project fact: builds require Node 26.
Pi stores it with SQL through the real memory tool; the audit journal records the write. Nothing waits for approval.
Open /memory: the Usage tab shows the store at a glance.
The Journal tab shows the journaled DDL and insert; the detail view exposes actor, timing, and the undo snapshot.
The Browse tab runs a read-only query and finds the stored fact.
Protagonist: memory.
Point: the agent owns the schema, every call is journaled, and recall is one query away.
The model is scripted; tool execution, database changes, and Pi's terminal UI are real.
The recording uses synthetic data in isolated OS-temp storage, never the user's memory database.
# memory demo
1. Ask Pi to remember a project fact: builds require Node 26.
2. Pi stores it with SQL through the real `memory` tool; the audit journal records the write. Nothing waits for approval.
3. Open `/memory`: the Usage tab shows the store at a glance.
4. The Journal tab shows the journaled DDL and insert; the detail view exposes actor, timing, and the undo snapshot.
5. The Browse tab runs a read-only query and finds the stored fact.
Protagonist: memory.
Point: the agent owns the schema, every call is journaled, and recall is one query away.
The model is scripted; tool execution, database changes, and Pi's terminal UI are real.
The recording uses synthetic data in isolated OS-temp storage, never the user's memory database.