Agents & Gateway
Manage multi-channel, multi-agent bindings and routing via Gateway; node pairing, pending/approve flows, and other processes run natively on macOS.
kvmjet@mac-mini ~/openclaw
$ openclaw gateway status --verbose
✓ gateway: listening wss://0.0.0.0:18789
✓ nodes: 2 paired · channels: telegram, discord
# Agent orchestration on real macOS — Gateway, multi-channel routing, and automated tasks
Chain triggers, routing, execution, and callbacks into an auditable pipeline; computing runs on data center Macs without entangling your local environment. See operation guides in theBlog · Featured.
/* OpenClaw */
Chain triggers, routing, execution, and callbacks into an auditable pipeline; computing runs on data center Macs without entangling your local environment.
Manage multi-channel, multi-agent bindings and routing via Gateway; node pairing, pending/approve flows, and other processes run natively on macOS.
Xcode builds, signing, Simulator, and certain agent toolchains require macOS. Cloud hosts provide predictable, dedicated computing with a fixed egress.
Local machine handles orchestration and triggering; data center Mac handles builds, daemon persistence, and channel callbacks. Certificates and local state remain on the dedicated node.
/*Why Run on Kvmjet*/
Bare-metal isolation, fixed egress, and multi-region deployment let Gateway and execution nodes be placed per scenario.
Entire Mac mini is dedicated — certificates, daemons, and local state don't interfere with other tenants.
Webhook, Telegram/Discord callbacks, and cross-region pulls travel on dedicated lines for more predictable latency.
Gateway and execution nodes can be placed by proximity — e.g., US East gateway + Asia-Pacific VNC acceptance.
Daily for trials; monthly/quarterly for persistent Gateway or CI; disk and Thunderbolt expandable on demand.
/*Common Topics*/
Topic overviews below; operation guides in theBlog · Featured.
Official script / npm path, onboard and gateway health check; SSH/VNC connectivity as acceptance baseline.
Differences between SSH tunnel and wss direct connection, daemon/launchd persistence, and common Web Chat troubleshooting.
Bindings, node pairing, Telegram/Discord and other channel destinations, and multi-agent task division.
US East/West/Asia-Pacific node selection; 16GB vs 24GB, disk add-ons, and multi-machine cluster topology.
Chain xcodebuild, pre-release checks, and callback notifications into fixed pipelines — less manual button-clicking.
Reference solutions for common issues: exit 127, pairing pending, cross-region fetch, and cache drift.
/*Deployment*/
Steps vary by version and network environment; the following is the common sequence on Kvmjet.
# step 1 — Rent a Mac node
$ kvmjet order --spec m4 --region us-east
On thepricing page, select M4 memory, disk, data center, and billing cycle; try daily first to test latency and build speed.
# step 2 — SSH / VNC access
$ ssh user@<instance-ip> && open vnc://<instance-ip>
Retrieve credentials from the console after provisioning; use VNC for graphical acceptance, SSH for installing dependencies and viewing logs.
# step 3 — Install and configure OpenClaw
$ openclaw onboard && openclaw gateway start
Follow the official guide to complete onboard, Gateway, and channel binding; use launchd for persistence.
# step 4 — Connect to your business pipeline
$ openclaw bind --ci github --notify telegram
Integrate CI, notification channels, or agent workflows; plan gateway and execution node partitions for multi-machine scenarios.
/*Featured Articles*/
See the Featured Blog for the full article list and updates.
# ready to deploy?
From daily trials to a persistent Gateway — configure and choose your data center in one step on the pricing page.