release: v0.9.0

README.md

@@ -1,74 +1,40 @@
 # OpenClaw Manager (OCM)
 
-A local control panel for [OpenClaw](https://github.com/anthropics/openclaw) that makes setup checks, agent management, health inspection, and recovery much easier — without living in JSON and terminal tabs all day.
+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.
 
 [中文说明](#中文说明) · [中文使用说明（含截图）](docs/USAGE_GUIDE.zh-CN.md) · [English Guide (with screenshots)](docs/USAGE_GUIDE.en.md)
 
 ---
 
-## Why OCM exists
+## Quick Start
 
-Running OpenClaw directly is powerful, but the day-to-day workflow can get messy fast:
+```bash
+# Clone
+git clone https://github.com/dtzp555-max/ocm.git
+cd ocm
 
-- `openclaw.json` is easy to break by hand
+# Run (no npm install needed)
-- agent / bot / channel bindings are hard to visualize
+bash start.sh        # macOS / Linux
-- health checks, logs, restarts, and rollback are scattered across terminal commands
+start.bat            # Windows
-- when something goes wrong, recovery is slower than it should be
 
-OCM gives you a **local control panel** for the things that become painful first:
+# Update
-- seeing your current setup clearly
+git pull --ff-only
-- operating it more safely
+```
-- recovering faster when something breaks
 
-## Is OCM for you?
+Open [http://localhost:3333](http://localhost:3333) in your browser. For remote access, use `bash start.sh --host 0.0.0.0`.
+## Docs
 
-**OCM is a good fit if:**
+- English guide: docs/USAGE_GUIDE.en.md
-- you already run OpenClaw locally
+- 中文使用说明: docs/USAGE_GUIDE.zh-CN.md
-- you want a visual control panel for agents, routing, logs, health, and backups
+- FAQ: docs/FAQ.md
-- you are tired of editing nested config by hand
+- Security notes: docs/SECURITY.md
-- you want safer rollback / recovery nearby
+- Changelog: docs/CHANGELOG.md
 
-**OCM is probably not the best starting point if:**
-- you have not installed OpenClaw yet
-- you expect every OS / channel workflow to be equally mature today
-- you want a hosted cloud dashboard instead of a local tool
 
-## What OCM helps you do
+## Features
-
-### 1) See your OpenClaw setup clearly
-- inspect agents and sub-agents in a tree
-- verify bindings and routing
-- view models, auth, usage, and health in one place
-
-### 2) Operate OpenClaw with less risk
-- restart gateway
-- inspect logs
-- run OpenClaw commands from the built-in terminal
-- make config changes with rollback nearby
-
-### 3) Recover faster when things go wrong
-- browse backups / snapshots
-- roll back config safely
-- keep troubleshooting and operational tools close to the same UI
-
-## See it quickly
-
-These are the highest-value surfaces for first-time users:
-
-<p>
-  <img src="docs/redacted-screenshots-refresh/dashboard-2026-03-07.jpg" width="860" />
-</p>
-
-<p>
-  <img src="docs/redacted-screenshots-refresh/agents-2026-03-07.jpg" width="280" />
-  <img src="docs/redacted-screenshots-refresh/cli-2026-03-07.jpg" width="280" />
-  <img src="docs/redacted-screenshots/actions.jpg" width="180" />
-</p>
-
-More screenshots: see the [full usage guide](docs/USAGE_GUIDE.en.md) or the gallery below.
 
 <details>
-<summary><b>Full screenshots gallery</b> (redacted: no personal paths, no Telegram IDs)</summary>
+<summary><b>Screenshots</b> (redacted: no personal paths, no Telegram IDs)</summary>
 
 <p>
   <img src="docs/redacted-screenshots/dashboard.jpg" width="240" />
@@ -86,76 +52,6 @@ More screenshots: see the [full usage guide](docs/USAGE_GUIDE.en.md) or the gall
 
 </details>
 
-## Quick Start (recommended path)
-
-```bash
-# Clone
-git clone https://github.com/dtzp555-max/ocm.git
-cd ocm
-
-# Run (no npm install needed)
-bash start.sh        # macOS / Linux
-start.bat            # Windows
-```
-
-Then open [http://localhost:3333](http://localhost:3333).
-
-For remote access, use:
-
-```bash
-bash start.sh --host 0.0.0.0
-```
-
-## First-run checklist
-
-For a good first experience, do these first:
-
-1. Confirm OCM found the correct OpenClaw directory
-2. Open **Dashboard** and check gateway health
-3. Open **Agents** / **Channels** and inspect bindings
-4. Open the built-in **Terminal** and run one OpenClaw command
-5. Check **Actions** / backup / rollback so recovery is nearby before you need it
-
-## Current support status
-
-**Best supported today**
-- macOS / Linux
-- local OpenClaw installations
-- local health / logs / ops / backup workflows
-- Telegram-first agent management workflows
-
-**Supported, but not equally smooth in every case**
-- Discord agent / thread workflows
-- more advanced routing setups
-- mixed environment / service layouts
-
-**Not the primary path today**
-- fully beginner-first OpenClaw onboarding
-- every OS / shell / service combination
-- WhatsApp-heavy sub-agent topology workflows
-
-## Common friction points
-
-The most common reasons OCM feels rough are not usually “the UI is broken”, but environment mismatch:
-
-- OpenClaw itself is not fully healthy yet
-- wrong OpenClaw directory
-- path / permission issues
-- different service/runtime layouts across machines
-- channel workflow differences
-
-That is why OCM should be thought of as a **control panel for an existing OpenClaw setup**, not a magic replacement for all installation complexity.
-
-## Docs
-
-- **Start here**: docs/USAGE_GUIDE.en.md
-- 中文使用说明: docs/USAGE_GUIDE.zh-CN.md
-- FAQ: docs/FAQ.md
-- Security notes: docs/SECURITY.md
-- Changelog: docs/CHANGELOG.md
-
-## Features by area
-
 - **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.
@@ -167,27 +63,11 @@ That is why OCM should be thought of as a **control panel for an existing OpenCl
 ## What's New (v0.9.x)
 
 - **Discord support (v0.9.x)**: add agent/sub-agent flows for Discord (main agent binds channel; sub-agent binds thread).
-- **README screenshots gallery**: screenshots grouped into a collapsible section so the homepage stays shorter.
+- **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.
-
+## Telegram Workflow & Safety
-## Channel Support
-
-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.
-
-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
-
-## Recommended Workflows
-
-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.
-
-### Telegram Workflow & Safety
 
 OCM is designed primarily for **Telegram-based OpenClaw workflows**:
 
@@ -233,18 +113,6 @@ 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:
@@ -287,38 +155,7 @@ MIT
 
 ## 中文说明
 
-OpenClaw Manager（OCM）是一个本地 OpenClaw 控制面板，用来更直观地管理 Agent、查看绑定关系、做健康检查、运行内置 CLI，并在改配置或排错时少踩坑。
+OpenClaw Manager 是一个零依赖的本地 Web 管理界面，用于可视化管理 [OpenClaw](https://github.com/anthropics/openclaw) AI 智能体。所有代码在一个 `.js` 文件中，只需 Node.js 18+，不需要 `npm install`。
-
-### OCM 解决什么问题
-
-直接使用 OpenClaw 很强，但日常维护很容易变成：
-- 改 `openclaw.json` 容易手滑
-- Agent / bot / 群 / 线程绑定关系很难一眼看清
-- 健康检查、日志、重启、回滚散落在多个终端命令里
-- 出问题时恢复链路不够顺手
-
-OCM 的定位不是替代 OpenClaw，而是给现有 OpenClaw 环境加一个**本地控制台**。
-
-### 适合谁
-
-**适合：**
-- 已经在本机跑通 OpenClaw 的用户
-- 想更直观地管理 Agent / Routing / Health / Logs / Backups 的用户
-- 不想频繁手改复杂 JSON 的用户
-
-**暂时不太适合：**
-- 还没装好 OpenClaw、希望 OCM 包办全部安装复杂度的新手
-- 默认期待所有平台 / 所有 channel 路线都同样成熟的用户
-- 想要云端托管产品而不是本地工具的用户
-
-### OCM 最有价值的三件事
-
-1. **看清你的 OpenClaw 结构**
-   - Agent 树、绑定关系、模型、认证、健康状态更直观
-2. **更安全地做运维操作**
-   - 重启 gateway、看日志、跑 CLI、改配置、回滚更顺手
-3. **出问题时恢复更快**
-   - 备份、回滚、排查入口都更近
 
 ### 快速开始
 
@@ -329,33 +166,49 @@ bash start.sh        # macOS / Linux
 start.bat            # Windows
 ```
 
-打开 [http://localhost:3333](http://localhost:3333)。
+访问 [http://localhost:3333](http://localhost:3333)。远程访问请使用 `bash start.sh --host 0.0.0.0`。
 
-### 第一次使用建议先做这几步
+### 功能
 
-1. 确认 OCM 找到了正确的 OpenClaw 目录
+- **Agent 管理** — 添加主 Agent 和子 Agent，树状结构查看，内联切换模型，浏览工作区文件
-2. 打开 **Dashboard** 看 gateway 是否健康
+- **使用统计** — 从 OpenClaw 会话文件解析真实 Token 用量，按模型/Agent/日期维度展示
-3. 打开 **Agents / Channels** 看绑定是否正确
+- **模型与认证** — 管理注册模型列表，内置 Provider 认证引导
-4. 打开内置 **Terminal** 跑一条 OpenClaw 命令
+- **内置终端** — 实时流式输出，预设命令，收藏夹，Tab 补全
-5. 看一眼 **Actions / 备份 / 回滚**，确保恢复路径就在手边
+- **运维面板** — 重启网关、查看日志、健康检查、本地/NAS 备份、Cron 任务管理
+- **双语界面** — 中英文一键切换
 
-### 当前支持定位
+### Telegram 场景与安全提示
 
-**目前最好用的场景：**
+OCM 主要面向 **Telegram 场景**：
-- macOS / Linux
-- 本地 OpenClaw 环境
-- 本地 health / logs / ops / backup 工作流
-- Telegram-first 的 Agent 管理方式
 
-**支持，但不保证同样顺滑：**
+- 通过群组绑定主 Agent，并在每条树下管理多个 Sub-Agent
-- Discord workflow
+- 让每个 Agent 拥有独立 `workspace`、`SOUL.md`、`MEMORY.md`
-- 更复杂的 routing / service 布局
+- 通过可视化方式更新 `openclaw.json`，减少手动改配置风险
-- 混合环境
+- 建议使用者已具备基础 OpenClaw CLI 操作经验（如 `onboard`、认证、查看网关日志）
 
-### 文档
+关键安全设置（务必确认）：
 
-- 英文使用说明：docs/USAGE_GUIDE.en.md
+- BotFather 里 **Allow Groups = ON**
-- 中文使用说明：docs/USAGE_GUIDE.zh-CN.md
+- BotFather 里 **Group Privacy = OFF**
-- FAQ：docs/FAQ.md
+- 每个 Agent 群组只保留“你自己 + 对应 Agent/Sub-Agent”
-- 安全说明：docs/SECURITY.md
+- 不要邀请其他人进组（会带来安全和 API 费用风险）
-- 更新记录：docs/CHANGELOG.md
+
+### 配置
+
+启动脚本自动检测 `~/.openclaw` 目录。如需指定其他路径：
+
+```bash
+bash start.sh --dir /path/to/.openclaw --port 8080
+```
+
+也可手动创建 `manager-config.json`：
+
+```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/FAQ.md

@@ -51,12 +51,3 @@ 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/SCREENSHOT_REFRESH_BRIEF.md

@@ -1,79 +0,0 @@
-# OCM Screenshot Refresh Brief
-
-Goal: refresh only the highest-value README screenshots first, not every screenshot.
-
-## Redaction rules
-Always hide or blur:
-- Telegram / Discord IDs
-- bindings / peer IDs / thread IDs
-- local filesystem paths containing Tao's name
-- account labels if they expose personal identifiers
-- anything that looks like a secret/token
-
-## Priority 1 screenshots
-
-### 1) Dashboard hero
-Purpose:
-- show OCM as a real control panel
-- support the README first-run / health story
-
-Wanted state:
-- Dashboard page open
-- gateway looks healthy if possible
-- cards readable
-- top bar clean
-- no obvious warning/noise unless it helps credibility
-
-Frame guidance:
-- browser window wide enough to show full dashboard naturally
-- keep top navigation visible
-- avoid cropping too tightly
-
-### 2) Agents page
-Purpose:
-- show the core product value: visible agent topology / structure
-
-Wanted state:
-- main agent + several sub-agents visible
-- structure easy to understand at a glance
-- avoid visual clutter where possible
-- keep model selectors/buttons visible, but not the focus
-
-Frame guidance:
-- enough width to show the tree clearly
-- IDs and personal paths redacted
-
-### 3) CLI / Terminal page
-Purpose:
-- show that OCM is not only a viewer; it can operate OpenClaw too
-
-Wanted state:
-- built-in terminal open
-- a real command visible (recommended: `openclaw status` or `openclaw doctor`)
-- real output visible
-- do not use tutorial arrows / annotation bubbles
-
-Frame guidance:
-- include command input and some output
-- avoid empty terminal state
-- redact paths / personal names
-
-## Priority 2 screenshots
-- Actions menu
-- Backup / rollback
-- Channels
-- Models
-- Auth
-- Cron
-- Stats
-
-## Selected refresh set (2026-03-07)
-- Dashboard: `docs/redacted-screenshots-refresh/dashboard-2026-03-07.jpg`
-- Agents: `docs/redacted-screenshots-refresh/agents-2026-03-07.jpg`
-- CLI: `docs/redacted-screenshots-refresh/cli-2026-03-07.jpg`
-- Keep using existing `docs/redacted-screenshots/actions.jpg` for now
-
-## Notes
-- Existing `actions.jpg` is already strong and can stay for now.
-- The new Dashboard and Agents captures are preferred for README hero/overview use.
-- The new CLI capture is preferred because it shows a real command and real output.

docs/SECURITY.md

@@ -28,25 +28,3 @@ 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)** as an **OpenClaw control panel** for agent setup, routing, health checks, built-in CLI, and safer config changes.
+> Goal: Use **OpenClaw Manager (OCM)** to make agent/sub-agent setup and day-to-day ops **visual, safer, and easier to audit**.
 
 ---
 
@@ -60,18 +60,7 @@ Recommended rule:
 
 ---
 
-## 2) First-run mindset
+## 2) Start OCM (macOS)
-
-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:
 
@@ -89,7 +78,7 @@ bash start.sh --host 127.0.0.1
 
 ---
 
-## 4) Dashboard: check health first
+## 3) Dashboard: check health first
 
 The Dashboard is your “sanity check”:
 
@@ -103,11 +92,11 @@ Screenshot:
 
 ---
 
-## 5) Create a main agent (with its own Telegram bot)
+## 4) 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.
 
-### 5.1 BotFather prerequisites
+### 4.1 BotFather prerequisites
 
 1) Create a bot
 - In Telegram, open **BotFather**
@@ -126,7 +115,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
 
-### 5.2 Add the agent in OCM
+### 4.2 Add the agent in OCM
 
 Go to **Agents**:
 
@@ -143,15 +132,15 @@ OCM writes the agent + Telegram account/binding into `openclaw.json`.
 
 ---
 
-## 6) Create a sub-agent (recommended workflow)
+## 5) Create a sub-agent (recommended workflow)
 
-### 6.1 Why a new group per sub-agent
+### 5.1 Why a new group per sub-agent
 
 - clean context isolation
 - easier debugging
 - easy to “turn off” by muting a group
 
-### 6.2 Step-by-step
+### 5.2 Step-by-step
 
 In **Agents** → `+ Add Sub-Agent`:
 
@@ -183,37 +172,7 @@ 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**:
 
@@ -225,7 +184,7 @@ Here you can quickly validate:
 
 ---
 
-## 8) Model settings (Models)
+## 7) Model settings (Models)
 
 Go to **Models**:
 

docs/USAGE_GUIDE.zh-CN.md

@@ -2,7 +2,7 @@
 
 > 面向：已经在本机安装并跑通 OpenClaw 的用户（至少会用 `openclaw status` / `openclaw gateway logs`）
 >
-> 目标：把 **OpenClaw Manager (OCM)** 当成 **OpenClaw 控制台** 来用：管理 Agent、查看 Routing、做健康检查、运行内置 CLI，并更安全地修改配置。
+> 目标：用 **OpenClaw Manager (OCM)** 把“创建 Agent / Sub-Agent、绑定 Telegram 群、管理模型/认证、看用量、看 cron”这套流程做成可视化、可回溯、低风险。
 
 ---
 
@@ -54,20 +54,9 @@ OCM 的定位：**把配置变更“可视化 + 可检查 + 可回滚（配合
 
 ---
 
-## 2) 第一次使用时最该确认什么
+## 2) 启动与进入 OCM
 
-对新用户来说，第一步不是“先把所有配置都改完”，而是先确认四件事：
+### 2.1 启动（macOS）
-
-1. OCM 找到的是正确的 OpenClaw 目录
-2. Gateway 是健康的
-3. Agent / Routing 能正常查看
-4. 内置终端可以正常跑命令
-
-所以第一次使用时，最重要的页面其实是 Dashboard、Routing 和内置终端。
-
-## 3) 启动与进入 OCM
-
-### 3.1 启动（macOS）
 
 在 OCM 目录：
 
@@ -79,7 +68,7 @@ bash start.sh
 
 > 需要限制只能本机访问：`bash start.sh --host 127.0.0.1`
 
-### 3.2 Dashboard（先看健康状态）
+### 2.2 Dashboard（先看健康状态）
 
 建议第一步先看 Dashboard，确认：
 - 机器资源（CPU/RAM/DISK）
@@ -92,11 +81,11 @@ bash start.sh
 
 ---
 
-## 4) 创建主 Agent（Main Agent / 独立 Bot）
+## 3) 创建主 Agent（Main Agent / 独立 Bot）
 
 > 你的 `main` 一般是默认存在的；这里重点讲“新增一个 **拥有独立 Telegram bot 的主 Agent**”。
 
-### 4.1 BotFather 侧准备（必须）
+### 3.1 BotFather 侧准备（必须）
 
 1) 创建 bot
 - 在 Telegram 找 **BotFather**
@@ -112,7 +101,7 @@ bash start.sh
 
 > 如果 Group Privacy 没关，bot 在群里看不到普通消息，会表现成“经常 typing 但没输出 / 没反应”。
 
-### 4.2 在 OCM 添加主 Agent
+### 3.2 在 OCM 添加主 Agent
 
 进入 **Agents** 页面：
 
@@ -128,14 +117,14 @@ bash start.sh
 
 ---
 
-## 5) 创建 Sub-Agent（最常用）
+## 4) 创建 Sub-Agent（最常用）
 
-### 5.1 为什么 Sub-Agent 要用“新群”
+### 4.1 为什么 Sub-Agent 要用“新群”
 
 - 让每个 Sub-Agent 有自己独立的对话上下文、任务边界
 - 出问题直接在该群排查，不污染主 Agent 的对话
 
-### 5.2 Sub-Agent 创建流程（逐步）
+### 4.2 Sub-Agent 创建流程（逐步）
 
 进入 **Agents** 页面 → 点击 `+ Add Sub-Agent`，按引导做：
 
@@ -166,37 +155,7 @@ 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**：
 
@@ -210,7 +169,7 @@ OCM 也支持 Discord：
 
 ---
 
-## 8) 模型管理（Models 页）
+## 6) 模型管理（Models 页）
 
 进入 **模型**：
 
@@ -222,7 +181,7 @@ OCM 也支持 Discord：
 
 ---
 
-## 9) 认证管理（Auth 页）
+## 7) 认证管理（Auth 页）
 
 进入 **认证**：
 

openclaw-manager.js

@@ -24,7 +24,7 @@ const SCRIPT_DIR = __dirname;
 const MANAGER_CONFIG = path.join(SCRIPT_DIR, 'manager-config.json');
 let PORT = 3333;
 let HOST = '0.0.0.0';
-const APP_VERSION = '0.9.3';
+const APP_VERSION = '0.9.0';
 // --port 参数
 const portIdx = process.argv.indexOf('--port');
 if (portIdx !== -1 && process.argv[portIdx + 1]) PORT = parseInt(process.argv[portIdx + 1]) || 3333;
@@ -315,28 +315,6 @@ ${hasMemory ? initialMemory : '> 暂无初始记录。记忆将通过日常对
 `;
 }
 
-function generateCurrentStateMd() {
-  return `# CURRENT_STATE
-
-_Last updated: TBD Australia/Brisbane_
-
-## In Flight
-- none
-
-## Blocked / Waiting
-- none
-
-## Recently Finished
-- none
-
-## Next
-- none
-
-## Reset Summary
-- No active summary yet.
-`;
-}
-
 // ── 请求解析 ──────────────────────────────────────────────────
 function parseBody(req) {
   return new Promise((resolve, reject) => {
@@ -376,7 +354,6 @@ async function handleApi(req, res, urlObj, body) {
         })(),
         primaryModel: cfg.agents?.defaults?.model?.primary || '未配置',
         platform: process.platform,
-        ocmVersion: APP_VERSION,
       }));
     } catch (e) { res.writeHead(500); res.end(JSON.stringify({ ok: false, error: e.message })); }
     return;
@@ -519,7 +496,6 @@ async function handleApi(req, res, urlObj, body) {
     const agentName = name || agentId;
     await fsp.writeFile(path.join(wsPath, 'SOUL.md'), generateSoulMd(agentName, purpose || '', personality || ''), 'utf8');
     await fsp.writeFile(path.join(wsPath, 'MEMORY.md'), generateMemoryMd(agentName, ''), 'utf8');
-    await fsp.writeFile(path.join(wsPath, 'memory', 'CURRENT_STATE.md'), generateCurrentStateMd(), 'utf8');
     // Create agents/<id>/ runtime directory (required by OpenClaw gateway)
     const agentRuntimeDir = path.join(OPENCLAW_DIR, 'agents', agentId);
     await fsp.mkdir(agentRuntimeDir, { recursive: true });
@@ -529,7 +505,7 @@ async function handleApi(req, res, urlObj, body) {
       ok: true, agentId, workspacePath: wsPath, configBackup: bakPath,
       notes: [
         'Agent created with its own bot token',
-        'Workspace directory created with SOUL.md, MEMORY.md, and memory/CURRENT_STATE.md',
+        'Workspace directory created with SOUL.md and MEMORY.md',
         'Runtime directory created at agents/' + agentId + '/',
         'Configuration updated and backed up',
         'Restart gateway to load new bot: openclaw gateway restart'
@@ -588,7 +564,6 @@ async function handleApi(req, res, urlObj, body) {
     await fsp.mkdir(path.join(wsPath, 'memory'), { recursive: true });
     await fsp.writeFile(path.join(wsPath, 'SOUL.md'), generateSoulMd(name || agentId, purpose || '', personality || ''), 'utf8');
     await fsp.writeFile(path.join(wsPath, 'MEMORY.md'), generateMemoryMd(name || agentId, ''), 'utf8');
-    await fsp.writeFile(path.join(wsPath, 'memory', 'CURRENT_STATE.md'), generateCurrentStateMd(), 'utf8');
 
     const agentRuntimeDir = path.join(OPENCLAW_DIR, 'agents', agentId);
     await fsp.mkdir(agentRuntimeDir, { recursive: true });
@@ -599,7 +574,7 @@ async function handleApi(req, res, urlObj, body) {
       notes: [
         'Discord agent created (single Discord bot)',
         'Channel binding added',
-        'Workspace + runtime directories created (including memory/CURRENT_STATE.md)',
+        'Workspace + runtime directories created',
         'Configuration updated and backed up',
         'Restart gateway to apply: openclaw gateway restart'
       ]
@@ -658,7 +633,6 @@ async function handleApi(req, res, urlObj, body) {
     const name = displayName || agentId;
     await fsp.writeFile(path.join(wsPath, 'SOUL.md'),   generateSoulMd(name, purpose || '', personality || ''), 'utf8');
     await fsp.writeFile(path.join(wsPath, 'MEMORY.md'), generateMemoryMd(name, initialMemory || ''), 'utf8');
-    await fsp.writeFile(path.join(wsPath, 'memory', 'CURRENT_STATE.md'), generateCurrentStateMd(), 'utf8');
 
     const agentRuntimeDir = path.join(OPENCLAW_DIR, 'agents', agentId);
     await fsp.mkdir(agentRuntimeDir, { recursive: true });
@@ -668,7 +642,7 @@ async function handleApi(req, res, urlObj, body) {
     res.end(JSON.stringify({ ok: true, agentId, workspacePath: wsPath, configBackup: bakPath,
       notes: [
         'Discord sub-agent created (thread-only binding)',
-        'Workspace + runtime directories created (including memory/CURRENT_STATE.md)',
+        'Workspace + runtime directories created',
         'Configuration updated and backed up',
         'Restart gateway to apply: openclaw gateway restart'
       ]
@@ -732,7 +706,6 @@ async function handleApi(req, res, urlObj, body) {
     const name = displayName || agentId;
     await fsp.writeFile(path.join(wsPath, 'SOUL.md'),   generateSoulMd(name, purpose, personality), 'utf8');
     await fsp.writeFile(path.join(wsPath, 'MEMORY.md'), generateMemoryMd(name, initialMemory), 'utf8');
-    await fsp.writeFile(path.join(wsPath, 'memory', 'CURRENT_STATE.md'), generateCurrentStateMd(), 'utf8');
     // Create agents/<id>/ runtime directory (required by OpenClaw gateway)
     const agentRuntimeDir = path.join(OPENCLAW_DIR, 'agents', agentId);
     await fsp.mkdir(agentRuntimeDir, { recursive: true });
@@ -741,7 +714,7 @@ async function handleApi(req, res, urlObj, body) {
     res.end(JSON.stringify({ ok: true, agentId, workspacePath: wsPath, configBackup: bakPath,
       notes: [
         'Sub-agent created and shares parent bot',
-        'Workspace and runtime directories created (including memory/CURRENT_STATE.md)',
+        'Workspace and runtime directories created',
         'Configuration updated and backed up',
         'Restart gateway to apply: openclaw gateway restart'
       ],
@@ -2005,7 +1978,7 @@ const MAIN_HTML_BODY = String.raw`
   </div>
   <div class="status-row">
     <div class="dot" id="dot"></div>
-    <span class="status-txt" id="statusTxt"></span>
+    <span class="status-txt" id="statusTxt">连接中...</span>
   </div>
   <button class="lang-toggle" onclick="toggleLang()" id="langToggleBtn">EN</button>
   <div class="menu-wrap">
@@ -2056,16 +2029,6 @@ const MAIN_HTML_BODY = String.raw`
       </div>
     </div>
     <div class="dash-gauges" id="dashGauges"><div class="empty">Loading...</div></div>
-    <div class="card dash-notice">
-      <h3 data-i18n="dash.firstRunTitle">🚀 First-run checklist</h3>
-      <ul class="dash-note-list">
-        <li data-i18n="dash.firstRun1">Confirm OCM is pointed at the correct OpenClaw directory.</li>
-        <li data-i18n="dash.firstRun2">Check this Dashboard first: make sure Gateway is running and the system looks healthy.</li>
-        <li data-i18n="dash.firstRun3">Open Agents / Routing and confirm the bindings you expect are actually there.</li>
-        <li data-i18n="dash.firstRun4">Use the built-in Terminal to run <code>openclaw doctor</code> once so you catch environment/auth issues early.</li>
-        <li data-i18n="dash.firstRun5">Before bigger edits, make a backup or check rollback so recovery is nearby if something goes wrong.</li>
-      </ul>
-    </div>
     <div class="dash-sections">
       <div class="card dash-card" id="dashSystem">
         <h3>🖥️ System Info</h3>
@@ -2211,7 +2174,6 @@ const MAIN_HTML_BODY = String.raw`
       <select id="cliPreset" onchange="onCliPresetSelect()" style="font-size:11px;padding:3px 6px;max-width:180px;background:var(--bg);border:1px solid var(--border);border-radius:6px;color:var(--text)">
         <option value="" data-i18n="cli.presets">── 常用命令 ──</option>
       </select>
-      <button class="btn-secondary" style="font-size:11px;padding:3px 10px" onclick="copyCliCommand()" data-i18n="cli.copy">复制命令</button>
       <button class="btn-secondary" style="font-size:11px;padding:3px 10px" onclick="clearCliOutput()" data-i18n="cli.clear">清空</button>
       <button class="btn-secondary" style="font-size:11px;padding:3px 10px" onclick="toggleCliPanel()" data-i18n="cli.collapse">▼ 收起</button>
     </div>
@@ -2476,12 +2438,6 @@ const I18N = {
     'models.onlyCliHint':'模型下拉仅显示 openclaw models list 返回的模型。',
     'models.modelListErr':'读取 openclaw models list 失败：',
     'models.modelListEmpty':'未从 openclaw models list 解析到模型。请先运行 openclaw onboard 并确认模型可用。',
-    'dash.firstRunTitle':'🚀 首次使用检查清单',
-    'dash.firstRun1':'先确认 OCM 指向的是正确的 OpenClaw 数据目录。',
-    'dash.firstRun2':'先看 Dashboard：确认 Gateway 正在运行，系统状态看起来正常。',
-    'dash.firstRun3':'打开 Agents / Routing，确认你期望的绑定确实已经存在。',
-    'dash.firstRun4':'用内置终端先运行一次 <code>openclaw doctor</code>，尽早发现环境或认证问题。',
-    'dash.firstRun5':'在做较大改动前，先做一次备份或确认回滚入口，出问题时更容易恢复。',
     'dash.noticeTitle':'📌 Telegram 使用说明（重要）',
     'dash.notice1':'OCM 主要面向 Telegram：通过群组绑定 Agent，让每个 Agent 拥有独立 Workspace / SOUL.md / MEMORY.md。',
     'dash.notice2':'请确保你已有基本 OpenClaw 操作经验。OCM 主要负责可视化更新 openclaw.json，方便增删主 Agent 与 Sub-Agent，并支持多条 Agent 树。',
@@ -2513,7 +2469,7 @@ const I18N = {
     'actions.restoreConfirm':'确认将配置恢复为：\\n{filename}\\n\\n当前配置将先被自动备份。继续？',
     'actions.restored':'已恢复 ','actions.restoreFail':'恢复失败: ',
     'actions.setupEmpty':'请填写路径','actions.setupSwitching':'目录已切换，正在刷新...','actions.setupInvalid':'路径无效','actions.setupReqFail':'请求失败: ',
-    'common.loading':'加载中...','common.close':'关闭','status.connecting':'连接中...','status.configReadError':'无法读取配置',
+    'common.loading':'加载中...','common.close':'关闭',
     'btn.save':'保存','btn.delete':'删除','btn.cancel':'取消','btn.add':'添加','btn.remove':'移除',
     'agents.addAgent':'＋ Add Agent','agents.addSub':'＋ Add Sub-Agent','agents.hint':'Add Agent: create a top-level agent (a long-lived role) for a new domain. Add Sub-Agent: create a child under a parent; sub-agents use the parent Telegram bot but have their own workspace + SOUL.md + MEMORY.md, preventing context mixing, improving focus, and saving tokens.',
     'agents.addAgentTitle':'Add Agent (Main Bot)','agents.addSubTitle':'Add Sub-Agent',
@@ -2540,11 +2496,6 @@ const I18N = {
     'guide.sub.discord.s3':'右键该 Thread → <b>Copy Link</b>，粘贴到表单里（OCM 自动解析 <code>threadId</code>）。',
     'guide.sub.discord.warn':'⚠️ 约定：主 Agent 绑定 Channel；Sub-Agent 绑定 Thread。不要把 Sub-Agent 绑到普通 Channel。',
     'wiz.telegramId':'你的 Telegram User ID','wiz.telegramIdHint':'💡 可通过 @userinfobot 获取，填写后自动配置 allowFrom 白名单','wiz.telegramIdPh':'例如: 123456789',
-    'wiz.channel':'渠道',
-    'wiz.discordChannel':'Discord 频道链接/ID',
-    'wiz.discordChannelHint':'建议：右键频道 → Copy Link，粘贴后自动解析 channelId（可选 guildId）。',
-    'wiz.discordThread':'Discord Thread 链接/ID（仅 Thread）',
-    'wiz.discordThreadHint':'建议：在主频道内创建 thread → 右键 thread → Copy Link，粘贴后自动解析 threadId。',
     'agents.empty':'暂无 Agent','agents.main':'主 Agent','agents.bound':'已绑群',
     'agents.saveModel':'保存模型','agents.viewFiles':'查看文件',
     'agents.defaultModel':'使用全局默认','agents.custom':'自定义','agents.noModel':'默认',
@@ -2577,7 +2528,7 @@ const I18N = {
     'ch.peerId':'Peer ID','ch.peerIdHint':'（群组 ID 或用户 ID）','ch.peerIdTip':'留空则匹配所有对应类型的 Peer',
     'ch.submit':'添加绑定',
     'l.sub':'选择运行模式',
-    'cli.open':'⌨️ 终端','cli.title':'⌨️ CLI 终端','cli.copy':'复制命令','cli.clear':'清空','cli.collapse':'▼ 收起',
+    'cli.open':'⌨️ 终端','cli.title':'⌨️ CLI 终端','cli.clear':'清空','cli.collapse':'▼ 收起',
     'cli.ready':'── 终端就绪，等待命令 ──','cli.cleared':'── 已清空 ──',
     'cli.presets':'── 常用命令 ──','cli.builtins':'内置命令','cli.favs':'我的收藏',
     'cli.run':'▶ 执行','cli.stop':'■ 停止','cli.star':'⭐','cli.manage':'管理',
@@ -2616,12 +2567,6 @@ const I18N = {
     'models.onlyCliHint':'Model dropdowns only show IDs returned by openclaw models list.',
     'models.modelListErr':'Failed to load openclaw models list: ',
     'models.modelListEmpty':'No model IDs were parsed from openclaw models list. Run openclaw onboard first.',
-    'dash.firstRunTitle':'🚀 First-run checklist',
-    'dash.firstRun1':'Confirm OCM is pointed at the correct OpenClaw directory.',
-    'dash.firstRun2':'Check Dashboard first: make sure Gateway is running and the system looks healthy.',
-    'dash.firstRun3':'Open Agents / Routing and confirm the bindings you expect are actually there.',
-    'dash.firstRun4':'Use the built-in Terminal to run <code>openclaw doctor</code> once so you catch environment or auth issues early.',
-    'dash.firstRun5':'Before bigger edits, make a backup or check rollback so recovery is nearby if something goes wrong.',
     'dash.noticeTitle':'📌 Telegram Usage Notes (Important)',
     'dash.notice1':'OCM is primarily for Telegram workflows: bind agents to groups so each agent has isolated Workspace / SOUL.md / MEMORY.md.',
     'dash.notice2':'Basic OpenClaw CLI experience is required. OCM focuses on visual openclaw.json updates for easier main-agent/sub-agent management and multiple agent trees.',
@@ -2653,7 +2598,7 @@ const I18N = {
     'actions.restoreConfirm':'Restore config to:\\n{filename}\\n\\nCurrent config will be auto-backed up first. Continue?',
     'actions.restored':'Restored ','actions.restoreFail':'Restore failed: ',
     'actions.setupEmpty':'Please enter a path','actions.setupSwitching':'Directory switched, refreshing...','actions.setupInvalid':'Invalid path','actions.setupReqFail':'Request failed: ',
-    'common.loading':'Loading...','common.close':'Close','status.connecting':'Connecting...','status.configReadError':'Unable to read config',
+    'common.loading':'Loading...','common.close':'Close',
     'btn.save':'Save','btn.delete':'Delete','btn.cancel':'Cancel','btn.add':'Add','btn.remove':'Remove',
     'agents.addAgent':'＋ Add Agent','agents.addSub':'＋ Add Sub-Agent','agents.hint':'Add Agent: create a top-level agent (a long-lived role) for a new domain. Add Sub-Agent: create a child under a parent; sub-agents use the parent Telegram bot but have their own workspace + SOUL.md + MEMORY.md, preventing context mixing, improving focus, and saving tokens.',
     'agents.addAgentTitle':'Add Agent (Main Bot)','agents.addSubTitle':'Add Sub-Agent',
@@ -2680,12 +2625,6 @@ const I18N = {
     'guide.sub.discord.s3':'Right-click the thread → <b>Copy Link</b>, paste into the form (OCM auto-parses the <code>threadId</code>).',
     'guide.sub.discord.warn':'Important: main agents bind to channels; sub-agents bind to threads. Do not bind sub-agents to normal channels.',
     'wiz.telegramId':'Your Telegram User ID','wiz.telegramIdHint':'💡 Get it from @userinfobot — auto-configures allowFrom whitelist','wiz.telegramIdPh':'e.g. 123456789',
-    'wiz.channel':'Channel',
-    'wiz.discordChannel':'Discord channel link/ID',
-    'wiz.discordChannelHint':'Tip: right-click channel → Copy Link. Paste to auto-parse channelId (optional guildId).',
-    'wiz.discordThread':'Discord thread link/ID (thread only)',
-    'wiz.discordThreadHint':'Tip: create a thread under your main channel → Copy Link. Paste to auto-parse threadId.',
-
     'agents.empty':'No Agents','agents.main':'Main Agent','agents.bound':'Bound',
     'agents.saveModel':'Save Model','agents.viewFiles':'View Files',
     'agents.defaultModel':'Use Global Default','agents.custom':'custom','agents.noModel':'Default',
@@ -2718,7 +2657,7 @@ const I18N = {
     'ch.peerId':'Peer ID','ch.peerIdHint':'(Group ID or User ID)','ch.peerIdTip':'Leave blank to match all peers of this type',
     'ch.submit':'Add Binding',
     'l.sub':'Select Mode',
-    'cli.open':'⌨️ Terminal','cli.title':'⌨️ CLI Terminal','cli.copy':'Copy cmd','cli.clear':'Clear','cli.collapse':'▼ Collapse',
+    'cli.open':'⌨️ Terminal','cli.title':'⌨️ CLI Terminal','cli.clear':'Clear','cli.collapse':'▼ Collapse',
     'cli.ready':'── Terminal Ready ──','cli.cleared':'── Cleared ──',
     'cli.presets':'── Presets ──','cli.builtins':'Built-in','cli.favs':'My Favorites',
     'cli.run':'▶ Run','cli.stop':'■ Stop','cli.star':'⭐','cli.manage':'Manage',
@@ -2756,9 +2695,6 @@ const LS = {
 let lang = LS.get('ocm_lang', 'en');
 function t(k) { return I18N[lang][k] || I18N.zh[k] || k; }
 function applyLang() {
-  document.documentElement.lang = lang === 'zh' ? 'zh-CN' : 'en';
-  const st = document.getElementById('statusTxt');
-  if(st && (!st.textContent || st.textContent === '连接中...' || st.textContent === 'Connecting...')) st.textContent = t('status.connecting');
   document.querySelectorAll('[data-i18n]').forEach(el => { el.textContent = t(el.dataset.i18n); });
   document.querySelectorAll('[data-i18n-placeholder]').forEach(el => { el.placeholder = t(el.dataset.i18nPlaceholder); });
   const ltb = document.getElementById('langToggleBtn');
@@ -2827,7 +2763,7 @@ async function checkStatus(){
     if(tv) tv.textContent = 'OCM v'+(r.ocmVersion||'--');
     const vb=document.getElementById('versionBadge'); if(vb) vb.textContent = 'v'+r.version;
     const ov=document.getElementById('ocmVersionBadge'); if(ov) ov.textContent='ocm v'+(r.ocmVersion||'--');
-  }catch{ setDot('err'); document.getElementById('statusTxt').textContent=t('status.configReadError'); }
+  }catch{ setDot('err'); document.getElementById('statusTxt').textContent='无法读取配置'; }
 }
 
 async function loadAll(){
@@ -3717,14 +3653,7 @@ async function deleteAuth(key){
 }
 
 function copyText(txt){
-  navigator.clipboard.writeText(txt).then(()=>toast(lang==='en'?'Copied':'已复制','success')).catch(()=>toast(lang==='en'?'Copy failed':'复制失败','error'));
+  navigator.clipboard.writeText(txt).then(()=>toast('已复制','success')).catch(()=>toast('复制失败','error'));
-}
-
-function copyCliCommand(){
-  const inp=document.getElementById('cliInput');
-  const cmd=(inp&&inp.value?inp.value:'').trim();
-  if(!cmd){ toast(lang==='en'?'Nothing to copy (CLI input is empty)':'没有可复制的命令（输入框为空）','error'); return; }
-  copyText(cmd);
 }
 
 
@@ -3964,8 +3893,8 @@ function runCli(){
   es.addEventListener('done',e=>{
     try{
       const d=JSON.parse(e.data);
-      if(d.code===0) cliAppend('\\n✅ Done (exit 0)\\n','cli-done-ok');
+      if(d.code===0) cliAppend('\\n✅ 完成 (exit 0)\\n','cli-done-ok');
-      else cliAppend('\\n❌ Exit code '+d.code+'\\n','cli-done-err');
+      else cliAppend('\\n❌ 退出码 '+d.code+'\\n','cli-done-err');
     }catch(_){}
     es.close(); cliEvt=null; setCliRunning(false);
   });
@@ -4432,7 +4361,7 @@ document.querySelectorAll('.tab').forEach(t=>{
 (function() {
   LS.del('ocm_mode');
   applyLang();
-  checkStatus().then(() => { loadAll(); setTimeout(() => loadDashboard(), 0); }).catch(e => console.error('Init error:', e));
+  checkStatus().then(() => { loadAll(); loadDashboard(); }).catch(e => console.error('Init error:', e));
   startHealthPolling();
 })();`;
 

package.json

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