Memory
Bots remember what matters between conversations, and you can read, download or delete anything they keep.
What a bot remembers
Each bot writes notes as it works: your preferences, facts about the job, what it tried. Its notes are
indexed in a file called MEMORY.md.
You can also just tell it: “remember that invoices go to the finance folder”.
A bot keeps its notes short, one fact per line. When something changes, it rewrites the old note
instead of adding a second one, and it deletes notes that no longer hold. It keeps at most 4 KB of
notes in MEMORY.md, merging or removing notes to make room. You can still add more by hand.
To see what a bot remembers, click its name at the top of the chat and open Memory. Each note can be downloaded or deleted.
Shared memory
Some things all your bots should know, such as your name, your company, or how you like reports written. Those go in Shared memory: your bots in the current space read these notes and keep them up to date. Other people’s bots in the space don’t see them.
A bot rewrites a shared note only with its observed document ID and revision. If another bot changed the note, or it was deleted and recreated, the save is refused. The bot must reread and reconcile the complete note before trying again; the tool does not merge text automatically.
Local notes that no longer fit in the active context can be found with search_local_memory and
read with read_local_memory, without connecting a memory provider. Search matches literal text.
Search results include a document ID, revision and snapshot. When reading a search result, pass its
revision as expected_revision and snapshot as expected_snapshot, including on the first read.
A changed, deleted or recreated note requires a fresh search instead of silently substituting a new
version. An unpinned read deliberately reads the current note at that path. Long notes are read in
bounded chunks with the same revision and snapshot checks. These tools read only the current bot’s
private notes and the current user’s shared notes in this space. They are unavailable to external conversations and after outside
messages enter the run. Search currently scans the authorized local collection before returning a
bounded page; it is not a semantic index.
Find it in Settings → Memory. Deleting a document removes it and its saved versions. It doesn’t remove what conversations already said, or copies made elsewhere, such as downloads or anything a memory provider stored.
Add client knowledge
In Shared memory, choose New note to add business facts or Import file to bring in a
UTF-8 .txt or .md file, up to 32 KiB. The note keeps its original title or filename and a source
badge. You can edit, download, or delete it in the same panel. Imported files become local text
notes; this does not crawl websites or parse PDFs, spreadsheets, or images.
Notes are available to your bots in this space through shared-memory context and local retrieval. They are data to consider, not instructions that grant new permissions. Source details survive an account export and import. Updates check the observed document ID and revision so a stale editor cannot overwrite another change or a replacement document.
Memory providers
Optionally, connect a memory service so bots can also recall facts by meaning, not just by reading their notes. In Settings → Memory, choose Connect memory provider:
- Supermemory: its cloud service, or your own instance.
- Serenity: choose Recall and write, or Recall only to keep it read-only.
- Honcho: reads from an existing Honcho peer and never writes to it.
Once connected, Default scope decides what bots share in the provider:
- Isolated: each bot recalls only what it saved. This is the default.
- Shared: bots in the space recall from one pool.
Each bot’s settings also gain a Memory scope under Advanced, so one bot can differ from the default.
Open work
Separate from memory, each bot keeps a short list of Open work: things it has started and not finished. It is in the bot’s settings. You can add items for it, or mark them complete.
Memory across spaces
Memory never crosses spaces. A bot in one space can’t read notes from another.