Docs: merge remaining channel support notes

Merged after adding Backups/Rollback docs + README screenshot gallery (v0.8.2).

DEVLOG.md

@@ -1,7 +1,64 @@
 # OpenClaw Manager — 开发日志
 
-> 最后更新：2026-02-27
-> 当前版本：v0.7.1
+> 最后更新：2026-03-01
+> 当前版本：v0.9.0
+
+---
+
+
+## v0.9.0 更新日志（2026-03-01）
+
+### New Features
+
+- Agents: Add Agent / Add Sub-Agent 向导支持 Telegram + Discord
+  - Telegram: 传统 group 绑定
+  - Discord: 主 Agent 建议绑定 Channel；Sub-Agent 建议绑定 Thread
+- Routing: 删除绑定提示文案增强（支持“更换 group/thread → 先删旧绑定再加新绑定”）
+
+### UX / UI
+
+- 顶部居中显示醒目的 OCM 版本标识
+- Agents 页面：Agent Tree 支持显示 bindings 概览（Telegram/Discord）并按 parentAgentId 分组
+- Setup Guide：补全 Telegram Allow Groups 步骤；Discord guide 按 channel/thread 经验重写
+
+### Fixes
+
+- 修复 MAIN_HTML_SCRIPT 内联 JS 语法问题（tree toggle / i18n 单引号等），避免启动自检失败
+
+## Unreleased（2026-02-28）
+
+### Dashboard / Layout
+
+- Removed the dashboard `HTTP Ping` field (often misleading in Telegram gateway setups)
+- Expanded dashboard visibility with richer gateway routing metadata:
+  - bind host
+  - telegram account count
+  - group count
+  - binding count
+  - allowFrom count
+- Reordered dashboard cards and made `Agents` / `Gateway` cards wider for denser information display
+
+### Bug Fixes
+
+- Fixed `main` agent workspace file browsing/editing fallback:
+  - when agent-level workspace is empty, it now resolves from defaults or `workspace/<agentId>`
+  - writing files now ensures workspace directory exists before save
+
+### UX Clarification
+
+- Channels page hint text updated to position it as **advanced routing management**
+- Clarifies scope difference from Agents page (daily add/remove should stay in Agents)
+- Navigation label updated from `Channels` to `Routing` to reduce conceptual overlap with Agent lifecycle management
+- Added `Routing` page agent filter (`All Agents` + per-agent quick filter) for easier large-tree inspection
+- Added compact grouped rendering in `Routing`: bindings are grouped by agent with expand/collapse support for denser large-config browsing
+
+### Settings UX
+
+- Merged `Models` and `Auth` pages into a single `Models & Auth` tab
+
+### Stats
+
+- Added daily (`1 day`) range option and set it as default
 
 ---
 

README.md

@@ -1,6 +1,6 @@
 # OpenClaw Manager (OCM)
 
-A zero-dependency, single-file web dashboard for [OpenClaw](https://github.com/anthropics/openclaw). Manage agents, monitor token usage, and run commands — all from your browser, no `npm install` required.
+A zero-dependency local control panel for [OpenClaw](https://github.com/anthropics/openclaw). Manage agents, bindings, logs, commands, and rollback from your browser — no `npm install` required.
 
 [中文说明](#中文说明) · [中文使用说明（含截图）](docs/USAGE_GUIDE.zh-CN.md) · [English Guide (with screenshots)](docs/USAGE_GUIDE.en.md)
 
@@ -31,50 +31,68 @@ Open [http://localhost:3333](http://localhost:3333) in your browser. For remote
 - Changelog: docs/CHANGELOG.md
 
 
+## Why OCM
+
+OCM is best thought of as an **OpenClaw control panel**, not just a config editor.
+
+It helps with three things that become painful fast in raw JSON / terminal workflows:
+
+- **Agent topology** — see which agent is bound to which chat/channel/thread
+- **Everyday operations** — run CLI commands, inspect health/logs, restart gateway
+- **Safer changes** — update config with backups and rollback nearby
+
 ## Features
 
-**Screenshots** — Redacted UI walkthrough (no personal paths, no Telegram IDs):
+<details>
+<summary><b>Screenshots</b> (redacted: no personal paths, no Telegram IDs)</summary>
 
-![](docs/redacted-screenshots/dashboard.jpg)
+<p>
+  <img src="docs/redacted-screenshots/dashboard.jpg" width="240" />
+  <img src="docs/redacted-screenshots/agents.jpg" width="240" />
+  <img src="docs/redacted-screenshots/channels.jpg" width="240" />
+  <img src="docs/redacted-screenshots/models.jpg" width="240" />
+  <img src="docs/redacted-screenshots/auth.jpg" width="240" />
+  <img src="docs/redacted-screenshots/stats.jpg" width="240" />
+  <img src="docs/redacted-screenshots/cron.jpg" width="240" />
+  <img src="docs/redacted-screenshots/actions.jpg" width="240" />
+  <img src="docs/redacted-screenshots/cli.jpg" width="240" />
+  <img src="docs/redacted-screenshots/cli-output.jpg" width="240" />
+  <img src="docs/redacted-screenshots/backup-rollback.jpg" width="240" />
+</p>
 
-![](docs/redacted-screenshots/agents.jpg)
+</details>
 
-![](docs/redacted-screenshots/channels.jpg)
+- **Agent Management** — Add main agents and sub-agents through a guided setup flow. View all agents in a tree structure with model selection, workspace browsing, and inline configuration.
+- **Usage Statistics** — Real token usage data parsed directly from OpenClaw session files. Breakdown by model, agent, and day with a visual chart.
+- **Model & Auth** — Configure models from your registered provider list. Follow built-in guides for provider authentication setup.
+- **Built-in CLI** — Available from any page (top-right **Terminal** + bottom dock). Run OpenClaw commands with **real-time streaming output**, **Tab completion**, built-in presets, and your own saved favorites.
+- **Ops Panel** — Restart gateway, view logs, run health checks, manage backups, **rollback/restore configs**, and handle cron tasks.
+- **Backups / Rollback** — Browse auto-snapshots of `openclaw.json*` and restore any previous version (current config is auto-backed up first).
+- **Bilingual UI** — English and Chinese interface with one-click language switching.
 
-![](docs/redacted-screenshots/models.jpg)
+## What's New (v0.9.x)
 
-![](docs/redacted-screenshots/auth.jpg)
+- **Discord support (v0.9.x)**: add agent/sub-agent flows for Discord (main agent binds channel; sub-agent binds thread).
+- **README screenshots gallery**: all screenshots are now grouped into one collapsible section to keep the homepage short.
+- **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
 
-![](docs/redacted-screenshots/stats.jpg)
+OCM is a local UI for OpenClaw. Core features like agent trees, routing, models/auth, ops, backups, and the built-in CLI are channel-agnostic.
 
-![](docs/redacted-screenshots/cron.jpg)
+Current channel positioning:
 
+- **Telegram** — best supported and most documented today
+- **Discord** — supported; recommended for private channels/threads with strict allowlist
+- **Feishu / Lark** — supported in broader OpenClaw ecosystems, but not a primary OCM workflow today
+- **WhatsApp** — not recommended for sub-agent topology workflows
 
-**Agent Management** — Add main agents and sub-agents through a guided setup flow. View all agents in a tree structure with model selection, workspace browsing, and inline configuration.
+## Recommended Workflows
 
-**Usage Statistics** — Real token usage data parsed directly from OpenClaw session files. Breakdown by model, agent, and day with a visual chart.
+OCM is **Telegram-first, not Telegram-only**. Telegram is the smoothest path today, but OCM is also useful for local ops, Discord routing, model/auth management, and backups.
 
-**Model & Auth** — Configure models from your registered provider list. Follow built-in guides for provider authentication setup.
-
-**Built-in CLI** — Run any OpenClaw CLI command with real-time streaming output. Includes tab completion and saved favorites.
-
-![](docs/redacted-screenshots/cli.jpg)
-
-**Ops Panel** — Restart gateway, view logs, run health checks, manage backups (local + NAS via SFTP/rsync), and handle cron tasks.
-
-**Bilingual UI** — English and Chinese interface with one-click language switching.
-
-## What's New (v0.7.x)
-
-- **Dashboard redesign**: circular CPU/RAM/DISK gauges + system/gateway/agent overview, with optional auto-refresh.
-- **Sub-agent creation flow**: step-by-step Telegram guide (BotFather → group → get group ID → fill form), with explicit safety warnings.
-- **Telegram allowlist helper**: optional “Your Telegram User ID” field can auto-append to `channels.telegram.allowFrom`.
-- **Model dropdown = real CLI output**: selectors are sourced from `openclaw models list` (with a warning if parsing fails).
-- **Cache-busting**: response headers + version checks help prevent stale frontend after updates.
-- **Setup page EN localization**: first-run directory selection page is fully bilingual.
-
-
-## Telegram Workflow & Safety
+### Telegram Workflow & Safety
 
 OCM is designed primarily for **Telegram-based OpenClaw workflows**:
 
@@ -120,6 +138,18 @@ You can also create `manager-config.json` manually:
 
 `manager-config.json` is gitignored and won't be committed.
 
+## First-Run Experience
+
+The first thing new users need is confidence that OCM is pointed at the right OpenClaw directory and that the gateway is healthy. The Dashboard, built-in CLI, and health/ops actions are intended to make that first-run check fast and visible.
+
+Recommended first demo flow:
+
+1. Start OCM
+2. Open Dashboard and confirm gateway health
+3. Open Agents / Routing and inspect bindings
+4. Run one CLI command from the built-in terminal
+5. Try backup / rollback from Ops
+
 ## Remote Access
 
 By default OCM binds to `0.0.0.0` (all interfaces). Access it from another device on your LAN using the IP shown at startup. To restrict to localhost only:
@@ -213,3 +243,9 @@ bash start.sh --dir /path/to/.openclaw --port 8080
 ```json
 { "dir": "~/.openclaw" }
 ```
+
+
+## Discord (thread-first) notes
+
+- Recommended: keep top-level agents in dedicated channels, and bind sub-agents to **threads** (one thread per task).
+- To switch a Telegram group / Discord thread binding: go to **Routing** → remove the old binding → add a new binding with the new ID/link.

docs/CHANGELOG.md

@@ -2,6 +2,21 @@
 
 This is a user-facing summary derived from `DEVLOG.md`.
 
+## v0.9.0
+- Agents: Telegram + Discord support in Add Agent / Add Sub-Agent wizard (main agent binds channel; sub-agent binds thread).
+- UI: top-center OCM version badge; improved Telegram/Discord setup guides.
+
+## v0.8.2
+- Docs: reorganize README screenshots into a collapsible gallery to reduce scroll.
+- Docs: add Backups / Rollback screenshot and README feature blurb.
+- Docs: refresh redacted screenshots (Channels + Actions + Stats) and feature descriptions.
+
+## v0.8.1
+- Docs: add Stats screenshot and expand feature list.
+
+## v0.8.0
+- Docs: bilingual usage guides refreshed (EN + zh-CN) with redacted screenshots.
+
 ## v0.7.6
 - Docs: annotated screenshots with arrows for key UI controls.
 

docs/CONTRIBUTING.md

@@ -0,0 +1,65 @@
+# Contributing (OCM)
+
+This repo is optimized for fast iteration and safe maintenance.
+
+## Workflow (PM + Codex)
+
+Default rule:
+
+- Codex implements changes on a **new branch** and opens a **PR**.
+- Xiao Qiang (PM) reviews + runs local smoke tests.
+- Tao approves.
+- Only after explicit approval, we merge.
+
+Fast-path (small changes):
+
+- For small doc/copy/layout fixes, Tao allows **auto-merge after PM verification** (tests/smoke pass).
+- PM must still send Tao a short completion note with the PR link and summary.
+
+
+## Versioning
+
+- Single source of truth:
+  - `package.json#version`
+  - `openclaw-manager.js` → `APP_VERSION`
+- When bumping a version, update **both** in the same commit.
+- Prefer **semver-ish**: `MAJOR.MINOR.PATCH` (e.g. `0.8.2`).
+
+## Language policy (Docs + UI)
+
+- **DEVLOG.md must be English-only.**
+- UI:
+  - English mode should not show Chinese strings (except user-provided content).
+  - Chinese mode can be fully Chinese.
+- When adding new UI strings, ensure both locales are updated.
+
+## README policy
+
+- Keep the README homepage **short**.
+- Screenshots should be grouped (e.g. in a collapsible gallery) to avoid long scroll.
+- The “Features” section should be **complete** and reflect actual UI capabilities.
+
+## Screenshots (redaction)
+
+- Store public screenshots under: `docs/redacted-screenshots/`
+- Redact sensitive info:
+  - local username/path fragments
+  - Telegram peer IDs
+  - any tokens/keys
+- Prefer **English UI** screenshots.
+- Prefer clean crops (avoid arrows/annotations unless truly necessary).
+
+## Text style
+
+- Be concrete and user-focused.
+- Prefer consistent naming:
+  - “Remote backup setup” (not “NAS backup setup”)
+  - “Backups / Rollback” for restore/snapshot functionality
+
+## PR checklist
+
+- [ ] Description includes: what/why/how
+- [ ] If UI changed: include screenshots
+- [ ] Version updated when needed
+- [ ] English UI audited (no stray Chinese)
+- [ ] `DEVLOG.md` updated (English-only)

docs/FAQ.md

@@ -51,3 +51,12 @@ 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 模式依赖清晰的会话边界、独立路由和可控权限，因此目前更推荐 Telegram / Discord 这类更容易做隔离的渠道。
+
+如果未来支持 WhatsApp，更可能先从通知或轻量交互开始，而不是多 sub-agent 群聊拓扑。

docs/SECURITY.md

@@ -28,3 +28,25 @@ If you share screenshots publicly:
 - blur any tokens/keys if visible
 
 This repo contains **redacted + annotated** screenshots under `docs/annotated-screenshots/`.
+
+
+## Discord safety
+
+Recommended defaults (especially for shared/community servers):
+
+- Prefer **private channels / private threads** as agent boundaries
+- Use a strict **allowlist** of channels/threads the bot may respond in
+- Avoid giving memory-enabled or high-privilege agents broad public exposure
+- Prefer least-privilege Discord permissions for the bot
+
+## Feishu / Lark safety
+
+Feishu is more enterprise-oriented and usually needs stricter permission design:
+
+- Request the smallest permission scope possible
+- Treat chat/group visibility as a security boundary
+- 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 and routing harder.

docs/USAGE_GUIDE.en.md

@@ -2,7 +2,7 @@
 
 > Audience: People who already have OpenClaw running locally (you can run `openclaw status` and read `openclaw gateway logs`).
 >
-> Goal: Use **OpenClaw Manager (OCM)** to make agent/sub-agent setup and day-to-day ops **visual, safer, and easier to audit**.
+> Goal: Use **OpenClaw Manager (OCM)** as an **OpenClaw control panel** for agent setup, routing, health checks, built-in CLI, and safer config changes.
 
 ---
 
@@ -60,7 +60,18 @@ Recommended rule:
 
 ---
 
-## 2) Start OCM (macOS)
+## 2) First-run mindset
+
+For new users, the first win is not “configure everything” — it is:
+
+1. Confirm OCM found the right OpenClaw directory
+2. Confirm the gateway is healthy
+3. Confirm you can inspect agents / bindings
+4. Confirm the built-in CLI works
+
+That is why Dashboard + Routing + built-in CLI are the most important first-run surfaces.
+
+## 3) Start OCM (macOS)
 
 From the repo directory:
 
@@ -78,7 +89,7 @@ bash start.sh --host 127.0.0.1
 
 ---
 
-## 3) Dashboard: check health first
+## 4) Dashboard: check health first
 
 The Dashboard is your “sanity check”:
 
@@ -92,11 +103,11 @@ Screenshot:
 
 ---
 
-## 4) Create a main agent (with its own Telegram bot)
+## 5) Create a main agent (with its own Telegram bot)
 
 > 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**
@@ -115,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**:
 
@@ -132,15 +143,15 @@ OCM writes the agent + Telegram account/binding into `openclaw.json`.
 
 ---
 
-## 5) Create a sub-agent (recommended workflow)
+## 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`:
 
@@ -172,7 +183,37 @@ If you use `channels.telegram.allowFrom`, OCM can take “Your Telegram User ID
 
 ---
 
-## 6) Verify bindings (Channels)
+
+
+## 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)
+
+### 6.5.1 Add a Discord main agent
+
+Go to **Agents** → `+ Add Agent` → set **Channel = Discord**:
+
+![](redacted-screenshots/agents-discord-add-agent.png)
+
+Steps:
+1) Create/select a dedicated Discord **channel** (private recommended)
+2) Right-click channel → **Copy Link** → paste into the form (auto-parses channelId)
+
+### 6.5.2 Add a Discord sub-agent (thread-first)
+
+Go to **Agents** → `+ Add Sub-Agent` → set **Channel = Discord (thread only)**:
+
+![](redacted-screenshots/agents-discord-add-subagent.png)
+
+Steps:
+1) Create a **thread** under the main channel (one thread per task)
+2) If it is a private thread, add the bot to the thread
+3) Right-click thread → **Copy Link** → paste into the form (auto-parses threadId)
+
+## 7) Verify bindings (Channels)
 
 Go to **Channels**:
 
