From 2424a58721c11211adb67bd254bc91842b674e74 Mon Sep 17 00:00:00 2001 From: Tao Date: Fri, 6 Mar 2026 20:22:08 +1000 Subject: [PATCH] Clean up guide section numbering --- docs/USAGE_GUIDE.en.md | 14 +++++++------- docs/USAGE_GUIDE.zh-CN.md | 12 ++++++------ 2 files changed, 13 insertions(+), 13 deletions(-) diff --git a/docs/USAGE_GUIDE.en.md b/docs/USAGE_GUIDE.en.md index 5b08988..ef0d8d8 100644 --- a/docs/USAGE_GUIDE.en.md +++ b/docs/USAGE_GUIDE.en.md @@ -107,7 +107,7 @@ Screenshot: > Your `main` agent usually exists already. This section is for creating an additional **root agent** that owns its own Telegram bot/account. -### 4.1 BotFather prerequisites +### 5.1 BotFather prerequisites 1) Create a bot - In Telegram, open **BotFather** @@ -126,7 +126,7 @@ If group privacy is ON, the bot can’t see normal group messages. The symptom o - “typing…” appears frequently - sometimes no response at all -### 4.2 Add the agent in OCM +### 5.2 Add the agent in OCM Go to **Agents**: @@ -145,13 +145,13 @@ OCM writes the agent + Telegram account/binding into `openclaw.json`. ## 6) Create a sub-agent (recommended workflow) -### 5.1 Why a new group per sub-agent +### 6.1 Why a new group per sub-agent - clean context isolation - easier debugging - easy to “turn off” by muting a group -### 5.2 Step-by-step +### 6.2 Step-by-step In **Agents** → `+ Add Sub-Agent`: @@ -185,14 +185,14 @@ If you use `channels.telegram.allowFrom`, OCM can take “Your Telegram User ID -## 5) Discord workflow (main agent + sub-agent) +## 6.5) Discord workflow (main agent + sub-agent) OCM also supports Discord: - **Main agent**: bind to a dedicated **Channel** (channelId) - **Sub-agent**: bind to a dedicated **Thread** under that channel (threadId) -### 5.1 Add a Discord main agent +### 6.5.1 Add a Discord main agent Go to **Agents** → `+ Add Agent` → set **Channel = Discord**: @@ -202,7 +202,7 @@ Steps: 1) Create/select a dedicated Discord **channel** (private recommended) 2) Right-click channel → **Copy Link** → paste into the form (auto-parses channelId) -### 5.2 Add a Discord sub-agent (thread-first) +### 6.5.2 Add a Discord sub-agent (thread-first) Go to **Agents** → `+ Add Sub-Agent` → set **Channel = Discord (thread only)**: diff --git a/docs/USAGE_GUIDE.zh-CN.md b/docs/USAGE_GUIDE.zh-CN.md index 267f214..b19588a 100644 --- a/docs/USAGE_GUIDE.zh-CN.md +++ b/docs/USAGE_GUIDE.zh-CN.md @@ -67,7 +67,7 @@ OCM 的定位:**把配置变更“可视化 + 可检查 + 可回滚(配合 ## 3) 启动与进入 OCM -### 2.1 启动(macOS) +### 3.1 启动(macOS) 在 OCM 目录: @@ -79,7 +79,7 @@ bash start.sh > 需要限制只能本机访问:`bash start.sh --host 127.0.0.1` -### 2.2 Dashboard(先看健康状态) +### 3.2 Dashboard(先看健康状态) 建议第一步先看 Dashboard,确认: - 机器资源(CPU/RAM/DISK) @@ -96,7 +96,7 @@ bash start.sh > 你的 `main` 一般是默认存在的;这里重点讲“新增一个 **拥有独立 Telegram bot 的主 Agent**”。 -### 3.1 BotFather 侧准备(必须) +### 4.1 BotFather 侧准备(必须) 1) 创建 bot - 在 Telegram 找 **BotFather** @@ -112,7 +112,7 @@ bash start.sh > 如果 Group Privacy 没关,bot 在群里看不到普通消息,会表现成“经常 typing 但没输出 / 没反应”。 -### 3.2 在 OCM 添加主 Agent +### 4.2 在 OCM 添加主 Agent 进入 **Agents** 页面: @@ -130,12 +130,12 @@ bash start.sh ## 5) 创建 Sub-Agent(最常用) -### 4.1 为什么 Sub-Agent 要用“新群” +### 5.1 为什么 Sub-Agent 要用“新群” - 让每个 Sub-Agent 有自己独立的对话上下文、任务边界 - 出问题直接在该群排查,不污染主 Agent 的对话 -### 4.2 Sub-Agent 创建流程(逐步) +### 5.2 Sub-Agent 创建流程(逐步) 进入 **Agents** 页面 → 点击 `+ Add Sub-Agent`,按引导做: