diff --git a/docs/.i18n/glossary.zh-CN.json b/docs/.i18n/glossary.zh-CN.json index 1eb26ed11c8..5bd0c64b907 100644 --- a/docs/.i18n/glossary.zh-CN.json +++ b/docs/.i18n/glossary.zh-CN.json @@ -59,6 +59,10 @@ "source": "Feishu", "target": "Feishu" }, + { + "source": "Mattermost", + "target": "Mattermost" + }, { "source": "BytePlus (International)", "target": "BytePlus（国际版）" @@ -175,6 +179,10 @@ "source": "Polls", "target": "投票" }, + { + "source": "QQ Bot", + "target": "QQ Bot" + }, { "source": "Release Policy", "target": "发布策略" diff --git a/docs/start/docs-directory.md b/docs/start/docs-directory.md index 1dcb94ca48b..351603cc021 100644 --- a/docs/start/docs-directory.md +++ b/docs/start/docs-directory.md @@ -40,8 +40,9 @@ For a complete map of the docs, see [Docs hubs](/start/hubs). - [Control UI (browser)](/web/control-ui) - [Telegram](/channels/telegram) - [Discord](/channels/discord) -- [Mattermost (plugin)](/channels/mattermost) +- [Mattermost](/channels/mattermost) - [BlueBubbles (iMessage)](/channels/bluebubbles) +- [QQ Bot](/channels/qqbot) - [iMessage (legacy)](/channels/imessage) - [Groups](/channels/groups) - [WhatsApp group messages](/channels/group-messages) diff --git a/docs/start/hubs.md b/docs/start/hubs.md index 9ff1784f539..eaee7ff6c62 100644 --- a/docs/start/hubs.md +++ b/docs/start/hubs.md @@ -73,9 +73,10 @@ Use these hubs to discover every page, including deep dives and reference docs t - [Telegram](/channels/telegram) - [Slack](/channels/slack) - [Discord](/channels/discord) -- [Mattermost](/channels/mattermost) (plugin) +- [Mattermost](/channels/mattermost) - [Signal](/channels/signal) - [BlueBubbles (iMessage)](/channels/bluebubbles) +- [QQ Bot](/channels/qqbot) - [iMessage (legacy)](/channels/imessage) - [Location parsing](/channels/location) - [WebChat](/web/webchat) diff --git a/docs/start/onboarding-overview.md b/docs/start/onboarding-overview.md index dc5c65ace74..7d7e4c7fd60 100644 --- a/docs/start/onboarding-overview.md +++ b/docs/start/onboarding-overview.md @@ -10,7 +10,7 @@ sidebarTitle: "Onboarding Overview" # Onboarding Overview OpenClaw has two onboarding paths. Both configure auth, the Gateway, and -optional channels — they just differ in how you interact with the setup. +optional chat channels — they just differ in how you interact with the setup. ## Which path should I use? @@ -32,8 +32,9 @@ Regardless of which path you choose, onboarding sets up: 1. **Model provider and auth** — API key, OAuth, or setup token for your chosen provider 2. **Workspace** — directory for agent files, bootstrap templates, and memory 3. **Gateway** — port, bind address, auth mode -4. **Channels** (optional) — bundled chat channels such as Feishu, Google Chat, - Microsoft Teams, Telegram, WhatsApp, Discord, and more +4. **Channels** (optional) — built-in and bundled chat channels such as + BlueBubbles, Discord, Feishu, Google Chat, Mattermost, Microsoft Teams, + Telegram, WhatsApp, and more 5. **Daemon** (optional) — background service so the Gateway starts automatically ## CLI onboarding diff --git a/docs/start/openclaw.md b/docs/start/openclaw.md index 3c53ee6b8b0..5d0b3fc753e 100644 --- a/docs/start/openclaw.md +++ b/docs/start/openclaw.md @@ -16,7 +16,7 @@ You’re putting an agent in a position to: - run commands on your machine (depending on your tool policy) - read/write files in your workspace -- send messages back out via WhatsApp/Telegram/Discord/Mattermost (plugin) +- send messages back out via WhatsApp/Telegram/Discord/Mattermost and other bundled channels Start conservative: diff --git a/docs/start/wizard-cli-reference.md b/docs/start/wizard-cli-reference.md index a6ed512b078..a45e02f6251 100644 --- a/docs/start/wizard-cli-reference.md +++ b/docs/start/wizard-cli-reference.md @@ -19,7 +19,7 @@ Local mode (default) walks you through: - Model and auth setup (OpenAI Code subscription OAuth, Anthropic Claude CLI or API key, plus MiniMax, GLM, Ollama, Moonshot, StepFun, and AI Gateway options) - Workspace location and bootstrap files - Gateway settings (port, bind, auth, tailscale) -- Channels and providers (Telegram, WhatsApp, Discord, Google Chat, Mattermost plugin, Signal) +- Channels and providers (Telegram, WhatsApp, Discord, Google Chat, Mattermost, Signal, BlueBubbles, and other bundled channel plugins) - Daemon install (LaunchAgent, systemd user unit, or native Windows Scheduled Task with Startup-folder fallback) - Health check - Skills setup @@ -66,7 +66,7 @@ It does not install or modify anything on the remote host. - [Telegram](/channels/telegram): bot token - [Discord](/channels/discord): bot token - [Google Chat](/channels/googlechat): service account JSON + webhook audience - - [Mattermost](/channels/mattermost) plugin: bot token + base URL + - [Mattermost](/channels/mattermost): bot token + base URL - [Signal](/channels/signal): optional `signal-cli` install + account config - [BlueBubbles](/channels/bluebubbles): recommended for iMessage; server URL + password + webhook - [iMessage](/channels/imessage): legacy `imsg` CLI path + DB access diff --git a/docs/start/wizard.md b/docs/start/wizard.md index d30deee70ff..8e3e1379319 100644 --- a/docs/start/wizard.md +++ b/docs/start/wizard.md @@ -77,7 +77,7 @@ Onboarding starts with **QuickStart** (defaults) vs **Advanced** (full control). 3. **Gateway** — Port, bind address, auth mode, Tailscale exposure. In interactive token mode, choose default plaintext token storage or opt into SecretRef. Non-interactive token SecretRef path: `--gateway-token-ref-env `. -4. **Channels** — bundled chat channels such as Feishu, Google Chat, Microsoft Teams, Discord, Signal, Slack, Telegram, WhatsApp, BlueBubbles, iMessage, and more. +4. **Channels** — built-in and bundled chat channels such as BlueBubbles, Discord, Feishu, Google Chat, Mattermost, Microsoft Teams, QQ Bot, Signal, Slack, Telegram, WhatsApp, and more. 5. **Daemon** — Installs a LaunchAgent (macOS), systemd user unit (Linux/WSL2), or native Windows Scheduled Task with per-user Startup-folder fallback. If token auth requires a token and `gateway.auth.token` is SecretRef-managed, daemon install validates it but does not persist the resolved token into supervisor service environment metadata. If token auth requires a token and the configured token SecretRef is unresolved, daemon install is blocked with actionable guidance.