@@ -184,7 +225,7 @@ Here you can quickly validate:
 
 ---
 
-## 7) Model settings (Models)
+## 8) Model settings (Models)
 
 Go to **Models**:
 
@@ -223,6 +264,20 @@ OCM parses usage from OpenClaw session JSONL files.
 
 ---
 
+## 10) Actions menu (ops shortcuts)
+
+The **⚡ Actions** dropdown in the top-right provides common operational shortcuts:
+- Restart Gateway
+- Live Logs
+- Manual Backup / Backups & Rollback
+- NAS Backup Setup
+- Health Check
+- Open Config Dir / Switch OpenClaw Dir
+
+Screenshot:
+
+![](redacted-screenshots/actions.jpg)
+
 ## 10) Cron jobs (Cron)
 
 Go to **Cron**:
@@ -252,6 +307,8 @@ Screenshot:
 
 ![](redacted-screenshots/cli.jpg)
 
+![](redacted-screenshots/cli-output.jpg)
+
 ## 11) Fast troubleshooting
 
 ### “Typing…” but no reply in a Telegram group

docs/USAGE_GUIDE.zh-CN.md

@@ -2,7 +2,7 @@
 
 > 面向：已经在本机安装并跑通 OpenClaw 的用户（至少会用 `openclaw status` / `openclaw gateway logs`）
 >
