Configure agent memory
Control what your agent remembers across conversations.
Intermediate · ~10 min · Prerequisites: a published agent
Building and editing agents is admin-only. Members can run and observe agents, but only admins can create or change them.
What you'll do
Review how your agent's memory works, decide whether to enable it, and understand what gets retained — and when to clear it.
How agent memory works
By default, each agent conversation is stateless: a fresh thread starts with no recollection of previous threads. Memory changes that. When memory is on, the agent retains facts and preferences a member has shared across conversations — so a member doesn't have to re-explain their context every time.
For the full technical details of what is stored and how it is scoped, see Memory.
Turn memory on or off
Go to /admin/agents/<slug>/edit and open the Memory section of the editor.
- Toggle Enable memory on to let the agent retain cross-conversation context for each member.
- Toggle it off to make every conversation independent. This is the right choice for agents handling sensitive workflows where carryover context would be a liability — for example, a compliance or HR triage agent.
Save the draft and publish a new version for the change to take effect for members.
What gets remembered
When memory is on, the agent stores information the member explicitly shares or that the agent infers from repeated patterns — things like preferred output format, a project they keep referencing, or their role. The agent uses this to skip re-asking for context it already has.
Memory is per-member — what user A shares is never surfaced to user B. Each member's memory is also scoped to this agent; a different agent has its own memory store.
Members can view and clear their own memory for any agent from the agent's chat settings. Admins can reset memory org-wide from the agent editor.
When to reset
A few situations where resetting is the right call:
- The agent's role changed significantly. Old memory shaped by the previous role can give stale or contradictory context.
- A member reports the agent making wrong assumptions. Stale memory is often the cause. Ask them to clear their own memory first; if the problem persists, it's likely an instructions issue.
- You're testing a freshly published version. Use the test panel — test-panel conversations don't write to memory, so your tests stay clean.
To reset memory org-wide, open the Memory section in the editor and click Reset all member memory. This takes effect immediately and cannot be undone.