information field and a type field — with the agents that use it, how many memories it holds, how many people contributed, and when it was last saved to.
Counts include private memories. Their content stays visible only to the people who saved them: the list on a base’s page shows what you may see (“8 of 33 visible to you”).
A base greyed out with “not configured correctly” is missing a required field; a base marked “not found in code” is referenced by an agent but no longer exists in the deployment.
A memory base
Click a base to see its memories with search, a Mine filter, and filters for visibility, type and creator. Select rows to change access or delete in bulk — the same dialogs as in Knowledge. “Open in Knowledge” reaches the generic item tools.Map
A base’s Overview tab draws the base as a cloud: one dot per passage of a memory, placed from its embedding so that near means similar, and rotatable. Named regions float over the cloud and are listed as chips underneath with how many passages each holds — a region is a cluster of positions, named from the words that set it apart from the rest of the base, read out of the text index the search already keeps. No model is asked, so a region’s name is the base’s own vocabulary, in the clipped form the index stores it in. Selecting a chip dims everything outside that region, and memories in a conflict group are ringed. Hovering a dot names the memory it came from. Selecting one draws lines to the passages worded most like it and opens a panel on that memory: its type where the base declares one, then whatever the base recorded about it — how many passages it was split into, how much text it holds, when it was added and when it last changed, and where it came from — a link to the memory itself, and the memories worded most like it. A memory appears once in that list however many of its passages are related, so a long memory no longer fills the panel with its own name. Selecting a region chip while no dot is selected opens the panel on the region instead, listing the memories it holds and how many of each one’s passages fall inside it. A memory base grows over time, so the cloud can also be filtered by when a memory was added, using the slider under the chips. Memories outside the window dim rather than disappear, so the shape of the base stays put while you watch it fill in. The slider is only offered where the base actually spans more than a day. Only passages you may read are drawn, so a base with private memories draws fewer dots than it has passages; the counts under the cloud cover the whole base and never show content you may not see. A large base is sampled, with the caption saying how many of how many passages are drawn. A base has to be mapped once before any of this appears, and until then the tab says so — see Map in Knowledge for what an administrator runs.Usage
Every time an agent is given a memory for an answer, that use is recorded — the memory, the agent, the conversation and the time, never the content. A base’s page shows how many memories were never used, the list has a Last used column and a Usage filter (never used, not used in 90 days), and selected memories can be archived in bulk: they leave recall and the counts, and can be restored in Knowledge. A memory’s page lists its recent conversations; the link opens only conversations you may read. Guest chats count too, shown as “Guest”.Conflicts
Find conflicts on a base’s Conflicts page scans the shared memories: memories that say nearly the same thing are grouped as near-duplicates, and similar memories that disagree are judged by the agent’s model and listed as contradictions. For each group you can keep one (the others are archived), merge near-duplicates into a single memory with a suggested wording that credits all authors and keeps the usage history, or mark the group as not a conflict so it never comes back. Private memories are never scanned. Changing a memory needs write access on it; the page disables what you may not change.A memory
Each memory shows its wording, why it was saved, the source conversation when the base records it (an optionalsource_session field), who saved it and when, and who can see it. Make private and Delete are available to the creator, admins, and people with an explicit write grant on the memory. Its Usage section shows how often it was given to an agent and the recent conversations.