What Oda sends to model providers

When DataMind Oda asks a model for an answer, the request carries more than the chat's messages. Oda adds a few facts about itself, about the chat, and about the packages installed with it. This page lists what rides a request, what the model reads of it, and how to turn the package inventory off.

What rides a model request

• Your conversation. The messages of the chat; for files and images, what the model receives is described in Attachments in model requests.
• App attribution. Oda names itself and its version in every request, so the service can tell which app, and which version, called it. That attribution carries no secrets, no file paths, no chat identifiers, no prompt text and no personal identifiers. Model calls and failures covers this identification.
• The chat's identity. Each request carries an identity for the chat it belongs to.
• A package inventory. On the routes that support it, the list of the plugin packages active in the request; it is on by default.
• A part of the chat's log. On those routes, the newest part of the chat's log travels with the request; Chat logging covers what it carries and how delivery works.
• The installation id. Oda also sends this installation's anonymous id with its AI requests; Usage reporting and the installation id explains what it is.

The package inventory and the log part count as delivered only when the request succeeds.

What the model sees

Only the chat's messages reach the model, together with the file and image material that Attachments in model requests describes. The other items a request carries sit outside the model's input, so none of them is visible to the model or changes the answer.

What your company records about Oda's requests is separate from what a model sees; Manage DataMind Oda for your company covers the company's log.

The package inventory

• What it carries. The plugin packages active in the request, each with its name and version. Oda works the list out for each request, so it matches the request it rides.
• On by default. The inventory is on by default, and it can be turned off: with the inventory off, Oda omits the package metadata from its requests.
• Its page. In the app, the inventory's page is titled Plugin Package Inventory; it reports the plugin packages active in each model request.

Questions, answered

Can the model read the package inventory or the log part?

No. Only the chat's messages reach the model. The attribution, the chat's identity, the package inventory and the log part travel with the request but stay outside the model's input, so none of them is visible to the model or changes the answer.

Is the package inventory sent by default?

Yes. The inventory is on by default, and Oda works it out for each request from the packages active at that moment.

How do I turn the package inventory off?

The inventory can be turned off; its page in the app is titled Plugin Package Inventory. With the inventory off, Oda omits the package metadata from its requests.

What does the package inventory contain?

The plugin packages active in the request, each named with its version. A package that is not active is not listed.

Is the inventory sent even if I never installed any packages myself?

Yes. Oda itself is built from plugin packages, so the inventory reports the packages active in the installation even when you have added no packages yourself.

Why is a package missing from the inventory?

The inventory covers the packages Oda loads as part of the installation. A package that is disabled or failed is left out, and a package replaced in place while Oda runs is picked up after a restart.

Does a request say which chat it belongs to?

Yes. Each request carries an identity for the chat it belongs to. It is not part of what the model reads.

Why did a request fail over a package's name and version?

Oda works out the inventory before a request goes out. A package it cannot identify, for example one whose details declare no name or version, stops that preparation: the request does not run, and Oda reports the package instead of sending an incomplete inventory. The package has to be corrected or removed; if you did not install packages on this computer, report the message to your DataMind OS administrator.