What is User Profile Memory?
Also called persona memory.
User profile memory is a persistent, structured record of durable facts about an individual user, such as their role, preferences, working context, and constraints. Unlike conversation history it is intentionally small, curated, and injected into most sessions. It exists so an assistant does not have to relearn stable details in every new conversation.
The distinguishing property is stability. A profile stores facts expected to hold across sessions, such as a preferred language, a timezone, a technical level, or an ongoing project, and deliberately excludes situational details that were true only during one conversation. Keeping it small is a design requirement, since profile content is injected into nearly every request and therefore competes with task-relevant context.
Structure beats prose. Storing typed fields with explicit keys makes the profile editable, diffable, and selectively injectable, whereas a free-text paragraph tends to accumulate contradictions and cannot be updated precisely. Structure also allows only the relevant subset to be injected for a given task, rather than the whole record every time.
Writing to the profile needs discipline. Automatic extraction from conversation captures useful preferences but also captures one-off statements that were never meant to persist, and an incorrectly stored fact can quietly distort every future session. Common safeguards are requiring repeated evidence before promotion, timestamping every entry, recording where it came from, and asking the user to confirm significant additions.
Profiles carry privacy and product obligations that ordinary caches do not. They hold personal data by definition, so users need to see what is stored, correct it, and delete it, and sensitive inferences about health, beliefs, or finances warrant particular caution or exclusion. Regulatory frameworks in several jurisdictions grant access and erasure rights over exactly this kind of stored personal record.
Key points
- Stores stable, cross-session facts about one user
- Kept small because it is injected into most requests
- Structured fields beat free-text for editing and selective use
- Requires evidence and confirmation before writing
- Users must be able to view, correct, and delete it
In practice
A profile holds four fields: works in logistics, prefers concise answers, uses metric units, and is currently migrating a warehouse system. Each carries a source and a date. A new session about routing software starts with those four lines injected, so the assistant does not ask about units or context again. When the migration finishes, the user removes that field from the memory settings page.