From 5fa60e653563aa993682eb475bc69ca2a4439b95 Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Sat, 4 Apr 2026 15:07:32 +0100 Subject: [PATCH] docs: refresh channel overview mirrors --- docs/index.md | 6 +++--- docs/web/control-ui.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/index.md b/docs/index.md index 8135b79e744..c7172206774 100644 --- a/docs/index.md +++ b/docs/index.md @@ -26,7 +26,7 @@ title: "OpenClaw"

Any OS gateway for AI agents across Discord, Google Chat, iMessage, Matrix, Microsoft Teams, Signal, Slack, Telegram, WhatsApp, Zalo, and more.
- Send a message, get an agent response from your pocket. Run one Gateway across built-in channels, bundled plugins, WebChat, and mobile nodes. + Send a message, get an agent response from your pocket. Run one Gateway across built-in channels, bundled channel plugins, WebChat, and mobile nodes.

@@ -43,14 +43,14 @@ title: "OpenClaw" ## What is OpenClaw? -OpenClaw is a **self-hosted gateway** that connects your favorite chat apps and channel plugins — Discord, Google Chat, iMessage, Matrix, Microsoft Teams, Signal, Slack, Telegram, WhatsApp, Zalo, and more — to AI coding agents like Pi. You run a single Gateway process on your own machine (or a server), and it becomes the bridge between your messaging apps and an always-available AI assistant. +OpenClaw is a **self-hosted gateway** that connects your favorite chat apps and channel surfaces — built-in channels plus bundled or external channel plugins such as Discord, Google Chat, iMessage, Matrix, Microsoft Teams, Signal, Slack, Telegram, WhatsApp, Zalo, and more — to AI coding agents like Pi. You run a single Gateway process on your own machine (or a server), and it becomes the bridge between your messaging apps and an always-available AI assistant. **Who is it for?** Developers and power users who want a personal AI assistant they can message from anywhere — without giving up control of their data or relying on a hosted service. **What makes it different?** - **Self-hosted**: runs on your hardware, your rules -- **Multi-channel**: one Gateway serves built-in and plugin channels simultaneously +- **Multi-channel**: one Gateway serves built-in channels plus bundled or external channel plugins simultaneously - **Agent-native**: built for coding agents with tool use, sessions, memory, and multi-agent routing - **Open source**: MIT licensed, community-driven diff --git a/docs/web/control-ui.md b/docs/web/control-ui.md index 5b5943fd530..d761cb785e9 100644 --- a/docs/web/control-ui.md +++ b/docs/web/control-ui.md @@ -79,7 +79,7 @@ The Control UI can localize itself on first load based on your browser locale, a - Chat with the model via Gateway WS (`chat.history`, `chat.send`, `chat.abort`, `chat.inject`) - Stream tool calls + live tool output cards in Chat (agent events) -- Channels: WhatsApp/Telegram/Discord/Slack + plugin channels (Mattermost, etc.) status + QR login + per-channel config (`channels.status`, `web.login.*`, `config.patch`) +- Channels: built-in plus bundled/external plugin channels status, QR login, and per-channel config (`channels.status`, `web.login.*`, `config.patch`) - Instances: presence list + refresh (`system-presence`) - Sessions: list + per-session thinking/fast/verbose/reasoning overrides (`sessions.list`, `sessions.patch`) - Cron jobs: list/add/edit/run/enable/disable + run history (`cron.*`)