Memory files, limits and history

Every memory is a small file on this computer, and you can read or edit it yourself. This page covers what a memory file contains, the limits that apply to it, how Oda keeps its older versions, and how the memories reach the model. To save and manage memories in the app, see Memory.

What a memory file looks like

Oda keeps each memory as its own file on this computer, named with the memory's id.

• One set of files holds your global memories, used in every chat. Each workspace folder has a set of its own, used only by chats in that folder (see Workspaces, files and permissions).
• The id is eight characters: the digits 0 to 9 and the lowercase letters a to f. A file whose name is not a valid id is not treated as a memory.
• A workspace's set of files sits in a folder named with the workspace's key: a folder name of letters, digits, dots, underscores and hyphens, beginning with a letter or digit, and never . or ...
• A file opens with a settings block between two --- lines, the frontmatter, and the memory's text follows the block:

---
title: Reply language
enabled: true
source: user
---

Reply in short bullet points.

• title (required): the memory's name. Oda normalises it to a single line with single spaces.
• enabled (required): true or false. A memory that is turned off stays in the list and is not sent to the model.
• source (required): user or ai, whoever saved the memory. A memory Oda saved itself is marked saved by the agent.
• sessionId, created and updated (optional): the chat an Oda-saved memory came from, and when the memory was created and last saved.

The text below the block is the memory itself; Oda trims it at the ends.

The limits that apply

The defaults, and the range each value can be set to:

• Saving, changing, turning on or restoring a memory over its title or text limit is refused; so is a change that would take the memory a chat receives over its token limit. The message names the value and the limit.
• Turning a memory off and deleting it are never refused.
• The token estimate counts about four characters per token.

Versions and history

Every change to a memory keeps the text it replaced as a version. Versions are kept in a history area, apart from the memory files.

• A version's name starts with the moment it was saved, in the form YYYYMMDDTHHMMSSmmmZ-<source>, with a number added when two versions carry the same moment.
• The source says where the change came from: chat for a change from a chat, settings for one created or edited in Settings > Memory, restore for a version restored, undo for a chat change undone, external for an edit made outside the app, and found for the first text of a file created outside the app.
• Only the newest versions are kept: ten by default, and older ones drop as new ones arrive. Saving the same text again saves nothing, and the same text is kept once, as the newest version.
• Deleting a memory removes its file and marks it deleted: it waits under Recently deleted in Settings > Memory, and its earlier text stays as a version. Restoring it writes the text back and keeps the replaced text as a version of its own, so a restore can itself be undone.
• A version that cannot be found reports No saved version "<id>" of this memory exists.

Changing a memory

In the app, a change to a memory goes through a check first:

• A change must give the title, the text, or both: Give a new title, a new text, or both.
• The title and text are checked before saving: A memory needs a title., A memory needs some text., A memory title is limited to <n> characters; this one has <m>., and A memory is limited to <n> characters; this one has <m>. Shorten it or split it into several memories.
• A change that changes nothing is answered with a note that the memory already had that title and text, and saves no version.
• A change that names a memory this chat cannot find is refused: No memory with the id "<id>" exists in this chat's memory. Call memory_list for the current ids.
• Any other failure reads The memory could not be changed: <reason>.
• Every change refreshes the list in Settings > Memory, and it applies from the next step.

You can also change a memory in its file. Oda reads the files again as it works, so a change you save there applies from the next step, with no restart. When Oda next saves that memory, it keeps your outside text as a version first.

When a memory file has a problem

Oda checks each memory file it reads. A file that fails is listed as a problem in Settings > Memory and is not sent with your messages.

• A file that cannot be read reports what is wrong: The file does not start with a --- frontmatter block., The frontmatter is not valid YAML: <message>, or The frontmatter fields <names> are missing or invalid.
• A file over its size limit, or a memory over its title or text limit, is reported too: The file is larger than <n> bytes., or The memory is longer than <n> characters or its title longer than <m>; shorten it in the file.

Correct the file and save it again; Oda reads the files again as it works, so the fix is picked up at the next step.

How memories reach the model

• The memory travels with your messages and stays part of the chat. The complete memory is sent the first time; after that, Oda adds a short note only when the memory differs from what was last sent.
• The note lists what was added, changed or removed, and says that the change applies from then on, while the rest of the memory is unchanged.
• If a long chat is compacted (see Chat compaction), the memory can be removed with the older part of the chat; the complete memory is then sent again.
• A memory that is turned off, or whose file has a problem, is not sent.
• Memories are kept only on this computer and are never synced; like the rest of a chat, they are sent with your requests.

Questions, answered

Where are my memory files kept?

In Oda's own folder inside your user profile on this computer: one set of files holds your global memories and one set for each workspace folder. Each memory is a plain text file named with its id, and Oda never syncs them anywhere.

Can I add or edit a memory file myself?

Yes. Save it in the right set, with a valid id as its name and a valid settings block, and Oda picks it up as it works, so your change applies from the next step. When Oda next saves that memory, it keeps your outside text as a version first. A file whose name is not a valid id is not treated as a memory.

Which lines does a memory file's settings block hold?

title, enabled and source are required, and sessionId, created and updated are optional; the memory's text goes below the block. enabled turns the memory on or off, and source records who saved it.

What limits apply to one memory?

One memory's title, text and file each have a default limit: 120 characters, 2000 characters and 64 KiB. The whole memory a chat receives is bounded as well, at about 8000 tokens counted at four characters per token.

How many versions does Oda keep for a memory?

The ten newest by default, and an installation can keep between 2 and 100. Older versions drop as new ones arrive, and saving the same text again saves nothing.

When does a change to a memory apply?

From the next step, whether it was made in a chat, in Settings > Memory, or in the file itself: Oda reads the memory files again as it works.

Why is a memory not sent with my messages?

It is turned off, or its file has a problem. A memory turned off stays in the list but is not sent; a file Oda cannot read, or one over a size, title or text limit, is listed as a problem in Settings > Memory and is never sent.

What does the source line in a memory file mean?

It records who saved the memory: user for one you saved yourself, ai for one Oda saved for you. A memory Oda saved is marked saved by the agent in the list.

What does the token estimate for a memory mean?

It is Oda's estimate of how much of the model's reading space the memory takes, counted at about four characters per token. Settings > Memory shows the estimate, and the same figure is used for the message limit.