DataMind Oda can start Subagents: helper chats that each run part of a task while the main chat keeps working. Two limits decide how deep and how wide that delegation may go, and this page shows where to set them and what saving does.
The same two values appear on two surfaces, and both write the same settings:
| Limit | What it decides | Accepted values | Default |
|---|---|---|---|
| Maximum recursion depth | How many levels of Subagents an Agent can create. | A whole number of 0 or more | 3 |
| Subagent parallelism limit | How many Subagents are live at the same time under the same main Agent, across all recursion levels. | A whole number of 1 or more | 8 |
Worth knowing:
Worth knowing:
| Message | What it means | What to do |
|---|---|---|
Enter a whole number of 0 or more. | The Maximum recursion depth value is not a whole number of 0 or more. | Correct the value; Save waits until the field is valid. |
Enter a whole number of 1 or more. | The Subagent parallelism limit value is not a whole number of 1 or more. | Correct the value; Save waits until the field is valid. |
The deployment did not accept these values; they were left for you to correct. | Oda could not save the change, so nothing was written and your draft is kept for correction. | Correct the values and save again; if it repeats, ask your administrator. |
Settings changed elsewhere. | The settings changed somewhere else while you were editing, so Oda will not overwrite the newer values. | Discard your draft, reopen the surface, and make the change again. |
This deployment stores settings read-only. | This installation keeps its settings read-only, so the fields stay disabled. | The values cannot be changed here; ask your administrator. |
This plugin is not loaded, so it cannot be configured right now. | The deployment does not offer these settings right now, so the card cannot be configured. | Try again later; if it stays this way, ask your administrator. |
On two surfaces, both writing the same values: the Subagent limits card under Settings > Agent presets, below the preset roster, and the Limits section of the Subagent page on the Plugins page, in the Official group. The Plugins surface is a developer one; the card under Agent presets works without developer switches.
It disables Subagents for the tools that take their depth from this setting. A tool with a maximum of its own keeps its own number, because that setting takes precedence.
Every Subagent that is live at the same time under the same main Agent, across all recursion levels. The main Agent itself is not counted, and new Subagent starts are rejected while the limit is reached.
3 levels for Maximum recursion depth and 8 live Subagents for Subagent parallelism limit. Reset to default on an overridden field returns it to that value.
Yes. If a tool defines its own maximum recursion depth, that setting takes precedence over Maximum recursion depth.
Save waits until you change something. It stays unavailable while a value is invalid, while a save is running, and while a draft is out of date because the settings changed elsewhere.
It clears your saved value for that field, so the value Oda ships with applies again. The reset is staged like any other edit and is written by the next Save.
They are dropped when you leave the surface; nothing is written before you save.
If the surface reads This deployment stores settings read-only., this installation keeps its settings read-only and the fields stay disabled.
It is a developer surface: it appears while Developer tools are on (Developer settings). The limits are still available: the Subagent limits card under Settings > Agent presets works without it.
Not on these surfaces: the Subagent limits carry no teammate count. Teammates have their own card under Agent Teams on the Agent presets page, and Agent teams covers the teams themselves.