Skip to main content
Choose the execution environment first, then the tool for each operation. A Host gives the agent commands on one machine. Central gives it a container with the CLIs needed to operate an external control plane. Assigned MCP and HTTP API plugins can be used alongside either environment.

​
Tool selection decision tree

For single-machine operations, this shell branch assumes a simple CLI and no additional service authentication. The Host’s configured connection credentials still apply. Configure Central for control-plane commands, even when the command affects only one remote resource. Host agents retain access to authorized cloud or database CLIs already installed and configured on their Host when no suitable plugin is assigned. A missing Central alone does not block these existing commands, including when Central is disabled. Central remains the configuration choice for a new dedicated control-plane command environment.

​
Choose the tool

Use run_shell for a simple pre-installed CLI with usable help and no service authentication. Prefer a plugin for a control-plane CLI when any of these applies:
  • It requires authentication to an external service.
  • Its help does not explain the commands and arguments the agent needs.
  • It is a custom or internal tool whose behavior the agent cannot infer reliably.
Choose a suitable MCP plugin first. Suitable means that its documented tools and input schemas cover the requested operation and that you can scope its access to the agent. An MCP that lacks the operation does not take precedence over an HTTP API plugin that supports it. When no suitable MCP is available, configure an HTTP API plugin with API documentation and structured request arguments. Use Plugins to configure and assign the integration. A plugin’s presence alone does not make it the right tool for every step, and access to live data alone does not take precedence over the simple CLI branch.

​
Combine plugins and shell commands

A task can call an assigned plugin and run shell commands in its configured Host or Central. Use shell commands for helpers, additional tools or capabilities that the plugin lacks. For example, an MCP can retrieve an inventory while a shell command formats a local file. Fallback uses only authorized access and commands available in the configured environment. It cannot bypass an authorization refusal or a disabled/unassigned plugin. A missing response from a modifying call does not establish that it failed; do not repeat the operation through another tool without establishing its outcome.

​
Configuration and scope

These are agent instructions based on the task context and tool descriptions. They do not automatically create a Central, install a plugin or change an agent’s execution target. If the required environment or access is missing, the agent reports the configuration needed. Configure and test it before creating a new task. Give each agent only the plugins and credentials its operations need. Keep unrelated tools out of the context. The stored credential catalog lists secrets managed by 2501. It does not inventory authentication already configured on a Host, such as a CLI profile, environment or instance role. An empty catalog alone is not evidence that an installed Host CLI cannot authenticate; the agent uses permitted tool results to establish its actual state.