memory_schema

Defines the per-power-user memory the agent maintains: publicFields (a power-user-visible profile) and privateFields (the agent’s working notes). Shapes…

memory_schema — Memory schema

Defines the per-power-user memory the agent maintains: publicFields (a power-user-visible profile) and privateFields (the agent’s working notes). Shapes what the agent remembers and how.

Section key memory_schema · Shape object · Tier All plans
Edit in the dashboard: Memory page
Related: Memory guide

Fields

Field	Required	Type	Allowed values / constraints	Default	Description
schemaVersion	no	integer	—	—	Starts at 1; the server bumps when keys/types change.
publicFields	no	array of object	—	—	Power-user-visible profile fields. Each: { key (snake_case), label, description, type (string|longtext|enum|multi_enum|boolean|integer|date), options (for enum), required, elicitationPriority (high|medium|low|never), elicitationPrompt }.
privateFields	no	array of object	—	—	Agent-only working notes. Each: { key (snake_case), label, guidance, maxLength, retentionPolicy (persistent|rolling), rollingLimit }. A field may instead be a structured, queryable list by adding kind:‘record_array’ with keyField (the upsert key), recordSchema:{ fields:[{ key, type (string|number|integer|boolean|date), required? }] }, and optional maxRecords. The agent upserts records via update_user_memory and filters them with query_user_memory_field.
updated_at	no	string	—	—	Auto-stamped on write.