What Oda shows and what its logs keep

Before technical text reaches a person, DataMind Oda rewrites it into the product's own wording. Messages you read and details you copy are therefore written with Oda's own names, while Oda's own log files on your computer keep the original wording. This page explains what is reworded, where that wording applies, and what stays as it is.

What is reworded

The rewrite covers the software's own names, paths and build locations, in a fixed order:

• Paths. A path that points inside the installed software is shortened to the part inside it, written with forward slashes; the machine's own folders are dropped.
• Build locations. A line that points into the place where Oda was built keeps only the file name and position, such as at resolveBareSpecifier (sea-main.js:3001:14).
• Names. An installed part is shown as oda/<name>, a one-word name as oda-<name>, and an environment name carries the ODA_ prefix.
• Labels. A leading label that carries the command's internal name is removed; the rest of the line stays.
• The software's name itself. Any other word for the software, or for where it came from, is shown as Oda and keeps its capitalisation.

A message about a part that cannot be loaded therefore reads like Cannot find package 'oda/browser-use', and a failure line names its part in the same wording, as in oda/api-remotes: failed.

The result is stable: text already in this wording is not changed a second time.

Failure output when Oda starts reads the same way; Startup and diagnostics covers how to read a failed start.

Where the reworded text applies

• Where a person reads or copies. The rewrite applies to the text Oda shows you and to text you copy from the app: messages, failure output and copied details. It is a display change only; it never affects what Oda does.
• Not where machines read. Text that goes to a model never passes through the rewrite, and the log files on the computer keep the original wording.

What stays as it is

• Model names. The name of a model is deliberately left unchanged.
• Web addresses. An address keeps its form; only a product name inside it is reworded. The addresses that identify model services are deliberately left unchanged as well.

Questions, answered

Why does a message name a part of Oda I have never heard of?

The message came from inside the app, and its internal names are shown in Oda's own wording before you read them. A part of the software can read as oda/<name> anywhere in a message. Keep the text as it is when you report it.

Which text does this rewording apply to?

Technical text Oda shows to a person or puts on the clipboard: messages, failure output and copied details. It is a display change only, so it never affects what Oda does.

Are the log files on my computer reworded too?

No. The rewrite applies only to what Oda shows or copies; the log files on the computer keep the original wording. If you compare the two, differences in names and paths are expected.

Does the rewording reach what Oda sends to a model?

No. It applies only where a person reads or copies text, and content a model sees never passes through it.

Are model names reworded too?

No. The name of a model, and the addresses that identify model services, are deliberately left as they are.

Why did a path in a message lose its first folders?

The path pointed inside Oda's installed software. Only the part inside the software is kept, and it is written with forward slashes; the folders that exist only on this machine are dropped.

Why does a failure line show only a file name and numbers?

That line points into the place where Oda was built. The build location is not useful outside Oda, so it is dropped and the file name with its line and column stays, as in at resolveBareSpecifier (sea-main.js:3001:14).

I am reporting a problem. Should I send the text exactly as Oda shows it?

Yes. What Oda shows or copies is already written in product wording, so send it exactly as it appears. The original wording stays in Oda's own log files on the computer. For problems of other kinds, see Updates and troubleshooting.