Memory
NEXUS keeps one shared, durable memory store — the same store the app itself maintains — instead of per-agent or per-client note files. Agents write to it as they work through the memory_* tools, you curate the durable parts of it by pinning, and every entry is versioned, scoped, and secret-scanned before it lands.
Three properties define the store:
- Scoped. Every entry names where it is visible — private to one agent, one session, one workspace, one project, or everywhere. Visibility is enforced on every read; an agent is never shown an entry outside its own scopes.
- Versioned. Entries are immutable. An edit writes a new version that supersedes the prior one, and a deletion is itself a version — a tombstone — so history is never silently rewritten.
- Guarded. A body that looks like a credential is refused with the detected pattern named. Memory never stores secrets.
Where memory shows up
| Surface | What it shows |
|---|---|
The memory_* MCP tools | Write, search, list, read, edit, and delete entries from any connected agent or CLI. |
| The Pinned Memory panel | The human control surface for pinned rules and data mappings, with scope filter chips and the Promote/Discard queue for agent proposals. |
| An agent's Memory card | What that agent can recall — entry counts by scope, a freshness distribution, and a write heatmap. |
| The Neural Map | Each memory entry as a node; entries whose freshness has left active render dimmed. |
In this guide
- Scopes — the five scopes, their visibility rules, and how surfaces group them.
- Pinning & Promotion — pinned rules and data mappings, the Pinned Memory panel, and promoting agent proposals.
- Versions & Deletion — immutable versions, tombstones, freshness, and retention.
The knowledge-fabric switch
The whole store rides on the knowledge fabric's master switch — Knowledge fabric enabled, on by default. When you turn it off, every memory_* call is refused, reads included, and nothing new is written anywhere.
Where to go next
- Pinned Memory — the getting-started walk through pinning your first rule.
- Memory tools — the exact
memory_*tool contract. - Memory card — reading one agent's recall at a glance.