Skip to main content
Central gives an agent a container with the command-line tools it needs to operate an external control plane: a cloud account, a Kubernetes cluster, vCenter. Use a Host for commands on one machine and Central for a control plane, even when a change touches a single resource; Shell, Central and plugins walks through the choice.

​
Central Configurations

A Central configuration is a versioned manifest: one Kubernetes Pod or Deployment, or one Compose service on Swarm. The engine runs it on its own cluster or on another cluster, in a namespace or network your operator dedicates to Central. Credentials are mapped to environment variables from saved Secrets or Vault paths, never written into the manifest.

​
Agents and Central

An agent can hold a Host and several Centrals from its organization. When a task first runs a command, the engine picks the Host for machine-local work or the Central whose tools fit the request, and that choice holds for the whole task. In the same task, the agent can use its assigned MCP servers and HTTP APIs. Central configurations has the setup steps.

​
Central and Clusters

A Central configuration can run on a cluster’s nodes, to operate a control plane only that network zone can reach; registering a cluster has the setup steps.