Skip to content

Use Agent Memory

With memory on, Controller and your agents keep short facts between conversations. They remember what you tell them about yourself and how you like to work. An agent can also keep team memory: facts for everyone who uses it, such as where the team keeps its docs. Memory holds only what a person or a chat saves. Nothing is learned in the background.

Memory Holds Who changes it
Controller memory What Controller remembers about you. You, in your chats with Controller or in Settings → Memory.
About you (per agent) What one agent remembers about you. Each person has their own. You, in your private chats with the agent or from its Memory button.
Team (per agent) Facts every user of the agent benefits from. Only the agent’s owner, in their own private chat or from the Memory button.

Private chats are chats in the app, Slack direct messages with a matched member, and conversations through an assistant connector. Slack channel threads and scheduled runs act for no one present: they get no personal memory and only read team memory.

An entry is one short sentence, up to 1,000 characters. A memory holds at most 100 entries and 6,000 characters. Chats never save passwords, keys, payment details or one-time codes.

In the app: open Agents → Support helper → Edit, switch on Memory, then Save changes. Test chats use memory at once; the live agent uses it after you publish.

With an assistant: call agent_update, then publish with agent_publish:

{ "agentId": "<agentId>", "memoryEnabled": true }

Test and Live keep separate memories, as they keep separate chats. Nothing is copied when you publish, so team facts saved in Test are not in the live agent.

Controller memory is on by default. Turn it off with Controller memory in Settings → Memory.

In the app: Settings → Memory → Saved memories lists Controller and every live agent that remembers something about you. On an agent’s page, the Memory button next to Chats opens that version’s About you and Team tabs. Use Add memory to add a line, edit a line in place, or remove it from its menu. Clearing a whole memory is only in the app.

With an assistant: memory_list with no parameters returns your Controller memory and your memory with each agent. With an agent, it returns that agent’s memory about you, its team memory, and whether memory is on:

{ "agentId": "<agentId>" }

The agent’s owner can add "env": "test" to see Test memory. Everyone else sees Live. Each memory has a memoryId, and each entry an index that is never reused.

Add a fact about yourself to one agent:

{ "agentId": "<agentId>", "text": "I review invoices on Mondays." }

As the owner, add a team fact to the live agent with memory_add:

{ "agentId": "<agentId>", "about": "team", "text": "Support docs live in the Notion Support space." }

Leave out agentId to save to Controller memory. Correct an entry with memory_update and remove one with memory_remove, passing its memoryId and index:

{ "memoryId": "<memoryId>", "index": 3 }

Each call returns the memory as it now stands. Changes apply to the next conversation.

Use For
Instructions or knowledge files What the agent must always know: policies, product facts, a style guide.
Memory What the agent learns from people as it goes: preferences, team conventions.
Workflow data Records the agent keeps track of, such as a status per customer.