OpenClaw Architecture
OpenClaw puts channels, sessions, and devices behind one Gateway daemon. The agent does not speak Telegram or WhatsApp; it speaks the Gateway’s typed WebSocket. Channel plugins are ingress, not a second runtime.
One Gateway maps to one trust boundary. Extra channels, agents, and nodes stack in the same process. Split the Gateway when operators do not share trust, not when a second chat app appears.