For a task with several steps, DataMind Oda keeps a to-do list and writes its updates into your chat. Each update appears as a step row, and while the list is current its progress shows in the Steps chip above the message box and in the STEPS card in Activity. How Oda works with the list itself is on The agent task list; this page covers what you see in a chat.
3/ 7 completed, and names the task in progress when there is one.+2. That count is never cut off, even when the row is narrow.1 added · 1 updated · 1 removed, a single count like 3 added when only one kind moved, or No changes to the list when nothing moved.Added, Status changed, Reordered or Removed.+, one that left the list carries a −, and a task that changed state shows where it came from, reading Pending → In progress.2 unchanged; open the footer to see them.Initial list for the first recorded list, Changes since the previous list afterwards. An update with no tasks and no earlier list to compare reads The to-do list is empty.If the update's record cannot be read at all, the row opens as a plain block instead of the checklist, the same fallback as other steps; Step cards in chat covers it.
3/ 7, and the step being worked on now; pressing it opens Activity and flashes the STEPS card into view.Previous list unavailable and shows no change counts; when the earlier part of the chat loads, the comparison appears by itself.Every update appears in the chat as a row titled Update to-do list, and while the list is current its progress shows in the Steps chip above the message box and the STEPS card in Activity. The rows keep the history of updates; the chip and the card show only the latest list.
The chip shows the current list, not a permanent one. It keeps showing the finished list after a turn ends, then clears when the next turn begins; it returns with the next update Oda records. Every update stays in the chat as its own row, so nothing is lost.
That is Oda working in parallel, for example a background command or a helper agent. Oda marks every task it is actively working on; the row names the first and counts the rest, for example +2.
They recap the update against the list recorded before it: how many tasks are new (added), how many changed state or moved (updated), and how many are gone (removed). A single count stands alone, for example 3 added; an update that moved nothing reads No changes to the list.
Previous list unavailable?The list recorded before it is not loaded yet, so there is nothing to compare this update against. The comparison appears by itself when the earlier part of the chat loads. An update that already shows its comparison keeps it as first recorded, even when later updates are added.
Pending → In progress?The task changed state since the previous list. The reading is the previous state, an arrow, then the current state: the task was waiting and is now being worked on. A task that only moved position reads Reordered, a new one Added, and one that left the list Removed.
No. The list is Oda's own record of the task, and the card is read-only. Ask for the change in the chat, and Oda records a new update with it.
The row reports the failure, and the list keeps its last recorded state: a failed update is not recorded. Ask Oda to write the list again if it matters.
Every update keeps its own row in the chat. Expand the row to read the list as it stood at that update, with what had changed by then; the Steps chip above the message box and the STEPS card in Activity show only the latest list.