ภาพรวมใหญ่: Gateway ช่องทาง ทักษะ และหน่วยความจำ

OpenClaw rests on four pillars: Gateway, channels, skills, and memory. Together they let one assistant do a lot. 🏛️

The Gateway is the heart of the system. It is the single source of truth for sessions, routing, and channel connections.

The Gateway runs as a persistent local daemon, a background process that stays alive so the assistant is always reachable.

Channels are the chat apps you connect, like WhatsApp or Telegram, so you can talk to OpenClaw from where you already message.

Every channel connects through the Gateway, which manages all the chat bridges so one hub coordinates them all.

Skills are extensible capabilities and workflows. They give the assistant new abilities beyond plain conversation.

You can grab ready-made skills from ClawHub, the community skill repository, or build your own when you need something new.

Memory keeps context around the clock. OpenClaw retains what matters 24/7 so threads continue naturally.

Memory is organized into isolated sessions per sender, agent, and workspace, so different contexts never bleed together.

You can run several agents, and the Gateway handles multi-agent routing, sending each message to the right one.

A channel message hits the Gateway, which routes it to an agent that uses skills and memory, then replies back to you.

Let us pin down the role of the Gateway.

Four pillars work as one: the Gateway routes channels, runs skills, and keeps isolated memory so a single assistant stays organized. 🎉