AI memory
Memory supplies context across executions. It is not the same as a saved skill or the complete transcript of a chat.
User context
Chat and MCP can use per-user memory in their project context. A user’s remembered preferences do not grant authority to access another user’s resources. Do not put credentials or unnecessary sensitive material into remembered instructions.
Automation context
The automation form shows Memories: Always on. Automation memory supports continuity across that automation’s runs. It is distinct from the interactive user’s Chat/MCP memory and from the automation’s attached skill content.
If a run behaves unexpectedly, inspect its instructions, attached skills, input, and available memory context before repeating it. Changing a prompt does not necessarily erase prior context.
Choose the right mechanism
| Need | Mechanism |
|---|---|
| Repeatable, reviewed instructions | A skill, optionally defined in version-controlled code. |
| A particular conversation’s context | Chat history. |
| Continuity across an automation’s runs | Automation memory. |
| Authoritative business facts | Project records and verified tool results. |
Use only memory-management controls exposed by your installed application. Do not assume deleting a chat resets every memory store or that memory is an audit archive. See skills and runs.