Skip to main content

Brain Memory Brain

Start in one conversation​

Run anda memory guide for an offline introduction. No extra Brain or MIB setup is needed for ordinary memory. Tell Anda: “Remember that I prefer short release notes with a risk section.” After background processing, use /new and ask what it remembers. A reply saying “remembered” is not a storage receipt.

anda memory and TUI /memory show connection and processing status without model calls. The browser Memory workspace shows source-backed records and conversation activity. About you, Brain itself and System (the Brain's own $self and $system), a name search that calls no model, and the subjects and objects of records open entity pages: an entity's claims grouped by relation, each marked with Brain's current belief under the standard recall policy, with statements replaced by newer ones kept as history and a small graph of the related entities on that page. Records, entity pages and search list claims whose sources can be verified for you, and the Brain's own claims that carry no source at all, such as memory upgraded from KIP 1 and Maintenance conclusions; those are marked unsourced and read-only. Source quotes link to original messages when their stored mapping and digests match. Search may call a model and does not retry automatically.

Review a record's Correct, Stop using or Delete preview before confirming. Stopping use retains archived records; deletion purges the previewed native set. Source exclusions survive restart, and processing Notes are reset. Original chats, files, logs, backups and already delivered context remain. Unsupported or incomplete source scopes cannot be removed through this interface. A correction first asks which change it is: I said it wrong replaces your earlier claim, Things changed records a new value from now while the old one stays true for its time, and You recorded it wrong asks Brain to re-read the original message and repair the record. Deletion reports its erasure plan: completed, partial when a surface could not be verified, or blocked by a legal hold.

To start a conversation with restricted memory, run anda agent run --memory-mode no-store --prompt '…' or --memory-mode off; the chat apps don't offer a memory mode. These modes constrain automatic Brain access, including background writes; they are not incognito modes for chat or providers. Restricted modes also reject nested agents, bookmarks and cron changes.

For questions that must survive across conversations, use Set up a memory inbox or anda memory inbox setup. Review and apply the configuration, then explicitly run anda restart. Custom runtime files and environment overrides are preserved. Subscribe to a record to get a real native inbox item when it changes. In TUI, use /memory inbox, /memory answer <number> <text> and /memory retry <number>; retries reuse the saved event and text.

Read the inbox with anda memory inbox. Follow the printed anda memory inbox --cursor <next_cursor> command for another page. With --json, the cursor is in result.next_cursor.

MIB comparisons and business learning are advanced, separate features. anda memory evaluate plan --help describes the isolated CLI workflow in MIB-enabled builds. Costs may be incomplete. A memory comparison does not approve business learning or prove improvement.

Anda Brain is the long-term memory system behind Anda Bot. It is not a plain vector database or an ever-growing Markdown file; it is a memory brain designed for agents.

Brain turns conversations, files, tool results, and channel context into a growing Cognitive Nexus: people, projects, preferences, events, decisions, timelines, and the relationships between them.

Three-Phase Loop​

Formation​

Formation encodes useful conversations and work results into structured memories. It does not only ask whether a sentence appeared; it asks who, which project, what preference, what decision, what event, and when it happened.

Recall​

Recall lets Anda query the memory graph with natural language. Good recall explains the current task instead of returning nearest text fragments alone.

Maintenance​

Maintenance consolidates fragments, merges duplicate information, reduces the influence of stale knowledge, and preserves timelines when facts change.

How to Teach Anda​

You do not need to maintain memory files. A better approach is to state stable facts, changes, and preferences clearly.

Remember: I like short release notes, but keep a risk section.
The default model provider for this workspace changed from A to B.
When we mention Alice, we mean the mobile team designer.
Do you remember the background of the payments migration project?

What Makes a Good Memory​

  • Context: project, person, file, channel, or time range is clear.
  • Evolution: when a preference changes, state the old and new versions.
  • Boundaries: temporary information can be marked as only valid for the current task.
  • Correction: when Anda remembers incorrectly, state the correct version directly.

Local Data and Model Providers​

Memory graph data is stored locally in ~/.anda/db by default. Model providers may still participate in memory formation, recall support, and summarization, so choose providers and endpoints according to your privacy needs.

To make a provider preferred for memory-related tasks, add the brain label:

model:
  providers:
    - family: anthropic
      model: "deepseek-v4-pro"
      api_base: "https://api.deepseek.com/anthropic"
      api_key: "YOUR_API_KEY"
      labels: ["primary", "brain"]

Optional native runtime​

Set brain.runtime_config to a trusted JSON/YAML file relative to the configuration directory; BRAIN_RUNTIME_CONFIG overrides it. Restart to install bindings before Space loading. The browser Brain inbox and TUI /brain inbox, /brain status, /brain formation <id> use the authenticated caller. Reading is not execution permission; retry an answer with the same event key and text. Recall receipts prove delivery only, and Formation acceptance is not completion. The learning feature is independent of mib; semantic, utility, trust and automatic learning require explicit native configuration and authority. Current IM transports are not automatic action adapters. MIB persistent memory does not claim normal/ungated learning or complete costs. Each Formation window is an observed intent with a durable receipt, so an interrupted submission replays the same receipt instead of forming the window twice. recall_memory first waits briefly for the conversation's own pending windows and says which are still being processed. brain_attention also returns due commitments and fired watches since you last looked, and brain_feedback records the assistant's own report as attributed evidence, never a grade.

brain:
  runtime_config: brain-runtime.yaml

Older browser tokens keep working without a re-export: runtime requests retain the original user identity, and the embedded Brain accepts a token that names no audience while still verifying its signature and expiry.