Subagents

DataMind Oda can split a large task and hand parts of it to helper agents called subagents. A subagent works as a chat of its own, and you can follow it from the chat that started it.

What a subagent is

• A subagent is a helper agent that Oda starts for one part of a task. It runs its part in its own chat, with the same tools, and it stays visible to the chat that started it whether it is running or stored.
• The chat that starts a subagent stays the owner of the task: it reads the subagent's result and decides how to carry on.
• One-shot and continuable. A one-shot subagent does its piece in one run and ends: its chat is a record for reading. A continuable subagent keeps its identity after the run and can take follow-up messages; see Follow and control Subagents. A record that does not say which kind it is shows as unknown mode.
• What runs a subagent, and where a helper starts from, is in Subagent backends. A subagent can also run on a model chosen for it; see Choose models for Subagents.

Move between the chat and its subagents

A chat with subagents shows a switcher in its header; a chat with no subagent relationships shows nothing there.

1. Open the switcher beside the chat's title. It reads Switch subagent: <title> and carries a count such as 2 subagents, or 2 subagents running while they work.
2. In the Subagent sessions list that opens, pick the subagent you want. A row opens that subagent's chat; use Open <label> in sidebar to open it in the side panel instead (or in the main area when there is no side panel).

• A row shows the subagent's title, its kind (one-shot, continuable or unknown mode) and whether it is running, plus its token total and working time. Branches open on demand, loading that part of the list.
• The list opens after 150 ms of hover and closes 120 ms after the pointer leaves. Arrow keys move through the list, left and right open or close a branch, and Escape closes the list and returns focus to the switcher.
• While the list loads it reads Loading subagents…; if it cannot load, it reads Unable to load subagents with Retry.

Read a subagent's chat

• Subagent chats are not listed in the main sidebar. Reach one from the switcher list, from the Activity tab of the side panel, or with Open <label> in sidebar; Watch and steer subagents covers the Activity side.
• A one-shot subagent's chat is kept as a record and titled One-shot subagent record: One-shot tasks do not accept follow-ups; review the full execution record here.
• When the chat that started a subagent is closed, its chat reads This subagent is read-only for now and The parent session is offline; reopen it to continue sending messages. A subagent that is running right now keeps its message box.
• When the record does not say whether a subagent can take follow-ups, its chat reads Read the child session to determine whether it can be continued. Reopen the chat that started it to continue.

Point at a subagent with @

• Typing @ in the message box brings up references, including your subagents' labels. Picking one inserts the label as plain text (@<label> ).
• The mention is display text only: it does not message or continue the subagent. Use it to name the subagent you mean.

How many subagents may run

• The Subagent parallelism limit decides how many subagents may be live at once under the same chat, across all levels. It defaults to 8 and accepts 1 or more; the chat itself does not count. While the limit is reached, a new subagent start is refused.
• Maximum recursion depth decides how many levels of subagents may be created: 0 disables subagents for the tools that take their depth from this setting, and 1 means only the chat itself can start them. A delegation tool that sets its own depth takes precedence, and a start past the budget is refused.
• A subagent that is brought back later keeps the depth it was created with, so it cannot delegate as if it were a fresh top-level chat.
• Both limits live on the Subagent limits card under Settings > Agent presets, and on the Subagent page under Plugins. A value you save is marked Overridden; Reset to default returns the field to the value Oda ships with. Subagent limits covers the controls.

What a subagent may do on its own

A subagent never asks you for approval. It works inside the access of the chat that started it, taken when it starts; it cannot widen that access, and a subagent brought back later keeps the access it started with. Subagent permissions and sandboxing covers the rules, and Workspaces, files and permissions covers the access modes.

Questions, answered

What is a subagent?

A helper agent that DataMind Oda starts to run one part of a task. It works as a chat of its own, with its own record, and it stays visible to the chat that started it whether it is running or stored. Delegating work to subagents covers the delegation side.

What kinds of subagent does Oda start?

Two kinds. A one-shot subagent does its piece in one run and ends: its chat is a record for reading. A continuable subagent keeps its identity after the run and can take follow-up messages (Follow and control Subagents). A record that does not say which kind it is shows as unknown mode.

What do the count and the dot on the switcher mean?

The count is how many subagents the chat has, such as 2 subagents, or 2 subagents running while they work. The dot reads ongoing while subagents run, done once the work has finished, and idle otherwise.

Why do subagent chats not appear in the sidebar?

Subagent chats are not listed in the main sidebar. Reach one from the switcher list, from the Activity tab of the side panel, or with Open <label> in sidebar. The sidebar lists your own chats; Chat with Oda covers managing them.

What does the Subagent sessions list show?

The chat's subagents as a tree: a row shows the subagent's title, its kind (one-shot, continuable or unknown mode) and whether it is running, plus its token total and working time. A branch opens on demand, loading that part of the list. A row opens that subagent's chat; Open <label> in sidebar opens it in the side panel.

Why does the subagent list say it cannot load?

The list could not be fetched, so it reads Unable to load subagents with Retry. Press it to load the list again. While the list is loading it reads Loading subagents….

What does One-shot subagent record mean?

It is the title of a one-shot subagent's chat. That subagent ran once, and its chat is kept for reading: One-shot tasks do not accept follow-ups; review the full execution record here.

Can I message a subagent while its parent chat is closed?

Sending needs the chat that started the subagent open: its chat reads The parent session is offline; reopen it to continue sending messages. Reading still works, and a subagent that is running right now keeps its message box.

What happens when I pick a subagent after typing @?

It inserts the subagent's label as plain text (@<label> ). The mention does not message or continue the subagent; it names it in your message.

How many subagents can run at once?

The Subagent parallelism limit decides. It defaults to 8 and accepts 1 or more; the chat itself does not count. While the limit is reached, a new subagent start is refused. Change it on Subagent limits.