Memory
The Memory view displays stored fact records associated with a selected session.
This is currently an inspection view. Edit memory through the appropriate runtime flow or service rather than treating Studio cards as an editor.
Session-oriented view: Studio currently loads memory after you select a session. Do not treat this page as a complete user-wide inventory of every User-scoped fact.
Select A Session
Section titled “Select A Session”The session list is grouped by agent and uses the same session summaries as the Events view. Select a session to load its memory records.
User-scoped facts can be reused by the runtime across sessions, but the current Studio navigation remains session-based. A fact should not be assumed to appear under every session associated with the same user.
Search And Filter
Section titled “Search And Filter”Search matches records currently loaded into the browser:
- Key
- Value
- Kind
Kind chips are also generated from the records currently loaded and can filter categories such as:
factprofilesummaryusage
Other kinds can appear as the runtime evolves or applications store their own records.
Memory Cards
Section titled “Memory Cards”Each card shows:
- Kind.
- Key.
- Last update time.
- A preview of the value.
Select a card to open the full value. JSON strings are formatted when they can be parsed.
Diagnosing Agent Memory
Section titled “Diagnosing Agent Memory”Use this view when:
- A user preference was not recalled.
- A rolling summary appears incomplete or inaccurate.
- Usage totals do not match expectations.
- A memory write happened but later context did not use it.
Compare the memory record with the Events chain. A stored fact can exist but still be absent from a response because of scope, user/session identity, model behavior, or later updates.
Normal scoped facts are automatically supplied to the model, including when the
Agent node uses Context None. Internal keys beginning with __ follow their
dedicated runtime behavior instead.
Privacy
Section titled “Privacy”Memory can contain persistent user information and normal facts can be sent to the configured model provider. Do not store credentials or authentication secrets as facts. Do not share screenshots or record values without checking for personal or confidential data.