Documentation / Agent Memory

Agent Memory

Updated April 9, 2026

Settings Memory tab

Overview

The Memory tab in Agent Builder → Settings → Memory shows all persistent memories stored by your agents across conversations. Agents use memory to remember user preferences, prior decisions, and accumulated context — so they can pick up where they left off.

How Agent Memory Works

When an agent decides something is worth remembering — a user preference, a decision made, or a key piece of context — it stores it as a key-value pair in the memory table. On subsequent conversations, the agent retrieves relevant memories and uses them to inform its responses.

Memory is stored per entity (typically a user ID or session identifier) and per memory type. The table shows all memory entries across all agents and entities on your site.

Memory TTL

The Default Memory TTL setting controls how long memories are kept before being automatically deleted. Set the number of days and save.

  • Set to 0 to keep memories indefinitely (they will never expire automatically)
  • Memories with an explicit TTL set by the agent override this default

Viewing and Filtering Memories

The memory table shows all stored entries with the following columns:

  • Type — the category of memory (e.g. preference, decision, context)
  • Entity — the user or session the memory belongs to
  • Key — the memory identifier
  • Value — the stored content (truncated; hover to see the full value)
  • Expires — the expiry date, or — if the memory has no TTL
  • Updated — when the memory was last written

Use the Type and Entity dropdowns to filter the table. Click Filter to apply.

Deleting Memories

Click the × button on any row to delete that individual memory entry immediately.

To remove multiple entries at once, filter by type or entity and click Clear Filtered to delete all matching entries. Click Clear All Memories to wipe every memory entry on the site.

The memory table is empty until your assistants have had enough conversations to start accumulating context. Once memory entries exist, they appear here automatically.