Memory

Route /memory. What the agent remembers between sessions.

Namespaces

Memory is partitioned and the partitions never cross.

• default is your own memory, which every session reads.
• agent:<name> is a named agent's, which only that agent reads.

The Scope control switches between them; choosing agent reveals a name box. The namespace in effect is always shown above the results, so there is no way to write into the wrong one without seeing it.

Writing

Text is the fact, in plain language — the release runbook lives in docs/release.md is a good one. Tags are a comma-separated list used for retrieval, like project, release.

Write stores it and the notice confirms it. Facts are additive: writing a correction does not remove the thing it corrects, so prefer one clear statement over an accumulating pile of near-duplicates.

Searching

Query is natural language, not a keyword match — "what do I know about…" is the right shape. Hits come back with their tags and their text.

Deleting

There is no delete. The protocol has memory.search and memory.write and nothing else, so the Delete button on each hit is disabled and says why. Until the core grows the method, removing a fact means editing the daemon's memory store directly.