@keyou007/agent-bot 0.1.11 → 0.1.13-alpha.0

package/.env.example

@@ -1,4 +1,4 @@
-# agent-bot init fills these through Feishu one-click registration.
+# agentbot init fills these through Feishu one-click registration.
 # Leave them blank for console-only mode. When binding an existing app manually,
 # FEISHU_USER_OPEN_ID is the private-chat fallback for startup notifications.
 FEISHU_APP_ID=

package/CHANGELOG.md

@@ -6,6 +6,25 @@ The project follows [Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
+## [0.1.13-alpha.0] - 2026-08-03
+
+- Upgrade existing Profiles during `agentbot init` by filling missing `config.yaml` and `.env` settings, detecting Codex and TraeX versions, offering explicit install or upgrade actions, and requiring an interactive default-Agent selection.
+- Keep the generated Agent list focused on Codex and TraeX while preserving existing custom Agents and user configuration during Profile upgrades.
+- Generalize runtime messages, cards, help, documentation, and package metadata from Codex-specific wording to the selected App Server Agent.
+- Recognize known TraeX code-mode tool-channel failures in completed responses and guide users to switch models with `/model`.
+- Make Alpha the default release channel, with tested Alpha sequencing and explicit stable promotion commands.
+- Publish Alpha packages under npm's `alpha` dist-tag and mark their GitHub releases as prereleases while preserving `latest` for stable versions.
+
+## [0.1.12] - 2026-08-03
+
+- Add a ready-to-use TraeX App Server example to the checked-in and generated default configuration.
+- Rename the configured App Server adapter kind from `codex` to `app-server` while normalizing existing `codex` values during loading, and show the active Agent's display name in progress-card connection and waiting states.
+- Retry `thread/list` with `updated_at` and remember that capability when a compatible App Server such as TraeX rejects Codex's `recency_at` sort extension.
+- Add `agentbot task newgroup <task>` and `agentbot task forkgroup <task>` to create inherited task groups or fork a task's latest completed turn through the running Server, with optional titles, target-Agent and project overrides for NewGroup, and structured JSON output.
+- Register `agentbot` as the primary CLI executable, retain `agent-bot` as a deprecated forwarding entry with a localized warning, and update current documentation and CLI guidance to use the new command.
+- Refresh Windows Machine and User environment variables before initial Supervisor launch, replacement Supervisor launch, and every Worker launch so restarts pick up updated `PATH` and other values while preserving Profile isolation.
+- Extend App Server session lifecycle requests to 60 seconds so slower compatible Agents such as TraeX can complete `thread/start` without producing a late unknown response.
+
 ## [0.1.11] - 2026-08-02
 
 - Retry Feishu messages, replies, and card updates rejected by email-address content auditing with audit-safe text; keep message reactions pending until terminal presentation succeeds while allowing session and queue state to settle after presentation failures.

package/README.md

@@ -4,15 +4,15 @@
 
 # Agent Bot
 
-Use local Codex and ACP agents directly from Feishu.
+Use Codex, TraeX, and compatible ACP agents directly from Feishu.
 
 English | [简体中文](README.zh.md)
 
-Agent Bot runs on your computer and connects a Feishu bot to your local Codex environment. Send a message to start working; the bot updates a progress card while the agent runs and sends the final answer as Markdown.
+Agent Bot runs on your computer and connects a Feishu bot to your local coding agents. Send a message to start working; the bot updates a progress card while the agent runs and sends the final answer as Markdown.
 
 ## What You Can Do
 
-- Use your existing local Codex login from Feishu
+- Use your existing local Codex or TraeX login from Feishu
 - Create, continue, switch, fork, and stop tasks
 - Work with text, images, groups, and threads
 - Queue follow-up Prompts or add instructions while a task is running
@@ -24,34 +24,47 @@ Agent Bot runs on your computer and connects a Feishu bot to your local Codex en
 ### Requirements
 
 - Node.js 22 or later
-- Codex CLI installed and available as `codex`
-- A completed local Codex login
+- At least one supported App Server Agent: Codex or TraeX
+- A completed local login for the Agent you intend to use
 
-Check the login:
+Check the installed Agents and login state:
 
 ```powershell
+codex --version
 codex login status
+traex --version
+traex login status
 ```
 
+You can continue to initialization when either Codex or TraeX is ready. `agentbot init` checks both Agents and can help install or upgrade either one.
+
 ### Install
 
 ```powershell
 npm install --global @keyou007/agent-bot
-agent-bot --version
-agent-bot --help
+agentbot --version
+agentbot --help
+```
+
+To try the current Alpha channel without replacing npm's stable `latest` tag:
+
+```powershell
+npm install --global @keyou007/agent-bot@alpha
 ```
 
-This installs the `agent-bot` command globally. Command-line help, status, progress, prompts, and errors follow the system language for Chinese and English locales; all other locales fall back to English. JSON output remains language-neutral and stable. See the [technical reference](docs/technical-reference.md#development-and-source-installation) to install from source.
+This installs `agentbot` as the primary command. The legacy `agent-bot` command remains available temporarily, prints a deprecation warning, and will be removed in a future release. Command-line help, status, progress, prompts, and errors follow the system language for Chinese and English locales; all other locales fall back to English. JSON output remains language-neutral and stable. See the [technical reference](docs/technical-reference.md#development-and-source-installation) to install from source.
 
 ### Initialize
 
 ```powershell
-agent-bot init
+agentbot init
 ```
 
-Follow the displayed link or scan the QR code to create and authorize the Feishu bot. Initialization prepares `~/.agent-bot`, saves the bot credentials and the authorizing user, checks the required permissions, and starts Agent Bot automatically.
+Initialization detects Codex and TraeX and reports their installed versions. Missing or outdated Agents are summarized once with their exact install or upgrade commands. Enter one or more action numbers separated by commas, enter `all`, or press Enter to skip maintenance. A failed command does not block the remaining initialization steps. After these checks, select the default Agent by number or standard name; when the current default is still available, press Enter to confirm it. Agent Bot saves the selection to `defaults.agent` in `config.yaml` for future tasks.
+
+Then follow the displayed link or scan the QR code to create and authorize the Feishu bot. Initialization prepares `~/.agent-bot`, saves the bot credentials and the authorizing user, checks the required permissions, and starts Agent Bot automatically.
 
-Only a complete app ID and secret saved locally count as a successful bot creation. If initialization is interrupted before both credentials are saved, rerunning `agent-bot init` creates a new bot. If credentials were saved, initialization resumes by auditing that bot's remote permissions and subscriptions.
+Only a complete app ID and secret saved locally count as a successful bot creation. If initialization is interrupted before both credentials are saved, rerunning `agentbot init` creates a new bot. If credentials were saved, initialization resumes by auditing that bot's remote permissions and subscriptions.
 
 The `im:message.group_msg` permission cannot be added through Feishu's one-click configuration. When it is missing, Agent Bot prints a QR code and a direct Developer Console link already filtered to that permission. Add it manually, publish the app version, and complete tenant approval if required. While Agent Bot waits for it to become active, enter `Y` to skip this permission and continue initialization; the final result warns that ordinary group messages which do not mention the bot will be unavailable.
 
@@ -66,12 +79,12 @@ When optional permissions or subscriptions are missing, Agent Bot first shows th
 | `--profile <directory>`| Use an isolated profile directory   |
 | `--config <path>`      | Use a specific configuration file   |
 
-You can rerun `agent-bot init` later to check or complete the bot configuration. If the server is already running, initialization leaves it running.
+After upgrading Agent Bot, rerun `agentbot init` to refresh the Profile. It preserves existing values in `config.yaml` and `.env`, fills settings and environment variables added by the current version, lets you confirm or change the default Agent, and rechecks the Agents and bot configuration. If the server is already running, initialization leaves it running. In a non-interactive terminal, `init` cannot ask for a selection and keeps the already configured default Agent.
 
 To fully reconfigure a Profile, stop its server and select the Profile explicitly:
 
 ```powershell
-agent-bot --profile ~/.agent-bot init --reset
+agentbot --profile ~/.agent-bot init --reset
 ```
 
 Reset moves the active `config.yaml`, `.env`, `data/`, and `logs/` into a new timestamped directory under `.reset-backups`, then initializes clean replacements. Existing backup directories are retained. The old remote Feishu app is not deleted.
@@ -79,10 +92,10 @@ Reset moves the active `config.yaml`, `.env`, `data/`, and `logs/` into a new ti
 ### Start And Stop
 
 ```powershell
-agent-bot server status
+agentbot server status
 ```
 
-`agent-bot init` starts the server automatically. If you stop it later, run `agent-bot server start` to start it again. For local-only use, initialize with `--skip-feishu` and run `agent-bot console` instead.
+`agentbot init` starts the server automatically. If you stop it later, run `agentbot server start` to start it again. For local-only use, initialize with `--skip-feishu` and run `agentbot console` instead.
 
 The `Agent Bot 已启动` startup card shows the version of Agent Bot currently running.
 
@@ -91,7 +104,7 @@ Open Feishu, find the bot, and send a message. Agent Bot automatically creates a
 Stop the service with:
 
 ```powershell
-agent-bot server stop
+agentbot server stop
 ```
 
 ### Update Or Uninstall
@@ -99,15 +112,15 @@ agent-bot server stop
 Stop the running service before replacing or removing the global package:
 
 ```powershell
-agent-bot server stop
+agentbot server stop
 npm install --global @keyou007/agent-bot@latest
-agent-bot server start
+agentbot server start
 ```
 
 To uninstall:
 
 ```powershell
-agent-bot server stop
+agentbot server stop
 npm uninstall --global @keyou007/agent-bot
 ```
 
@@ -118,20 +131,22 @@ Uninstalling the npm package does not delete your data under `~/.agent-bot`.
 ### Service
 
 ```powershell
-agent-bot server status
-agent-bot server start
-agent-bot server stop
-agent-bot server restart
+agentbot server status
+agentbot server start
+agentbot server stop
+agentbot server restart
 ```
 
 `server restart` waits for current work to finish by default. Its status card includes a `Cancel` button while the restart is still waiting. Use `--immediate` only when interruption is acceptable.
 
+On Windows, every Supervisor and Worker launch reloads the latest Machine and User environment variables. Restart the service after changing `PATH` or another system environment variable; the active Profile selection remains isolated.
+
 `server status` shows the Lark App ID used by the running server. Add `--json` to read it from `feishuAppId`.
 
 ### Console
 
 ```powershell
-agent-bot console
+agentbot console
 ```
 
 The Console UI works without Feishu credentials. It will not share task state with a running server unless `--force` is supplied.
@@ -139,14 +154,18 @@ The Console UI works without Feishu credentials. It will not share task state wi
 ### Tasks
 
 ```powershell
-agent-bot task list
-agent-bot task status <task>
-agent-bot task prompt <task> "<prompt>"
-agent-bot task title <task> "<title>"
-agent-bot task stop <task>
+agentbot task list
+agentbot task status <task>
+agentbot task prompt <task> "<prompt>"
+agentbot task newgroup <task> [title] [--agent <name>] [--dir <path> | --nodir]
+agentbot task forkgroup <task> [title]
+agentbot task title <task> "<title>"
+agentbot task stop <task>
 ```
 
-`<task>` can be a number from `task list`, a task ID, or an unambiguous task-ID prefix. Run `agent-bot --help` for all CLI options.
+`<task>` can be a number from `task list`, a task ID, or an unambiguous task-ID prefix. Run `agentbot --help` for all CLI options.
+
+`task newgroup` creates a Feishu group and a new task. By default it inherits the source task's Agent and execution settings. `--agent <standard-name>` selects another configured Agent; the source project shape is still inherited, while the selected Agent uses its own runtime defaults for Provider, model, reasoning effort, and permission mode. `--dir` overrides the project directory and supports `~`; `--nodir` forces a Projectless App Server task. `task forkgroup` forks the source task's latest available completed turn without interrupting an active turn. Both commands require the Server to be running, invite the Profile's saved authorizing user, leave the source chat on its current task, and support `--json`.
 
 ## Feishu Commands
 
@@ -155,7 +174,7 @@ Plain text continues the current task. Messages beginning with `/` are commands.
 | Command                                  | Purpose                                     |
 | ---------------------------------------- | ------------------------------------------- |
 | `/new [title] [--dir <path> \| --nodir]` | Create a task                               |
-| `/sessions [keyword]`                    | Browse available Codex tasks                |
+| `/sessions [keyword]`                    | Browse available App Server tasks           |
 | `/switch [task]`                         | Switch tasks or return to the previous task |
 | `/fork [task]`                           | Create and open a task branch               |
 | `/status [task]`                         | View task progress and results              |
@@ -177,7 +196,7 @@ Plain text continues the current task. Messages beginning with `/` are commands.
 
 Slash commands accept any unique prefix, and compound commands accept registered initialisms: `/sess` runs `/sessions`, `/fg` runs `/forkgroup`, `/ng` runs `/newgroup`, and `/ns` runs `/nosteer`. Exact command names take priority. An ambiguous prefix such as `/s` or `/f` is rejected and reports every matching command.
 
-`/agent`, `/provider`, `/model`, `/thinking`, and `/permissions` use the same execution-settings card when there is something to select. When more than one Agent is configured, the card adds an Agent tab for selecting the default Agent used by future tasks; `/agent` opens that tab, including when the chat has no current task. With only one configured Agent, `/agent` reports the current Agent directly instead. Existing tasks keep their original Agent, and tasks using different Agents run independently. `/agent <name>` remains available for direct selection. `/provider` likewise reports the current Provider directly when no alternative Provider is configured. The other four commands activate their matching tabs and do not accept arguments. A task created without inherited settings uses the default Provider from your Codex configuration.
+`/agent`, `/provider`, `/model`, `/thinking`, and `/permissions` use the same execution-settings card when there is something to select. When more than one Agent is configured, the card adds an Agent tab for selecting the default Agent used by future tasks; `/agent` opens that tab, including when the chat has no current task. With only one configured Agent, `/agent` reports the current Agent directly instead. Existing tasks keep their original Agent, and tasks using different Agents run independently. `/agent <name>` remains available for direct selection. `/provider` likewise reports the current Provider directly when no alternative Provider is configured. The other four commands activate their matching tabs and do not accept arguments. A task created without inherited settings uses the selected Agent's default Provider.
 
 Private chats, group timelines, and threads keep separate current tasks. You can send an image by itself or together with text. While a task is running, plain text adds instructions to the current work; use `/queue` (or `/nosteer`) to always create a later turn.
 
@@ -187,11 +206,11 @@ Inside a thread, `/forkgroup` forks from the thread's original turn until the th
 
 After `/forkgroup` creates the new group, its welcome message shows the forked task's current Provider, model, reasoning effort, and permission type.
 
-`/new` and `/newgroup` accept the same project options. Pass `--dir <cwd>` to override the inherited project directory, or `--nodir` to force a Projectless Codex task; the two options are mutually exclusive. `~`, `~/...`, and `~\...` resolve from the current user's home directory for both commands. `/newgroup` immediately creates and binds the task in the new group while continuing to inherit the current task's Provider, model, reasoning effort, and permission mode without affecting the source task. If there is no current task, Agent Bot uses the selected agent and its runtime defaults. An explicit title becomes both the group suffix and the task title.
+`/new` and `/newgroup` accept the same project options. Pass `--dir <cwd>` to override the inherited project directory, or `--nodir` to force a Projectless App Server task; the two options are mutually exclusive. `~`, `~/...`, and `~\...` resolve from the current user's home directory for both commands. `/newgroup` immediately creates and binds the task in the new group while continuing to inherit the current task's Provider, model, reasoning effort, and permission mode without affecting the source task. If there is no current task, Agent Bot uses the selected agent and its runtime defaults. An explicit title becomes both the group suffix and the task title.
 
-When `/newgroup` omits the title, the task title is `新任务` and the default group name is `[agent] [project dir] 新任务 (mm-dd)`. Projectless groups omit the project segment entirely, using `[agent] title`. When `/forkgroup` omits the title, its task and group name use the same persistent `source title（分支 N）` sequence as `/fork`, without a date suffix. Feishu group names created by `/newgroup` and `/forkgroup` are capped at 60 displayed characters. When a generated name is too long, Agent Bot truncates only the title portion in the group name; the task title itself stays unchanged.
+When `/newgroup` omits the title, both the task title and the group-title portion use `新任务 (mm-dd)`, producing the default group name `[agent] [project dir] 新任务 (mm-dd)`. Projectless groups omit the project segment entirely, using `[agent] title`. When `/forkgroup` omits the title, its task and group name use the same persistent `source title（分支 N）` sequence as `/fork`, without a date suffix. Feishu group names created by `/newgroup` and `/forkgroup` are capped at 60 displayed characters. When a generated name is too long, Agent Bot truncates only the title portion in the group name; the task title itself stays unchanged.
 
-Renaming a bound group to `[agent] [project dir] title` synchronizes only `title` to the current task. The Agent and project-directory prefixes remain group metadata and are never included in the Codex task title. The older `[agent] title` format remains supported.
+Renaming a bound group to `[agent] [project dir] title` synchronizes only `title` to the current task. The Agent and project-directory prefixes remain group metadata and are never included in the task title. The older `[agent] title` format remains supported.
 
 ## Configuration And Data
 
@@ -213,21 +232,21 @@ By default, Agent Bot responds to ordinary messages in groups containing the bot
 Commands without `--profile` use the main profile at `~/.agent-bot`. To run another bot with isolated credentials, configuration, data, logs, and local control endpoint, pass its directory explicitly on every command:
 
 ```powershell
-agent-bot --profile ~/.agent-bot-rescue init
-agent-bot --profile ~/.agent-bot-rescue server start
-agent-bot --profile ~/.agent-bot-rescue server status
+agentbot --profile ~/.agent-bot-rescue init
+agentbot --profile ~/.agent-bot-rescue server start
+agentbot --profile ~/.agent-bot-rescue server status
 ```
 
 Alternative profiles are directory-based and are not registered by name. Each one uses `config.yaml`, `.env`, `data/`, and `logs/` inside the selected directory. `--profile` cannot be combined with `--config`.
 
 ## Troubleshooting
 
-- **The bot does not respond:** run `agent-bot server status` and check `~/.agent-bot/logs/agent-bot.log`.
+- **The bot does not respond:** run `agentbot server status` and check `~/.agent-bot/logs/agent-bot.log`.
 - **The Worker restarted after a Node crash:** check `~/.agent-bot/data/last-crash.json`, `~/.agent-bot/logs/worker.stderr.log`, and `~/.agent-bot/data/crash-reports/`.
-- **Feishu permissions are incomplete:** rerun `agent-bot init` and follow the displayed authorization steps.
-- **Codex cannot start:** run `codex login status` as the same operating-system user that runs Agent Bot.
-- **You only need local testing:** run `agent-bot init --skip-feishu`, then `agent-bot console`.
-- **A safe restart keeps waiting:** inspect active tasks with `agent-bot task list --status running`.
+- **Feishu permissions are incomplete:** rerun `agentbot init` and follow the displayed authorization steps.
+- **An Agent cannot start:** run `codex login status` or `traex login status` as the same operating-system user that runs Agent Bot, then rerun `agentbot init` to check its version.
+- **You only need local testing:** run `agentbot init --skip-feishu`, then `agentbot console`.
+- **A safe restart keeps waiting:** inspect active tasks with `agentbot task list --status running`.
 
 ## More Documentation
 

package/README.zh.md

@@ -4,15 +4,15 @@
 
 # Agent Bot
 
-通过飞书使用本机上的 Codex 和 ACP Agent。
+通过飞书使用本机上的 Codex、TraeX 和兼容 ACP 的 Agent。
 
 [English](README.md) | 简体中文
 
-Agent Bot 运行在你的电脑上，把飞书机器人连接到本机 Codex 环境。发送消息即可开始工作；执行过程中机器人会更新进度卡，完成后发送 Markdown 最终回答。
+Agent Bot 运行在你的电脑上，把飞书机器人连接到本机编程 Agent。发送消息即可开始工作；执行过程中机器人会更新进度卡，完成后发送 Markdown 最终回答。
 
 ## 可以做什么
 
-- 在飞书中使用本机已有的 Codex 登录
+- 在飞书中使用本机已有的 Codex 或 TraeX 登录
 - 创建、继续、切换、分支和停止任务
 - 使用文字、图片、群聊和话题协作
 - 排队后续 Prompt，或在任务运行中追加指令
@@ -24,34 +24,47 @@ Agent Bot 运行在你的电脑上，把飞书机器人连接到本机 Codex 环
 ### 使用前提
 
 - Node.js 22 或更高版本
-- 已安装 Codex CLI，并可直接执行 `codex`
-- 已完成本机 Codex 登录
+- 至少安装一个支持的 App Server Agent：Codex 或 TraeX
+- 已完成准备使用的 Agent 的本机登录
 
-确认登录状态：
+检查已安装的 Agent 和登录状态：
 
 ```powershell
+codex --version
 codex login status
+traex --version
+traex login status
 ```
 
+Codex 或 TraeX 中任意一个准备完成后即可继续初始化。`agentbot init` 会检查两者，并可帮助安装或升级。
+
 ### 安装
 
 ```powershell
 npm install --global @keyou007/agent-bot
-agent-bot --version
-agent-bot --help
+agentbot --version
+agentbot --help
+```
+
+如需试用当前 Alpha 通道，同时不影响 npm 的稳定版 `latest` 标签：
+
+```powershell
+npm install --global @keyou007/agent-bot@alpha
 ```
 
-该命令会全局安装 `agent-bot`。命令行帮助、状态、进度、交互提示和错误会根据系统语言显示中文或英文；其他未支持语言统一回退英文。JSON 输出不做本地化并保持字段稳定。从源码安装的方法见[技术参考](docs/technical-reference.zh.md#开发与源码安装)。
+该命令会把 `agentbot` 安装为主命令。旧的 `agent-bot` 命令暂时保留，运行时会显示弃用警告，并将在后续版本中移除。命令行帮助、状态、进度、交互提示和错误会根据系统语言显示中文或英文；其他未支持语言统一回退英文。JSON 输出不做本地化并保持字段稳定。从源码安装的方法见[技术参考](docs/technical-reference.zh.md#开发与源码安装)。
 
 ### 初始化
 
 ```powershell
-agent-bot init
+agentbot init
 ```
 
-打开命令显示的链接或扫描二维码，完成飞书机器人创建和授权。初始化会准备 `~/.agent-bot`、保存机器人凭据和授权用户、检查所需权限，并自动启动 Agent Bot。
+初始化会检测 Codex 和 TraeX，并显示已安装的版本。未安装或版本较旧的 Agent 会汇总显示对应的安装或升级命令；输入一个或多个操作编号（用逗号分隔）、输入 `all`，或直接回车跳过维护。命令执行失败不会阻塞后续初始化。检查完成后，可输入编号或标准名选择默认 Agent；当前默认值仍可用时，直接回车即可确认。Agent Bot 会把选择保存到 `config.yaml` 的 `defaults.agent`，供后续新任务使用。
+
+然后打开命令显示的链接或扫描二维码，完成飞书机器人创建和授权。初始化会准备 `~/.agent-bot`、保存机器人凭据和授权用户、检查所需权限，并自动启动 Agent Bot。
 
-只有 App ID 和 App Secret 都已保存到本地才视为机器人创建成功。如果初始化在完整凭据保存前中断，再次运行 `agent-bot init` 会创建新机器人；如果凭据已经保存，则会继续检查该机器人的远端权限和订阅。
+只有 App ID 和 App Secret 都已保存到本地才视为机器人创建成功。如果初始化在完整凭据保存前中断，再次运行 `agentbot init` 会创建新机器人；如果凭据已经保存，则会继续检查该机器人的远端权限和订阅。
 
 `im:message.group_msg` 无法通过飞书一键配置新增。缺少该权限时，Agent Bot 会显示二维码，以及已筛选该权限的开发者后台直达链接。请手动新增权限、发布应用版本，并在需要时完成租户管理员审批。Agent Bot 等待权限生效时，可输入 `Y` 跳过该权限并继续初始化；最终结果会提示机器人无法响应未 @ 它的普通群消息。
 
@@ -66,12 +79,12 @@ agent-bot init
 | `--profile <目录>`     | 使用指定目录中的独立 Profile |
 | `--config <路径>`      | 使用指定配置文件          |
 
-之后可以重新运行 `agent-bot init` 检查或补齐机器人配置。如果 Server 已在运行，初始化会保留当前服务。
+升级 Agent Bot 后，可以重新运行 `agentbot init` 刷新 Profile。它会保留现有 `config.yaml` 和 `.env` 中的值，补齐当前版本新增的配置项和环境变量，允许确认或更换默认 Agent，并重新检查 Agent 与机器人配置。如果 Server 已在运行，初始化会保留当前服务。非交互式终端无法询问选择，此时会保留配置中已有的默认 Agent。
 
 如需完整重新配置一个 Profile，请先停止它的 Server，并显式指定 Profile：
 
 ```powershell
-agent-bot --profile ~/.agent-bot init --reset
+agentbot --profile ~/.agent-bot init --reset
 ```
 
 重置会把当前 `config.yaml`、`.env`、`data/` 和 `logs/` 移入 `.reset-backups` 下新的时间戳目录，再创建干净的新文件和目录。已有备份会永久保留，不会被后续重置覆盖或清理。远端旧飞书应用不会被删除。
@@ -79,10 +92,10 @@ agent-bot --profile ~/.agent-bot init --reset
 ### 启动与停止
 
 ```powershell
-agent-bot server status
+agentbot server status
 ```
 
-`agent-bot init` 会自动启动 Server。之后如果手动停止了服务，可执行 `agent-bot server start` 再次启动。仅在本地使用时，请通过 `--skip-feishu` 初始化并运行 `agent-bot console`。
+`agentbot init` 会自动启动 Server。之后如果手动停止了服务，可执行 `agentbot server start` 再次启动。仅在本地使用时，请通过 `--skip-feishu` 初始化并运行 `agentbot console`。
 
 `Agent Bot 已启动` 启动卡片会显示当前正在运行的 Agent Bot 版本。
 
@@ -91,7 +104,7 @@ agent-bot server status
 停止服务：
 
 ```powershell
-agent-bot server stop
+agentbot server stop
 ```
 
 ### 更新或卸载
@@ -99,15 +112,15 @@ agent-bot server stop
 替换或移除全局包前，先停止正在运行的服务：
 
 ```powershell
-agent-bot server stop
+agentbot server stop
 npm install --global @keyou007/agent-bot@latest
-agent-bot server start
+agentbot server start
 ```
 
 卸载：
 
 ```powershell
-agent-bot server stop
+agentbot server stop
 npm uninstall --global @keyou007/agent-bot
 ```
 
@@ -118,20 +131,22 @@ npm uninstall --global @keyou007/agent-bot
 ### 服务管理
 
 ```powershell
-agent-bot server status
-agent-bot server start
-agent-bot server stop
-agent-bot server restart
+agentbot server status
+agentbot server start
+agentbot server stop
+agentbot server restart
 ```
 
 `server restart` 默认等待当前工作完成后再重启；等待期间可通过状态卡片下方的 `Cancel` 按钮取消。只有可接受中断时才使用 `--immediate`。
 
+Windows 下每次启动 Supervisor 或 Worker 都会重新读取最新的系统和用户环境变量。修改 `PATH` 或其他系统环境变量后重启服务即可生效，当前 Profile 选择仍保持隔离。
+
 `server status` 会显示当前运行服务使用的 Lark App ID；添加 `--json` 后可从 `feishuAppId` 字段读取。
 
 ### Console
 
 ```powershell
-agent-bot console
+agentbot console
 ```
 
 Console UI 不需要飞书凭据。除非传入 `--force`，否则不会与正在运行的 Server 共享任务状态。
@@ -139,14 +154,18 @@ Console UI 不需要飞书凭据。除非传入 `--force`，否则不会与正
 ### 任务管理
 
 ```powershell
-agent-bot task list
-agent-bot task status <任务>
-agent-bot task prompt <任务> "<prompt>"
-agent-bot task title <任务> "<标题>"
-agent-bot task stop <任务>
+agentbot task list
+agentbot task status <任务>
+agentbot task prompt <任务> "<prompt>"
+agentbot task newgroup <任务> [标题] [--agent <标准名>] [--dir <路径> | --nodir]
+agentbot task forkgroup <任务> [标题]
+agentbot task title <任务> "<标题>"
+agentbot task stop <任务>
 ```
 
-`<任务>` 可以是 `task list` 中的序号、任务 ID 或唯一的任务 ID 前缀。运行 `agent-bot --help` 可查看完整 CLI 参数。
+`<任务>` 可以是 `task list` 中的序号、任务 ID 或唯一的任务 ID 前缀。运行 `agentbot --help` 可查看完整 CLI 参数。
+
+`task newgroup` 会创建飞书群和新任务。默认继承源任务的 Agent 和运行设置；`--agent <标准名>` 可选择另一个已配置的 Agent，此时仍继承源任务的项目形态，但 Provider、模型、思考强度和权限模式使用目标 Agent 自己的 Runtime 默认值。`--dir` 可覆盖项目目录并支持 `~`，`--nodir` 会强制创建 Projectless App Server 任务。`task forkgroup` 从源任务最新可用的已完成 turn 创建分支，不会中断正在执行的 turn。两个命令都要求 Server 正在运行，邀请 Profile 中保存的授权用户，不会切换源会话的当前任务，并支持 `--json`。
 
 ## 飞书命令
 
@@ -155,7 +174,7 @@ agent-bot task stop <任务>
 | 命令                                    | 作用                       |
 | --------------------------------------- | -------------------------- |
 | `/new [标题] [--dir <路径> \| --nodir]` | 创建任务                   |
-| `/sessions [关键词]`                    | 浏览可用的 Codex 任务      |
+| `/sessions [关键词]`                    | 浏览可用的 App Server 任务 |
 | `/switch [任务]`                        | 切换任务，或返回上一个任务 |
 | `/fork [任务]`                          | 创建并打开任务分支         |
 | `/status [任务]`                        | 查看任务进度和结果         |
@@ -177,7 +196,7 @@ agent-bot task stop <任务>
 
 斜杠命令支持任意唯一前缀，复合命令还支持首字母缩写：`/sess` 等同于 `/sessions`，`/fg` 等同于 `/forkgroup`，`/ng` 等同于 `/newgroup`，`/ns` 等同于 `/nosteer`。完整命令名优先；`/s`、`/f` 等匹配多个命令的前缀会被拒绝，并列出全部候选命令。
 
-`/agent`、`/provider`、`/model`、`/thinking` 和 `/permissions` 在存在可选项时使用同一张运行设置卡片。配置了多个 Agent 时，卡片会增加 Agent tab，用于选择后续新任务使用的默认 Agent；即使当前聊天还没有任务，`/agent` 也能打开该 tab。只配置一个 Agent 时，`/agent` 直接显示当前 Agent，不打开卡片。现有任务仍保持原来的 Agent，使用不同 Agent 的任务可以相互独立地运行。`/agent <名称>` 继续支持直接选择。没有可切换的 Provider 时，`/provider` 同样只显示当前 Provider。其余四个命令激活各自对应的 tab，且不接受参数。没有可继承设置的新任务使用 Codex 配置中的默认 Provider。
+`/agent`、`/provider`、`/model`、`/thinking` 和 `/permissions` 在存在可选项时使用同一张运行设置卡片。配置了多个 Agent 时，卡片会增加 Agent tab，用于选择后续新任务使用的默认 Agent；即使当前聊天还没有任务，`/agent` 也能打开该 tab。只配置一个 Agent 时，`/agent` 直接显示当前 Agent，不打开卡片。现有任务仍保持原来的 Agent，使用不同 Agent 的任务可以相互独立地运行。`/agent <名称>` 继续支持直接选择。没有可切换的 Provider 时，`/provider` 同样只显示当前 Provider。其余四个命令激活各自对应的 tab，且不接受参数。没有可继承设置的新任务使用所选 Agent 的默认 Provider。
 
 私聊、群正文和话题分别维护当前任务。可以单独发送图片，也可以同时发送文字和图片。任务运行中发送普通文字会追加指令；需要确保形成后续 turn 时使用 `/queue`（或 `/nosteer`）。
 
@@ -187,11 +206,11 @@ agent-bot task stop <任务>
 
 `/forkgroup` 创建新群后，群内欢迎消息会显示分支任务当前使用的 Provider、模型、思考强度和权限类型。
 
-`/new` 和 `/newgroup` 支持相同的项目参数：使用 `--dir <cwd>` 覆盖继承的项目目录，或使用 `--nodir` 强制创建 Projectless Codex 任务，二者不能同时使用。两条命令中的 `~`、`~/...` 和 `~\...` 均表示当前用户目录。`/newgroup` 会立即在新群中创建并绑定任务，同时继续继承当前任务的 Provider、模型、思考强度和权限模式，不影响来源任务。来源聊天没有当前任务时，则使用选定 Agent 及其运行时默认设置。显式标题会同时作为群名后缀和任务标题。
+`/new` 和 `/newgroup` 支持相同的项目参数：使用 `--dir <cwd>` 覆盖继承的项目目录，或使用 `--nodir` 强制创建 Projectless App Server 任务，二者不能同时使用。两条命令中的 `~`、`~/...` 和 `~\...` 均表示当前用户目录。`/newgroup` 会立即在新群中创建并绑定任务，同时继续继承当前任务的 Provider、模型、思考强度和权限模式，不影响来源任务。来源聊天没有当前任务时，则使用选定 Agent 及其运行时默认设置。显式标题会同时作为群名后缀和任务标题。
 
-`/newgroup` 省略标题时，任务标题为 `新任务`，默认群名为 `[agent] [project dir] 新任务 (mm-dd)`。Projectless 群会完全省略项目段，群名格式为 `[agent] title`。`/forkgroup` 省略标题时，任务标题和群名都与 `/fork` 一样使用持久递增的 `源标题（分支 N）`，不追加日期。`/newgroup` 和 `/forkgroup` 创建的飞书群名最多显示 60 个字符。生成后的群名过长时，Agent Bot 只截断群名中的标题部分，任务标题本身保持不变。
+`/newgroup` 省略标题时，任务标题和群名中的标题部分统一使用 `新任务 (mm-dd)`，默认群名为 `[agent] [project dir] 新任务 (mm-dd)`。Projectless 群会完全省略项目段，群名格式为 `[agent] title`。`/forkgroup` 省略标题时，任务标题和群名都与 `/fork` 一样使用持久递增的 `源标题（分支 N）`，不追加日期。`/newgroup` 和 `/forkgroup` 创建的飞书群名最多显示 60 个字符。生成后的群名过长时，Agent Bot 只截断群名中的标题部分，任务标题本身保持不变。
 
-把已绑定任务的群改名为 `[agent] [project dir] title` 时，只会把 `title` 同步到当前任务；Agent 和工程目录前缀仅作为群元数据，不会写入 Codex 任务标题。旧的 `[agent] title` 格式仍然兼容。
+把已绑定任务的群改名为 `[agent] [project dir] title` 时，只会把 `title` 同步到当前任务；Agent 和工程目录前缀仅作为群元数据，不会写入任务标题。旧的 `[agent] title` 格式仍然兼容。
 
 ## 配置与数据
 
@@ -213,21 +232,21 @@ Agent Bot 将用户相关文件保存在仓库之外：
 不指定 `--profile` 时使用位于 `~/.agent-bot` 的主 Profile。运行其他相互隔离的机器人时，需要在每次命令中显式指定其目录：
 
 ```powershell
-agent-bot --profile ~/.agent-bot-rescue init
-agent-bot --profile ~/.agent-bot-rescue server start
-agent-bot --profile ~/.agent-bot-rescue server status
+agentbot --profile ~/.agent-bot-rescue init
+agentbot --profile ~/.agent-bot-rescue server start
+agentbot --profile ~/.agent-bot-rescue server status
 ```
 
 其他 Profile 不按名称注册，而是直接使用目录。每个 Profile 都在所选目录内保存自己的 `config.yaml`、`.env`、`data/` 和 `logs/`，飞书凭据与本地控制端点也相互隔离。`--profile` 不能和 `--config` 同时使用。
 
 ## 常见问题
 
-- **机器人没有响应：** 运行 `agent-bot server status`，并查看 `~/.agent-bot/logs/agent-bot.log`
+- **机器人没有响应：** 运行 `agentbot server status`，并查看 `~/.agent-bot/logs/agent-bot.log`
 - **Node 崩溃后 Worker 被自动重启：** 查看 `~/.agent-bot/data/last-crash.json`、`~/.agent-bot/logs/worker.stderr.log` 和 `~/.agent-bot/data/crash-reports/`
-- **飞书权限不完整：** 重新运行 `agent-bot init`，完成显示的授权步骤
-- **Codex 无法启动：** 使用运行 Agent Bot 的同一操作系统用户执行 `codex login status`
-- **只需要本地测试：** 运行 `agent-bot init --skip-feishu`，然后执行 `agent-bot console`
-- **安全重启一直等待：** 使用 `agent-bot task list --status running` 检查活动任务
+- **飞书权限不完整：** 重新运行 `agentbot init`，完成显示的授权步骤
+- **Agent 无法启动：** 使用运行 Agent Bot 的同一操作系统用户执行 `codex login status` 或 `traex login status`，然后重新运行 `agentbot init` 检查版本
+- **只需要本地测试：** 运行 `agentbot init --skip-feishu`，然后执行 `agentbot console`
+- **安全重启一直等待：** 使用 `agentbot task list --status running` 检查活动任务
 
 ## 更多文档
 

package/config.example.yaml

@@ -10,7 +10,7 @@ console:
 
 agents:
   codex:
-    kind: "codex"
+    kind: "app-server"
     title: "Codex"
     command: "codex"
     args:
@@ -21,28 +21,14 @@ agents:
       - "stdio://"
     env: {}
 
-  coco:
-    title: "Coco"
-    command: "coco"
+  traex:
+    kind: "app-server"
+    title: "TraeX"
+    command: "traex"
     args:
-      - "acp"
-      - "serve"
-    env: {}
-
-  coco-yolo:
-    title: "Coco YOLO"
-    command: "coco"
-    args:
-      - "acp"
-      - "serve"
-      - "--yolo"
-    env: {}
-
-  example:
-    title: "Example ACP Agent"
-    command: "node"
-    args:
-      - "./examples/example-acp-agent.js"
+      - "app-server"
+      - "--listen"
+      - "stdio://"
     env: {}
 
 defaults: