Work with memories

Use Brain to store a statement, find it later, and correct or remove it. Each operation acts on the selected product’s memory.

Before you start

You need access to Brain in your product. In the web app, you can search, browse, correct, and delete shared memories. Creation is available through agents over MCP or REST, not through the web app.

For MCP, use a product-scoped credential with read access to search, list, open, or inspect counts, and write access to add, correct, or delete. Set up MCP first if needed.

Adding and correcting use embedding and language-model tokens; searching uses embedding tokens. Deletion is not metered or blocked by the token allowance. See usage and limits.

Add a memory

1. Give your agent the text to store with brain_memory_add. For an example product named Acme, use: “Acme requires an email receipt after checkout.” Replace that sentence with a fact about your product.
2. Choose scope: shared is the default; private is visible only to the writing agent. Choose source_authority if needed: policy, official, team, or informal. The default is official. You can attach an object in metadata.
3. Keep the returned memory_id so you can retrieve or change the record later.

One write can produce the original text and several derived facts. The number of stored memories need not match your number of calls.

Search

1. Open Brain’s search page and ask a question, such as “What does Acme send after checkout?” With MCP, call brain_memory_search with that text as query.
2. Review the groups below. A result carries its match score, kind, and authority. Search matches meaning rather than requiring the same words.
3. Open a relevant result to inspect the full memory.

Any group can be empty. A product without consolidated memory usually has direct results only; cognition adds patterns and intentions over time.

For MCP, limit is a maximum per group, from 1 to 100. scope can be shared, private, or both; the default includes the shared pool and the agent’s own private notes. A person sees only shared memories.

Browse and open a record

1. Open Browse to list current memories in order. With MCP, use brain_memory_list; choose order: "desc" for newest first or "asc" for oldest first, and page with limit and offset. The maximum page size is 1,000.
2. Select a memory, or call brain_memory_get with its memory_id. The detail includes content, current-version status, replacement history, authority, kind, tags, metadata, confidence, and writer.

The list’s total is the number matching your scope across all pages, not the current page’s length. Superseded records are absent from the list. A record outside your product or another agent’s private scope reads as not found.

Correct a memory

1. Open the memory’s detail page and correct its text. With MCP, use brain_memory_update with memory_id and replacement content.
2. Open it again and confirm the corrected text. Search for the corrected statement to check what readers now retrieve.

Correction changes the text, not its scope, authority, history, or recording time. If a decision has changed rather than been recorded incorrectly, add a new memory and let Brain handle supersession under the authority rules.

Delete a memory

Deletion has no undo in the web app. Recovery requires a snapshot restore, which replaces the product’s entire memory rather than recovering one selected record.

1. Open the memory and check that it is the record you intend to remove. You can delete shared memories in your product or your own agent’s private memories.
2. Delete it from its detail page, or call brain_memory_delete with memory_id.
3. Search and browse again to confirm the intended statement is gone. If related statements remain, inspect their records before removing them.

Deleting a derived fact leaves its original text and sibling facts in place. Removing the whole write means removing all of those records. Brain repairs the replacement history around the deleted memory.

Verify it works

After adding a memory, retrieve the returned ID and compare its content with the submitted text. In the web app, a shared memory should also be readable through search or Browse. A private memory must be checked by the agent that wrote it.

The counts at the top of Browse, or brain_memory_stats with the same read scope, give a broader check: total memories, facts, summaries, identity statements, graph nodes and relations, and distinct entities. Counts alone don’t prove a particular statement was stored; inspect that record too.