-> 目标：用 **OpenClaw Manager (OCM)** 把“创建 Agent / Sub-Agent、绑定 Telegram 群、管理模型/认证、看用量、看 cron”这套流程做成可视化、可回溯、低风险。
+> 目标：把 **OpenClaw Manager (OCM)** 当成 **OpenClaw 控制台** 来用：管理 Agent、查看 Routing、做健康检查、运行内置 CLI，并更安全地修改配置。
 
 ---
 
@@ -54,9 +54,20 @@ OCM 的定位：**把配置变更“可视化 + 可检查 + 可回滚（配合
 
 ---
 
-## 2) 启动与进入 OCM
+## 2) 第一次使用时最该确认什么
 
-### 2.1 启动（macOS）
+对新用户来说，第一步不是“先把所有配置都改完”，而是先确认四件事：
+
+1. OCM 找到的是正确的 OpenClaw 目录
+2. Gateway 是健康的
+3. Agent / Routing 能正常查看
+4. 内置终端可以正常跑命令
+
+所以第一次使用时，最重要的页面其实是 Dashboard、Routing 和内置终端。
+
+## 3) 启动与进入 OCM
+
+### 3.1 启动（macOS）
 
 在 OCM 目录：
 
@@ -68,7 +79,7 @@ bash start.sh
 
 > 需要限制只能本机访问：`bash start.sh --host 127.0.0.1`
 
-### 2.2 Dashboard（先看健康状态）
+### 3.2 Dashboard（先看健康状态）
 
 建议第一步先看 Dashboard，确认：
 - 机器资源（CPU/RAM/DISK）
@@ -81,11 +92,11 @@ bash start.sh
 
 ---
 
-## 3) 创建主 Agent（Main Agent / 独立 Bot）
+## 4) 创建主 Agent（Main Agent / 独立 Bot）
 
 > 你的 `main` 一般是默认存在的；这里重点讲“新增一个 **拥有独立 Telegram bot 的主 Agent**”。
 
-### 3.1 BotFather 侧准备（必须）
+### 4.1 BotFather 侧准备（必须）
 
 1) 创建 bot
 - 在 Telegram 找 **BotFather**
@@ -101,7 +112,7 @@ bash start.sh
 
 > 如果 Group Privacy 没关，bot 在群里看不到普通消息，会表现成“经常 typing 但没输出 / 没反应”。
 
-### 3.2 在 OCM 添加主 Agent
+### 4.2 在 OCM 添加主 Agent
 
 进入 **Agents** 页面：
 
@@ -117,14 +128,14 @@ bash start.sh
 
 ---
 
-## 4) 创建 Sub-Agent（最常用）
+## 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`，按引导做：
 
