Skip to main content
OpenClaw is the only workload type Ageneral ships on nodes: a gateway, agent containers, connectors for channels and tools, platform skills synced to disk, and merged gateway configuration Ageneral pushes to the machine. Details on skills and connectors live in Skills and Connectors.

​
How it fits

  1. Configuration — Ageneral sends a merged OpenClaw gateway config, agent profiles, connector wiring, and pinned container images.
  2. Updates — When something changes, the platform notifies the node to fetch the latest configuration.
  3. Apply — The node merges the new settings, syncs skills onto disk where OpenClaw expects them; see Skills. It applies connector settings; see Connectors. It updates containers and restarts the gateway or agents when needed.
  4. Channels — Telegram, Discord, browser automation, and similar traffic run inside the OpenClaw gateway on the node.
Some actions, for example pairing approve, use a direct Ageneral connection to the node instead of the same background path used for routine config updates.

​
Models and secrets

OpenClaw’s model providers follow the same platform rules as the rest of Ageneral: use Ageneral-issued keys and node identity as described in Private nodes and Public nodes, including optional third-party providers such as OpenRouter when your project is configured for them.