DataMind Oda is built from plugins and ships with a set of its own. This page shows where you meet them: the Plugins page, where you switch feature bundles and open built-in settings, and Settings > Built-in plugins, the read-only list of what this installation loads.
Two surfaces cover plugins:
Both belong to the developer surface, so they stay hidden until the Plugins page feature is on:
Every optional feature bundle ships switched off. To switch one on or off:
Worth knowing:
Add an Auto review permission mode that uses the model to assess authorization before each tool call.Built-in plugins with settings keep their cards on the Plugins page too, in the Official group after the bundles. Open the group and select a plugin:
A card appears only while this deployment runs that plugin and Developer tools is on. A plugin with a settings card of its own is configured there, not in a generated form; Live plugin settings covers the forms some plugins expose while Oda runs.
Settings > Built-in plugins is an inventory: it shows which plugins this installation loads, and it is read-only. To open it:
Reading plugins….Composed per session by agent presets. Use Choose the agent preset to inspect to look at another preset's composition; the default preset shows first.Shared by the system and every session. · N plugins, and N failed when something failed).Each row names one plugin and shows its id, an enablement tag and the live phase in words. Expand a row for more: where it comes from, its runtime status, and a Disabled when condition where one applies. A coloured dot marks a phase that is still on its way, such as Waiting for dependencies or Loading.
The page never switches anything: it cannot enable, disable, add or remove a plugin. It is also a snapshot: it updates when you open it again or after a retry, not on its own while it stays open.
While you read the list, one of these states may show:
| Message | What it means | What to do |
|---|---|---|
Reading plugins… | The list is still reading the plugin state. | Wait; the rows appear when the read settles. |
No plugins are available. | This deployment exposes no plugin entries to the list. | Nothing to fix; there is nothing to list here. |
No matching plugins. | The search found nothing in either group. | Clear the search, or try another word. |
Plugins are temporarily unavailable. | The plugin state could not be read, so no rows are shown. | Choose Retry; if it keeps failing, ask your administrator. |
Some plugins could not sync on this page. | Part of the page did not finish loading; no plugin's state was changed by it. | Choose Retry this page; the retry reloads the page and switches nothing. |
This deployment exposes no plugin views. | The page has no views to show in this deployment. | Nothing to fix; there is no view to open here. |
To change a plugin's state, or to install or remove a bundle, use the Plugins page; Plugins and MCP connections covers installing.
The Plugins page manages plugins: there you switch feature bundles and plugin rows, install extra bundles, and remove what you added. Settings > Built-in plugins only inspects: it lists what this installation loads and cannot change anything. Plugins and MCP connections covers installing; Advanced features covers the Plugins page switch that reveals both surfaces.
No. The list is read-only: it reports each plugin's state and cannot switch, add or remove anything. Switches live on the Plugins page.
One of five states:
Enabled: the plugin is on.Disabled: it is off, either on its own or because a group that holds it is off.Conditional: it is available only while a condition on this installation holds, which the list cannot settle into a plain on or off.Enabled via presets: it is off globally, and one or more agent presets provide it per session; the expanded row lists the presets under Enabled in.Failed: it did not start.The Session plugins group shows what each agent preset composes for a session. Choose the agent preset to inspect switches the group to that preset's composition; the default preset shows first, and a preset that cannot load stays listed with its reason.
It marks a phase that is still on its way: while a plugin is Waiting for dependencies, Loading or Unloading, a dot shows it at a glance. The row also spells the phase out in words, and settled states such as Running or Not running show no dot.
On the Plugins page: open the Official group and select the plugin's card. Shell sets the command time limit and output cap (Shell settings), Subagent sets the delegation limits and the models Subagents may use (Subagent limits), and Agent loop sets the parallel tool-call cap (Agent loop settings).
It is a developer surface. In the desktop app and the VS Code extension, turn on Plugins page under Settings > Developer > Advanced features; see Advanced features. In the web app, the plugins page is one of the surfaces that appear only while Developer tools is on; see Developer settings.
There is no web search settings card; the plugin surfaces show none.
Reopen the page: the list takes a fresh snapshot when it opens and after a retry. It does not update itself while it stays open.
Plugins are temporarily unavailable. mean?The list could not read the plugin state, so it shows no rows. Choose Retry; if it keeps failing, ask your administrator.