Skip to main content
Memories give an agent recall across conversations. After each conversation, a memory service extracts important facts (“user prefers concise answers”, “their account ID is X”) and stores them. On future runs the agent retrieves the relevant ones and folds them into the prompt — so the user doesn’t have to repeat themselves and the agent feels like it remembers them.
Memories library

​
Two memory types

You can attach a service of either (or both) type to an agent.

​
Creating a memory service

  1. Open Agent Framework → Memories.
  2. Click Create Memory Service.
  3. Configure:
Save the service. It now lives at the project level and can be attached to any agent.

​
Attaching to an agent

  1. Open the agent → Memory tab.
  2. Select a memory service.
  3. Save.
When attached, the agent automatically gets two tools:
  • memory_search — retrieve relevant memories for the current turn.
  • memory_add — explicitly write a new memory mid-conversation (in addition to automatic extraction).
Both tools can be marked Requires Approval if you want a human review step before any memory is written.

​
How memory is keyed

Memories are scoped by namespace — typically by user. The namespace is read from the request context (or HTTP headers) and isolates one user’s memories from another’s. This means a single shared agent can serve many users without their memories bleeding across sessions.

​
When to use memories vs alternatives