AGENT MEMORY · TIERS AND CONSENT
Agent memory hierarchy: keep a preference across sessions only when approved
Move two statements through working memory, session state and durable memory, then return a week later as the same or a different person.
Event trace
Computed data
Final metrics
Two fictional statements from one user on a shared tablet; nothing is stored. Working memory lasts one turn and session state ends with the session. When asked, the agent offers to remember only the preference, never the one-off remark. Encryption, deletion requests and memory summarization are outside this drill.
Remembered without asking
In session 1, user U1 on shared tablet D9 says "Always give distances in kilometres" and later "I'm in a hurry today". Both pass through working memory and session state. The default Durable write policy, Write everything automatically, with Durable memory keyed by Device, stores both at session end. A week later U1 gets both back, including a remark that was only true that day: PERSISTED WITHOUT APPROVAL, 2 durable items. Working memory is what the model sees in one turn, session state lasts until the session ends, and durable memory outlives sessions, so it needs a key, a retention period and, for personal preferences, consent. On the board, red durable chips were written without consent.
Ask first
Choose Ask before writing. If the user does not approve, nothing is stored: FORGOTTEN AS REQUESTED. Tick User approves when asked: only the preference is stored and recalled in session 2, RECALLED WITH CONSENT, 1 durable item. Never write durable memory stores nothing: NOT RETAINED. The approval box only matters with the ask-first policy.
Whose memory is it
With approval granted, set Who starts session 2 to A different user on the same tablet. Keyed by device, U2 receives U1's preference: LEAKED TO ANOTHER USER. Key it by User account and U2 starts from defaults: KEPT TO ITS OWNER. Under automatic writes the leak carries both items.
Retention
Days until session 2 and Retention of durable memory decide whether a stored item is still there. With approval, 60 days against the default 30-day retention gives EXPIRED BEFORE REUSE. Under automatic writes the same gap recalls nothing, but the verdict remains PERSISTED WITHOUT APPROVAL, because the consent problem happened at write time.
Replay and limits
Any change recomputes the run and rewinds it; the Complete-run preview states the outcome at once. Play and Pause walk through the events, Next event jumps one event, Restart rewinds, Speed runs from 0.25x to 2x and Inspection time seeks from 0 to 60 seconds, where the outcome and final metrics appear. Two fictional statements; nothing is stored. Working memory lasts one turn and session state ends with the session. Encryption, deletion requests and summarization are outside this drill.