Attachments in model requests

In DataMind Oda, when you attach a file or an image to a message, what the model receives is not the file itself. Oda replaces every file with a short line in the request, and sends an image as a picture only when the model accepts images. This page follows what each request carries. For adding files to a message and the limits that apply, see Attach files and images to a message.

What the model receives for a file

Every file in a request becomes one line for the model. The line carries the file's name, its size in bytes, a short digest of its contents, and the path of a read-only copy Oda saved on this computer. The file's bytes are never sent to the model.

• Oda reads the saved copy with its file tools when the task needs the contents, and copies it to a writable location before changing anything.
• The line stands in for every file occurrence in the request, including files from earlier messages and files that came back inside a tool result.
• When Oda delegates work, the line travels with the task. Only helpers running on this computer can read the saved copy.
• If no readable path can be given, the line says the file cannot be reached, and Oda reports that instead of claiming it read the file.

What the model receives for an image

When the model accepts images, the picture travels with the request, together with a line that names the image, gives the preview size the request uses, and points to a read-only normalised copy on this computer.

• The normalised copy may be resized or re-encoded, so its dimensions, format and byte size can differ from the file you attached.
• Your attachment stays as you sent it; the copy is what the request uses.

When the model accepts text only

If the model of the chat accepts text only, the picture is left out of the request. Each image becomes a short note instead, the same note each time, reading [image omitted because this model accepts text only; ...] and carrying a short digest of the image.

• The note changes only what the model receives; the chat keeps the image, and nothing already in the chat is rewritten.
• The picture stays in the chat: a model that accepts images receives it. To change the model of a chat, see Chat with Oda.

When a request exceeds the image limits

A model may limit how many images one request can carry and how large they can be in total. When a request would go past those limits, Oda leaves out the oldest images first, until the request fits, and puts a note in each one's place, reading [image omitted to fit request image limits; ...].

• The note names the image and either gives the path of a read-only copy on this computer, or says that no local copy is available, so the image can be attached again if it is needed.
• The images stay in the chat; the notes replace them in what the model receives.
• Leaving images out is not an error: the request still goes with the notes in their place.
• When a request cannot fit even then, Oda reports how many more of the oldest images must be left out. How model calls fail and retry is covered on Model calls and failures.

Questions, answered

Does the model receive the file I attach, or a copy of it?

Neither. Oda never sends the file itself, or a copy of it, to the model. The model receives one line with the file's name, its size, a short digest and the path of a read-only copy saved on this computer; Oda reads that copy when the task needs the contents.

Does Oda read a file as soon as I attach it?

No. The file's line tells Oda where the saved copy is, and Oda opens it only when the task needs the contents.

What happens to an image when the model accepts text only?

The picture is left out of the request and replaced by a short note that says the image was omitted because the model accepts text only, with a short digest of the image. The chat keeps the image, and a model that accepts images receives it.

Why was an image left out of a request?

Every image in the chat counts, including images from earlier messages. When a request would carry more than the model allows, by count or by total size, Oda leaves out the oldest images first and puts a note in each one's place.

Are the images that were left out lost?

No. The chat keeps every image you attached. A left-out image is replaced by a note that names it and says whether a copy is available on this computer; when no copy is available, Oda asks you to attach the image again if it needs the picture.

What does the short digest in a file's line mean?

It is a short fingerprint of the file's contents. If the file changes, its digest changes too.

Can Oda change a file I attached?

The saved copy is read-only. Before changing anything, Oda copies the file to a writable location and works from there, so the saved copy is never edited in place.

Can other helpers read the file I attached?

Only helpers running on the same computer. The saved path travels with delegated work, and helpers on this computer can read it; helpers elsewhere cannot.

Why does an image sometimes differ from what I attached?

A request carries a read-only normalised copy that may be resized or re-encoded, so its dimensions, format and byte size can differ from the original file. The image in the chat stays as you sent it.

Why can Oda not reach a file I attached?

When no readable path to the saved copy can be given, the file's line says the file cannot be reached, and Oda reports that limitation instead of claiming it read the file.