Subagents are the helper chats DataMind Oda starts while it works. By default they use configured defaults or inherit the parent agent's model.
The Model selection section of the Subagent card changes that: with its switch on, agents can choose a provider, model and reasoning effort for each Subagent, from a list of models you authorise. Find the card on the Plugins page: open Subagent in the Official group, and look for Model selection beside Limits. The card is a developer surface, so it appears while Developer tools are on; Built-in plugins covers the page and its cards, and Subagent limits covers the Limits section.
The switch is off by default. Turning it on or off only changes a draft, and the text under the switch follows its state:
When enabled, agents can choose a provider, model, and reasoning effort for each Subagent from the authorized models below. Applies only to new sessions.Subagents use configured defaults or inherit the parent agent's model. Saved model choices are retained.An enabled switch must name at least one model: with nothing selected, the section reads Select at least one model before saving. and the card cannot save the change. The setting applies to new sessions only; a chat that already started is not affected.
Models agents may choose lists the model routes this deployment offers, grouped by vendor. Each row names a provider and a model that a Subagent may use.
Allow all {vendor} models, that selects every model of that vendor at once, and clears them together again when switched off.No model matches your search.Loading models…. If it cannot be read, the card offers Retry; the messages below cover what each state means.Models in your saved list that the catalogue no longer offers stay listed: they are marked Currently unavailable and you can still remove them. A saved list is kept even while the switch is off.
The card has one Save for both sections: Model selection and Limits. Each section is written only when you changed it, and the sections save on their own, so a refusal in one does not cancel the other. While a save runs, the button reads Saving… and the card's controls lock until it settles.
An edit stays a draft until you save it, and leaving the card drops what you did not save.
| Message | What it means | What to do |
|---|---|---|
Select at least one model before saving. | The switch is on but the list holds no models. | Select at least one model, then save again. |
Models could not be loaded. | The model catalogue could not be read, so the list has nothing to show. | Choose Retry; if it keeps failing, ask your administrator. |
Some model providers could not be loaded; saved choices remain removable. | Part of the catalogue could not be read. | The models that loaded stay usable, and saved choices stay removable; choose Retry to load the rest. |
No model provider currently advertises a model. | The catalogue currently offers no models. | Nothing to select yet; the list refreshes when the deployment's models change. |
Currently unavailable | A saved model that the catalogue does not offer right now. | Remove it if you no longer want it; until then it stays listed. |
On the Plugins page: open Subagent in the Official group and find Model selection, beside Limits. The card is a developer surface, so it appears while Developer tools are on. The limits are available without developer switches too: Subagent limits covers the Subagent limits card under Settings > Agent presets.
Yes. Each vendor group carries a switch, Allow all {vendor} models, that selects every model of that vendor together; switching it off clears them together again.
Select at least one model before saving.?The switch is on, but Models agents may choose holds no selection. An enabled switch must name at least one model, so the card waits: select a model, or turn the switch off, then save.
Currently unavailable?It is a model in your saved list that the catalogue does not offer right now. The card keeps it listed so your choice is not lost, and you can remove it at any time.
They are kept. The switch's own text says Subagents use configured defaults or inherit the parent agent's model. Turn it on again and the same models are there.
Models could not be loaded. What can I do?The model catalogue could not be read. Choose Retry to load it again. When only part of the catalogue fails, the card instead says Some model providers could not be loaded; saved choices remain removable., and the models that did load stay selectable. If it keeps failing, ask your administrator.
No model provider currently advertises a model.?The deployment's catalogue currently offers no models, so there is nothing to select yet. The list refreshes when the deployment's models change; if you expected models here, ask your administrator.
Yes. The Save footer belongs to the whole card: Model selection and Limits are saved together, and each section is written on its own, so a refusal in one does not cancel the other.