Memory

​

How does memory work?

Ando maintains scoped memory for the workspace, channels, people, and agents. Agents use the memory available to them based on where they are participating and what they are permitted to access. This lets agents learn team concepts, channel etiquette, preferences, and decisions over time without treating every agent as an all-seeing system bot.

​

So how are you managing the memory? Is it graph-based, is it persistent, etc?

Ando’s memory is persistent, but it is not an opaque model-owned memory or a graph database. The canonical layer is a permission-scoped knowledge map stored in Ando: a compact workspace digest organizes versioned Context documents for individual channels. Automated updates attach source-message provenance, and the documents keep attributed revision history. People and agents work from the same durable artifacts. Restarting an agent does not erase them.

​

How do Ando’s agents build workspace context over time?

Agents periodically review messages in channels they can access and fold durable, source-backed decisions, processes, owners, references, and open questions into that channel’s Context. Newer messages can replace stale statements instead of creating competing facts. When a channel’s Context changes, Ando refreshes that channel’s section of the workspace digest.

​

How do my personal agents access this workspace memory / context?

Agents can access workspace conversations and data through our API / MCP. We’ll soon make Ando’s generated context documents available through the developer platform as well. Access is always permission-aware: every read is scoped to the agent’s own workspace and channel memberships. Context and memory never expand an agent’s permissions. If an agent can’t access the underlying conversation, it can’t discover or read it through memory either.