Memory

A memory belongs to the tron, and the agents wired to it use it — reading, or reading and writing. Five kinds; the platform keeps what they hold.

Buffer

The last N messages of the conversation, word for word, read from the chat history. No loss on recent context, no long-term recall.

Summary + buffer

The recent messages word for word, plus a running summary of everything older, rewritten every few turns by a model call that counts with the turn.

Wiki

A folder of markdown pages the agents read and write during a run, kept by the platform with the history of every page and a trash. Yours to read and edit in the Garage.

Entity

One card per customer, product, person or place, with its kind, attributes and notes, updated by the agents after each turn.

Read or write

Each wire from a memory to an agent says what that agent may do: read only, or read and write. Two agents writing the same page at once never overwrite each other: the second is told and tries again.

RAG

A memory that is a library of documents. The agents search it with search_documents and read a document with read_document, with citations. Wired to read and write, an agent can also add notes with memory_add_document, remove them with memory_remove_document and list them with memory_list_documents (runtime 0.28.0); a note is searchable within seconds. You add documents from the Garage, upload them, or write a note. Its preset, embedding model and key work as in any library (see Libraries and documents).

Knowledge graph

A RAG or an entity memory can build a graph: entities and the relations between them, each relation with the documents it came from. For a RAG memory a model reads every chunk once (a cost per chunk, shown under Graph in Usage, and a warning before you switch it on); an entity memory adds relations at the end of each turn. Agents follow it with graph_neighbors (runtime 0.27.0). Garage → Memory → View shows it, and lets you remove a relation or rebuild.

Shared or per session

Every memory says its scope. Shared (the default) is one copy for the whole tron. Per session is one copy for each conversation: a chat session, a bridge conversation, a Tron API session. A per-session RAG memory still shares its base — the documents a person uploaded — and keeps per session only the notes the agents write there. A buffer or a summary also follows the tron's memory mode; the other kinds follow only their own scope. Changing the scope deletes nothing, and a session's copy goes when the session goes. Per session needs runtime 0.29.0 on a wiki, entity or RAG memory.

Erasing

Erase deletes what a memory holds — pages and their history, summaries, entities — and keeps the memory, its settings and its wires. A buffer holds nothing of its own: its messages are the chat history.