How it works
What mastermem puts into a session, and how memories are saved.
Memories come to the agent
Agents rarely search for what they do not know they are missing, so mastermem pushes memories in at the right moment:
| When | What the agent gets |
|---|---|
| Session start | Your always-on rules |
| First work on a project, server or tool | The memories of that project, server or tool |
| Every prompt | The memories that match it |
| After changes to infra, deploy files or services | The memories that may now be outdated |
The agent can also search on its own with memory_search and read a memory in full with memory_get.
Lessons are saved while you work
When you correct the agent, mastermem asks it at the end of its answer to save the lesson as a short memory. It checks for near-duplicates first and updates those instead. Memories with secrets are refused.
You can tell it directly too: "remember that we deploy with make release" or "forget that".
A memory
- Type:
rule,preference,procedure,fact,incident,project,lessonorlog. - Scope:
global, or what it is about, such asproject:billing-apiorhost:web-1. - Space: your private space or a team space.
- Always on: a few rules can go into every session. When an agent writes one, it waits in
To confirmuntil a person confirms it.
Every change is kept in the history of the memory and can be undone in the dashboard. Memories can carry files such as logos, images or PDFs (up to 25 MB each).
When mastermem is down
Your agent keeps working without memories: every hook gives up after a few seconds. Rule checks pause too, unless an
owner sets When mastermem is unreachable to Block risky commands in the team settings.