diff --git a/README.md b/README.md
index 6283d8f..417e0b9 100644
--- a/README.md
+++ b/README.md
@@ -67,6 +67,17 @@ Open [http://localhost:3333](http://localhost:3333) in your browser. For remote
 - **Built-in CLI terminal**: run OpenClaw commands from any page with streaming output, presets, favorites, and Tab completion.
 - **Ops actions**: restart gateway, view logs, health check, backups (local + NAS), and cron management.
 - **Telegram-first workflow**: safer sub-agent setup flow + allowlist helper + warnings for group privacy.
+## Channel Support
+
+OCM is a local UI for OpenClaw. The core features (agent trees, routing, models/auth, ops, backups) are channel-agnostic.
+
+Current focus:
+
+- **Telegram** — best supported and most documented today
+- **Discord** — supported (recommended for private channels/threads + strict allowlist)
+- **Feishu / Lark (飞书)** — supported (Beta; enterprise-oriented setup)
+- **WhatsApp** — **not supported for sub-agent workflows** (platform constraints make reliable multi-agent isolation + routing hard)
+
 ## Telegram Workflow & Safety
 
 OCM is designed primarily for **Telegram-based OpenClaw workflows**:
diff --git a/docs/FAQ.md b/docs/FAQ.md
index 6d61bdc..70dccfc 100644
--- a/docs/FAQ.md
+++ b/docs/FAQ.md
@@ -51,3 +51,13 @@ That said, your local OpenClaw config contains sensitive information. Follow the
 - don't share raw screenshots without redaction
 
 See: `docs/SECURITY.md`.
+
+
+## Q: 为什么 OCM 暂时不支持 WhatsApp 的 sub-agent 工作流？
+
+WhatsApp 在 bot/group 自动化能力上有较多平台限制（接入方式、权限与路由粒度、稳定性等）。
+
+OCM 的 sub-agent 模式依赖清晰的“会话边界 + 路由 + 最小权限”来保证安全和可维护性。
+因此我们目前不把 WhatsApp 作为 sub-agent 的推荐渠道，暂不支持该模式。
+
+如果未来支持 WhatsApp，更可能是 **单聊通知/轻量交互** 方向，而不是多 sub-agent 的群聊拓扑。
diff --git a/docs/SECURITY.md b/docs/SECURITY.md
index 1d9495d..640864c 100644
--- a/docs/SECURITY.md
+++ b/docs/SECURITY.md
@@ -20,6 +20,27 @@ Critical BotFather settings:
 - Allow Groups = ON
 - Group Privacy = OFF
 
+## Discord safety
+
+Recommended defaults (especially for open-source / shared servers):
+
+- Prefer **private channels / private threads** as agent boundaries.
+- Use a strict **allowlist** of channels/threads the bot is allowed to respond in.
+- Apply **least-privilege** Discord permissions when installing the bot (only what you need).
+- Avoid running memory-enabled agents in public channels.
+
+## Feishu / Lark (飞书) safety
+
+Feishu is enterprise-oriented and typically requires more permission setup:
+
+- Request the smallest permission scope possible for your app/bot.
+- Treat group visibility as a security boundary (who can see the bot’s outputs).
+- Prefer separate chats/spaces for different agents to reduce context bleed.
+
+## WhatsApp note
+
+WhatsApp is not a recommended target for sub-agent topology workflows. Constraints in bot/group automation make reliable multi-agent isolation + routing difficult.
+
 ## Sharing screenshots
 
 If you share screenshots publicly:
diff --git a/docs/USAGE_GUIDE.en.md b/docs/USAGE_GUIDE.en.md
index af7a29e..0ea742f 100644
--- a/docs/USAGE_GUIDE.en.md
+++ b/docs/USAGE_GUIDE.en.md
@@ -27,12 +27,20 @@ OCM’s role: **a zero-dependency local UI** that helps you view and update Open
 
 ---
 
-## 1) Why Telegram groups are the best way to build sub-agents
+## 1) Recommended: Telegram group workflow (best supported)
 
 Think of it as:
 
 > **One Telegram group = one agent boundary** (context + purpose + workspace).
 
+### Notes for other channels
+
+OCM is expanding beyond Telegram:
+
+- **Discord**: recommended to use **private channels/threads** as boundaries + strict allowlist routing.
+- **Feishu / Lark (飞书)**: supported (Beta); enterprise-oriented setup with stronger permission/visibility considerations.
+- **WhatsApp**: not recommended for sub-agent topology workflows (not supported).
+
 ### Benefits
 
 1) **Clear isolation**
diff --git a/docs/USAGE_GUIDE.zh-CN.md b/docs/USAGE_GUIDE.zh-CN.md
index ba6bf3f..9a51b37 100644
--- a/docs/USAGE_GUIDE.zh-CN.md
+++ b/docs/USAGE_GUIDE.zh-CN.md
@@ -27,10 +27,18 @@ OCM 的定位：**把配置变更“可视化 + 可检查 + 可回滚（配合
 
 ---
 
-## 1) 为什么用 Telegram group 来建 Sub-Agent 最合适
+## 1) 推荐：Telegram 群组工作流（目前支持最好）
 
 > 这里讨论的是 OpenClaw 的一种非常实用的工作方式：**“一个 Telegram 群 = 一个 Agent 的工作空间/人格/上下文边界”**。
 
+### 其他渠道说明
+
+OCM 正在扩展 Telegram 之外的渠道支持：
+
+- **Discord**：建议用**私密频道/私密 thread**作为边界，并启用严格 allowlist 路由。
+- **飞书 / Lark**：支持（Beta）；企业协作场景更强，但权限/可见性边界需要更谨慎。
+- **WhatsApp**：不适合做 sub-agent 群聊拓扑（暂不支持）。
+
 ### 1.1 Telegram group 方案的优势
 
 1. **边界天然清晰**