Use this file to discover all available pages before exploring further.
Network
Network hub
This hub links the core docs for how OpenClaw connects, pairs, and secures
devices across localhost, LAN, and tailnet.
Core model
Most operations flow through the Gateway (
), a single long-running process that owns channel connections and the WebSocket control plane.
- Loopback first: the Gateway WS defaults to .
Non-loopback binds require a valid gateway auth path: shared-secret
token/password auth, or a correctly configured non-loopback
deployment.
- One Gateway per host is recommended. For isolation, run multiple gateways with isolated profiles and ports (Multiple Gateways).
- Canvas host is served on the same port as the Gateway (, ), protected by Gateway auth when bound beyond loopback.
- Remote access is typically SSH tunnel or Tailscale VPN (Remote Access).
Key references:
Pairing + identity
Local trust:
- Direct local loopback connects can be auto-approved for pairing to keep
same-host UX smooth.
- OpenClaw also has a narrow backend/container-local self-connect path for
trusted shared-secret helper flows.
- Tailnet and LAN clients, including same-host tailnet binds, still require
explicit pairing approval.
Discovery + transports
Nodes + transports
Security
Related