@@ -155,7 +166,37 @@ OCM 的表单里可以填 “Your Telegram User ID”，让它自动把你的 us
 
 ---
 
-## 5) 绑定检查（Channels 页）
+
+
+## 6) Discord 工作流（主 Agent + Sub-Agent）
+
+OCM 也支持 Discord：
+
+- **主 Agent**：绑定到一个专用 **Channel**（channelId）
+- **Sub-Agent**：绑定到该 Channel 下的专用 **Thread**（threadId，thread-first）
+
+### 5.1 添加 Discord 主 Agent
+
+进入 **Agents** → `+ Add Agent` → 选择 **渠道 = Discord**：
+
+![](redacted-screenshots/agents-discord-add-agent.png)
+
+步骤：
+1) 创建/选择一个专用 Discord Channel（建议私密）
+2) 右键 Channel → **Copy Link** → 粘贴到表单（自动解析 channelId）
+
+### 5.2 添加 Discord Sub-Agent（Thread 优先）
+
+进入 **Agents** → `+ Add Sub-Agent` → 选择 **渠道 = Discord (thread only)**：
+
+![](redacted-screenshots/agents-discord-add-subagent.png)
+
+步骤：
+1) 在主 Channel 下新建 Thread（建议“一个任务一个 thread”）
+2) 如果是 private thread，需要把 bot 拉进 thread
+3) 右键 Thread → **Copy Link** → 粘贴到表单（自动解析 threadId）
+
+## 7) 绑定检查（Channels 页）
 
 进入 **Channels**：
 
@@ -169,7 +210,7 @@ OCM 的表单里可以填 “Your Telegram User ID”，让它自动把你的 us
 
 ---
 
-## 6) 模型管理（Models 页）
+## 8) 模型管理（Models 页）
 
 进入 **模型**：
 
@@ -181,7 +222,7 @@ OCM 的表单里可以填 “Your Telegram User ID”，让它自动把你的 us
 
 ---
 
-## 7) 认证管理（Auth 页）
+## 9) 认证管理（Auth 页）
 
 进入 **认证**：
 
@@ -224,6 +265,22 @@ OCM 内置一个 CLI 面板，用来直接运行 OpenClaw 命令（例如：`ope
 
 ![](redacted-screenshots/cli.jpg)
 
+![](redacted-screenshots/cli-output.jpg)
+
+## 9) Actions 菜单（运维快捷入口）
+
+右上角 **⚡ Actions** 下拉菜单提供常用运维操作：
+- Restart Gateway（重启网关）
+- Live Logs（实时日志）
+- Manual Backup / Backups & Rollback（备份/回滚）
+- NAS Backup Setup（NAS 备份配置）
+- Health Check（健康检查）
+- Open Config Dir / Switch OpenClaw Dir（打开/切换配置目录）
+
+截图示例：
+
+![](redacted-screenshots/actions.jpg)
+
 ## 9) Cron（定时任务）
 
 进入 **Cron**：

package.json

@@ -1,7 +1,7 @@
 {
   "name": "openclaw-manager",
-  "version": "0.7.1",
-  "description": "A local web UI for managing OpenClaw AI agents — no npm install required",
+  "version": "0.9.0",
+  "description": "A local web UI for managing OpenClaw AI agents \u2014 no npm install required",
   "main": "openclaw-manager.js",
   "scripts": {
     "start": "node openclaw-manager.js",