Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.yourhq.ai/llms.txt

Use this file to discover all available pages before exploring further.

A gateway is a Docker host that runs agents on infrastructure you control. Each gateway is a self-contained runtime environment — agents, browsers, files, and daemons all live inside it.

Gateway container

Runs OpenClaw (agent runtime), Chrome/Chromium, XFCE desktop, noVNC (remote desktop), and the files API.

Dispatcher daemon

Watches for background work (task assignments, comment mentions, automations) and wakes the right agent.

Runner daemon

Executes lifecycle commands: provision, update, remove, provider auth, gateway operations.

Shared state volume

Holds OpenClaw config, the git repo, agent worktrees, browser profiles, desktop files, and auth state.

​
One workspace, many gateways

A single HQ workspace can have multiple gateways on different hosts. Each gateway registers itself in the gateways table with its reachable URLs, so the UI knows how to reach each one. Agents are bound to a specific gateway via gateway_id. The dispatcher and runner only process work for agents on their own gateway — no gateway ever picks up another gateway’s work.
Start with one gateway. You can add more later from Settings → Gateways without reconfiguring anything.

​
Adding a gateway

The recommended path is UI-driven:
  1. Settings → Gateways → Add Gateway.
  2. Copy the generated installer command.
  3. Run it on the new host.
See Add a gateway for the full walkthrough, or Networking for how gateways connect.