mirror of
https://github.com/hanzoai/bot.git
synced 2026-10-30 17:24:26 +00:00
zeekay
4bdc9ee3e4
Comprehensive rename of all openclaw references to hanzo-bot equivalents: - Package: openclaw → @hanzo/bot - Binary: openclaw → hanzo-bot - Types: OpenClaw* → Bot* - Env vars: OPENCLAW_* → BOT_* - Android: ai.openclaw.android → ai.hanzo.bot.android - iOS/macOS: ai.openclaw.* → ai.hanzo.* - Swift modules: OpenClaw* → Bot* - Plugins: openclaw.plugin.json → bot.plugin.json - Paths: .openclaw/ → .hanzo/bot/ - URLs: github.com/openclaw → github.com/hanzoai
1.4 KiB
1.4 KiB
summary, read_when, title
| summary | read_when | title | |
|---|---|---|---|
| How the Gateway, nodes, and canvas host connect. |
|
Network model |
Most operations flow through the Gateway (bot gateway), a single long-running
process that owns channel connections and the WebSocket control plane.
Core rules
- One Gateway per host is recommended. It is the only process allowed to own the WhatsApp Web session. For rescue bots or strict isolation, run multiple gateways with isolated profiles and ports. See Multiple gateways.
- Loopback first: the Gateway WS defaults to
ws://127.0.0.1:18789. The wizard generates a gateway token by default, even for loopback. For tailnet access, runbot gateway --bind tailnet --token ...because tokens are required for non-loopback binds. - Nodes connect to the Gateway WS over LAN, tailnet, or SSH as needed. The legacy TCP bridge is deprecated.
- Canvas host is served by the Gateway HTTP server on the same port as the Gateway (default
18789):/__bot__/canvas//__bot__/a2ui/Whengateway.authis configured and the Gateway binds beyond loopback, these routes are protected by Gateway auth (loopback requests are exempt). See Gateway configuration (canvasHost,gateway).
- Remote use is typically SSH tunnel or tailnet VPN. See Remote access and Discovery.