Memory
Memory vs. knowledge base
They solve different problems and work well together.
| Knowledge base | Memory | |
|---|---|---|
| Source | Files you upload | Past conversations |
| Written by | You | The agent, automatically |
| Example | "The refund policy is 30 days." | "This customer is on the Enterprise plan and prefers email." |
How it works
Memory in Studio is fully automatic. The agent has no memory tools and makes no decisions about it.
- Before the agent thinks, Studio fetches memories relevant to the message.
- Those memories are added to what the agent sees.
- After a successful turn, the exchange is written back.
There is no "agentic memory" mode to configure, and nothing for the model to get wrong.
Supported providers
| Provider | Credential |
|---|---|
| Mem0 | API key |
| Supermemory | API key |
| MaxiMem | API key |
Set it up
1. Connect a provider (admin)
Sidebar → Memory → Connect provider → choose the provider → paste the API key → save.
The key is encrypted and never returned.
2. Attach it to an agent
Agent Builder → Memory section → pick the connection.
Attaching memory needs only Editor on the agent, with no connector permission. Every member can read memory connections by default, which is what makes the picker work for non-admins.
To turn memory off for an agent, clear the selection.
Scope: who remembers what
Memories are separated by organization, agent and user. One person's memories with an agent do not leak into another person's conversations with the same agent.
When memory is unavailable
If the provider is slow or down, the run still goes ahead, without memory, and a warning is recorded on the run. A memory outage degrades an agent; it does not break it.
You will see these warnings in Audit traces.
When to use memory
| ✅ Good fit | ❌ Poor fit |
|---|---|
| An assistant used repeatedly by the same person | A one-shot extraction agent |
| Customer-facing agents that should recall context | Anything where each run must be identical and reproducible |
| Long-running projects and cases | Storing authoritative policy. Use a Knowledge base instead. |