Prompts, queue and steering

Work in DataMind Oda happens in a chat: you send a prompt, and Oda works on it. This page covers what a prompt must contain, what happens when you send one while Oda is already working, and the time zone that goes with every message.

What a prompt must contain

A prompt needs something to send: text that is not only spaces or line breaks, or a file or image attached to it.

A message that carries neither is refused, and nothing is sent. The refusal reads prompt content must include non-whitespace text or an attachment. Oda checks the content before the message goes anywhere, so a refused message leaves the chat as it was.

Sending while Oda is working

You can keep sending while Oda works. A message sent during a run takes one of two paths:

The chat shows where the message went: queued while it waits, steering when it joined the running work.

Stopping a run does not throw the queue away: the messages that were waiting are kept, and they run in the order you sent them.

Change a message that is waiting

A message that is still waiting can still be changed:

Once a message has started sending, it is no longer waiting, so it can no longer be edited or removed.

The time zone that rides your message

Each message carries the time zone your computer reports, read from the app or browser you are using. You never type it: it goes with the message on its own.

Messages to a subagent's chat

Oda can hand part of a task to a subagent, which works in a chat of its own. That chat takes new work only from the chat that started it:

Questions, answered

What happens to a message I send while Oda is working?

It takes one of two paths. A queued message waits and becomes Oda's next piece of work; a steering message goes to the work that is already running and is taken at Oda's next step. The chat shows which one it is: queued while it waits, steering when it joined the running work. Messages that wait run in the order you sent them, oldest first.

Can I change or remove a message that is waiting?

Yes, while it is still waiting. You can edit it (text only), remove it, or steer it into the running work while Oda is working. Once a message has started sending it has left the queue, so it can no longer be edited or removed.

Why was my edit of a waiting message refused?

Editing a waiting message keeps to text. A message that carries a file or an image cannot be edited, and the edit is refused with queue edits accept text content only. An edit that holds only spaces or line breaks is refused with queue edit content must include non-whitespace text.

Can I steer a waiting message into the running work?

Yes, while Oda is still working: steering moves the message to the running work, and Oda takes it at its next step. Once the running work has moved past the point where it can take new input, the steer is refused; let the message run in its turn instead.

What happens to the queue when I stop a run?

The queue is kept. Stopping a run does not drop the messages that were waiting: when the stop is through, they still run, in the order you sent them.

Can I send a message with no text?

No. A prompt needs text that is not only spaces or line breaks, or a file or image attached to it. A message with neither is refused with prompt content must include non-whitespace text or an attachment, and nothing is sent.

Which time zone goes with my message?

The one your computer reports, read from the app or browser you are using. It is UTC or a standard zone name such as Europe/Berlin, and a common alias is rewritten to its official name when the message is sent. When no zone can be read, the message goes without one. You never type it yourself.

Why was my time zone refused?

Oda accepts UTC or a valid zone name. A value that is neither is refused with clientTimeZone must be UTC or a valid IANA Area/Location name, and the message is not sent. If sending fails with browser time zone is unavailable, the app you are sending from reported no zone at all; try again, and if it returns, note the message for your DataMind OS administrator.

Can I send a message into a subagent's chat?

No. A subagent's chat takes new work only from the chat that started it, and a message you send there is rejected; nothing is added. Oda continues the subagent from the chat that started it.

Why can't I attach a file when Oda continues a subagent?

A message that continues a subagent's work does not accept files: it is refused with subagent continuation does not accept files. Give the file to Oda in your own chat instead.