@keyou007/agent-bot 0.1.2 → 0.1.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (67) hide show
  1. package/.env.example +3 -1
  2. package/CHANGELOG.md +9 -0
  3. package/README.md +20 -7
  4. package/README.zh.md +20 -7
  5. package/config.example.yaml +1 -0
  6. package/dist/cli/FeishuAppRegistration.js +12 -2
  7. package/dist/cli/FeishuAppRegistration.js.map +1 -1
  8. package/dist/cli/Initializer.js +10 -4
  9. package/dist/cli/Initializer.js.map +1 -1
  10. package/dist/cli/ServerStarter.js +69 -0
  11. package/dist/cli/ServerStarter.js.map +1 -0
  12. package/dist/cli/help.js +6 -2
  13. package/dist/cli/help.js.map +1 -1
  14. package/dist/cli/profile.js +40 -0
  15. package/dist/cli/profile.js.map +1 -0
  16. package/dist/cli.js +40 -56
  17. package/dist/cli.js.map +1 -1
  18. package/dist/config/loadConfig.js +7 -2
  19. package/dist/config/loadConfig.js.map +1 -1
  20. package/dist/config/paths.js +1 -0
  21. package/dist/config/paths.js.map +1 -1
  22. package/dist/config/schema.js +1 -0
  23. package/dist/config/schema.js.map +1 -1
  24. package/dist/feishu/CardRenderer.js +21 -3
  25. package/dist/feishu/CardRenderer.js.map +1 -1
  26. package/dist/feishu/FeishuConnector.js +7 -76
  27. package/dist/feishu/FeishuConnector.js.map +1 -1
  28. package/dist/index.js +13 -5
  29. package/dist/index.js.map +1 -1
  30. package/dist/proxy/ProxySessionController.js +18 -3
  31. package/dist/proxy/ProxySessionController.js.map +1 -1
  32. package/dist/startup/StartupNotifier.js +13 -2
  33. package/dist/startup/StartupNotifier.js.map +1 -1
  34. package/dist/startup/startFeishu.js +1 -1
  35. package/dist/startup/startFeishu.js.map +1 -1
  36. package/dist/supervision/SafeRestartNotifier.js +23 -7
  37. package/dist/supervision/SafeRestartNotifier.js.map +1 -1
  38. package/dist/supervision/SafeRestartScheduler.js +20 -2
  39. package/dist/supervision/SafeRestartScheduler.js.map +1 -1
  40. package/dist/supervision/SupervisorDiagnostics.js +209 -0
  41. package/dist/supervision/SupervisorDiagnostics.js.map +1 -0
  42. package/dist/supervisor.js +47 -12
  43. package/dist/supervisor.js.map +1 -1
  44. package/docs/technical-reference.md +23 -5
  45. package/docs/technical-reference.zh.md +23 -5
  46. package/npm-shrinkwrap.json +2 -2
  47. package/package.json +1 -1
  48. package/skills/agent-bot/SKILL.md +23 -3
  49. package/src/cli/FeishuAppRegistration.ts +14 -1
  50. package/src/cli/Initializer.ts +10 -3
  51. package/src/cli/ServerStarter.ts +106 -0
  52. package/src/cli/help.ts +6 -2
  53. package/src/cli/profile.ts +59 -0
  54. package/src/cli.ts +51 -52
  55. package/src/config/loadConfig.ts +12 -2
  56. package/src/config/paths.ts +1 -0
  57. package/src/config/schema.ts +1 -0
  58. package/src/feishu/CardRenderer.ts +25 -3
  59. package/src/feishu/FeishuConnector.ts +6 -87
  60. package/src/index.ts +17 -5
  61. package/src/proxy/ProxySessionController.ts +18 -3
  62. package/src/startup/StartupNotifier.ts +21 -4
  63. package/src/startup/startFeishu.ts +1 -1
  64. package/src/supervision/SafeRestartNotifier.ts +22 -7
  65. package/src/supervision/SafeRestartScheduler.ts +27 -3
  66. package/src/supervision/SupervisorDiagnostics.ts +268 -0
  67. package/src/supervisor.ts +46 -11
@@ -33,6 +33,8 @@ Agent Bot 是基于 Node.js 22+、ESM 和 TypeScript 的应用,主要组件如
33
33
 
34
34
  默认用户数据根目录为 `~/.agent-bot`,可通过 `AGENT_BOT_HOME` 整体替换。
35
35
 
36
+ CLI 还支持显式指定目录的 Profile。不使用 `--profile` 时,命令使用主 Profile 以及原有的环境变量路径规则。`--profile <目录>` 会为当前命令及其启动的 Supervisor、Worker 固定 `AGENT_BOT_HOME` 和 `AGENT_BOT_CONFIG`,配置文件固定为 `<目录>/config.yaml`。它还会先清除继承的飞书凭据环境变量,再加载所选 Profile 的 `.env`,避免从主 Agent Bot 进程树中启动辅助实例时误用主机器人的凭据。`--profile` 不能和 `--config` 同时使用。其他 Profile 必须在每次命令中显式选择;Agent Bot 不维护按名称注册的 Profile。
37
+
36
38
  | 默认路径 | 内容 |
37
39
  | ------------------------------------ | -------------------- |
38
40
  | `~/.agent-bot/config.yaml` | YAML 主配置 |
@@ -43,9 +45,10 @@ Agent Bot 是基于 Node.js 22+、ESM 和 TypeScript 的应用,主要组件如
43
45
 
44
46
  配置文件优先级:
45
47
 
46
- 1. CLI `--config <路径>`
47
- 2. `AGENT_BOT_CONFIG`
48
- 3. `~/.agent-bot/config.yaml`
48
+ 1. CLI `--profile <目录>` 选择 `<目录>/config.yaml`
49
+ 2. CLI `--config <路径>`
50
+ 3. `AGENT_BOT_CONFIG`
51
+ 4. `<AGENT_BOT_HOME>/config.yaml`,默认为 `~/.agent-bot/config.yaml`
49
52
 
50
53
  默认 `.env` 始终从 Agent Bot 用户目录加载。加载 `.env` 后,YAML 中的 `${NAME}` 会使用进程环境变量展开。
51
54
 
@@ -59,6 +62,7 @@ Agent Bot 是基于 Node.js 22+、ESM 和 TypeScript 的应用,主要组件如
59
62
 
60
63
  - 进程环境变量优先于 `~/.agent-bot/.env`
61
64
  - `FEISHU_APP_ID` 和 `FEISHU_APP_SECRET` 必须同时存在
65
+ - 一键注册还会把授权用户的 `open_id` 保存为 `FEISHU_USER_OPEN_ID`
62
66
  - 除非使用 `--reconfigure-feishu`,完整凭据不会被替换
63
67
  - 缺少凭据或只有一项时会重新创建应用
64
68
  - 新创建的凭据经过 fsync、原子替换写入 `.env`,并在配置权限前读回校验
@@ -74,6 +78,8 @@ Agent Bot 是基于 Node.js 22+、ESM 和 TypeScript 的应用,主要组件如
74
78
 
75
79
  生成的授权链接不包含 App Secret。
76
80
 
81
+ 飞书初始化成功后,CLI 会先释放初始化锁,再通过与 `agent-bot server start` 相同的就绪检查流程启动后台 Supervisor,并等待最多 45 秒,直到 Worker 连接飞书并进入就绪状态。如果当前 Profile 的服务已经运行,不会创建第二个 Supervisor。`--skip-feishu` 会跳过自动启动;`--json` 会把结果写入 `server.status`,不会混入非 JSON 文本。
82
+
77
83
  ## 飞书应用要求
78
84
 
79
85
  基础消息能力依赖以下核心配置:
@@ -107,6 +113,7 @@ Agent Bot 是基于 Node.js 22+、ESM 和 TypeScript 的应用,主要组件如
107
113
  feishu:
108
114
  appId: "${FEISHU_APP_ID}"
109
115
  appSecret: "${FEISHU_APP_SECRET}"
116
+ userOpenId: "${FEISHU_USER_OPEN_ID}"
110
117
 
111
118
  console:
112
119
  enabled: true
@@ -131,7 +138,7 @@ logging:
131
138
  path: "./logs/agent-bot.log"
132
139
  ```
133
140
 
134
- `agent-bot server start` 要求同时配置飞书 `appId` 和 `appSecret`。命令会等待 SDK 的 WebSocket 长连接建立后才报告 Server 就绪;缺少凭据时启动失败并提示先初始化。`agent-bot console` 是明确的纯本地入口,不需要飞书凭据。
141
+ `agent-bot server start` 要求同时配置飞书 `appId` 和 `appSecret`。Worker 启动 SDK 长连接时不读取 SDK 日志或私有连接状态,随后通过发送启动状态卡片检查出站能力。通知通常发往已知私聊和最近活跃的群聊;数据库里尚无已知会话时,改用 `feishu.userOpenId`,按 `open_id` 私聊发送。存在通知目标时,至少一张卡片发送成功后 Server 才报告就绪,单个目标发送失败仍相互隔离。如果既没有已知会话,也没有 `feishu.userOpenId`,启动会跳过出站检查并继续。缺少凭据时仍会启动失败并提示先初始化。`agent-bot console` 是明确的纯本地入口,不需要飞书凭据。
135
142
 
136
143
  必须至少配置一个 Agent,`defaults.agent` 必须指向已配置的 Agent。
137
144
 
@@ -175,7 +182,7 @@ AGENT_BOT=1
175
182
 
176
183
  每个 turn 只有一张进度卡。普通更新最多每两秒一次,关键更新最短间隔 500 毫秒。完成时先把进度卡更新为终态,再单独发送 Markdown 最终回答。
177
184
 
178
- 消息去重后,Agent Bot 会尝试添加 `OnIt` 表情。Turn 成功、失败或取消时分别替换为 `DONE`、`ERROR` 或 `CrossMark`。表情操作失败不会阻塞任务。
185
+ 完成持久化消息去重占位后,Agent Bot 会等待 `OnIt` 表情添加成功,再进行聊天信息持久化、图片下载、队列等待、命令执行或 Runtime 调用。Turn 成功、失败或取消时分别替换为 `DONE`、`ERROR` 或 `CrossMark`。表情操作失败会记录日志,但不会阻塞任务。
179
186
 
180
187
  富文本图片会下载到输入图片缓存,并以 `localImage` 传给 Codex。纯图片消息使用默认 Prompt `请分析这张图片。`。ACP Runtime 不支持图片输入时会明确报错。
181
188
 
@@ -214,6 +221,15 @@ SQLite 保存:
214
221
 
215
222
  `agent-bot server start` 启动后台 supervisor。Worker 意外退出后会自动拉起;连续崩溃时使用 1 到 30 秒的指数退避。
216
223
 
224
+ Supervisor 的崩溃诊断文件按当前 Profile 隔离:
225
+
226
+ - `logs/supervisor.log` 持久记录 Worker PID、退出码、运行时长、重启延迟和诊断文件路径
227
+ - `logs/worker.stderr.log` 保存后台进程原本会丢失的 Node/V8 fatal 输出;两类诊断日志达到 10 MiB 时轮转,保留三个备份
228
+ - `data/last-crash.json` 指向最近一次 Worker 异常退出,带时间戳的 `data/crash-reports/crash-*.json` 保留历史记录
229
+ - Node 能生成报告时,写入 `data/crash-reports/report.*.json`
230
+
231
+ Supervisor、Worker、替换 Supervisor 和 Console Worker 默认启用 Node fatal error 与未捕获异常报告。Node 版本支持时还会排除环境变量和网络接口,避免凭据进入报告。主动重启退出码 `75` 和停止退出码 `76` 不会创建崩溃清单。
232
+
217
233
  安全重启会等待:
218
234
 
219
235
  1. 活动任务完成
@@ -224,6 +240,8 @@ SQLite 保存:
224
240
 
225
241
  首次安全重启状态卡会延迟 3 秒发送,让任务最终回答尽可能先到达;延迟期间的状态变化会合并到首张卡片。该延迟不阻塞调度器轮询,真正关闭前会立即 flush 尚未发送的卡片。
226
242
 
243
+ 等待中的安全重启状态卡底部带有 `Cancel` 操作。回调会携带调度器单调递增的计划 ID,因此旧卡片不会取消较新的重启。取消成功后,所有已发送的状态卡都会原地更新并移除按钮;调度器进入不可逆的正在重启阶段后也不再显示该按钮。
244
+
227
245
  本地控制服务负责修改任务和请求服务重启;只读任务查询直接访问 SQLite。
228
246
 
229
247
  ## 权限模式
@@ -1,12 +1,12 @@
1
1
  {
2
2
  "name": "@keyou007/agent-bot",
3
- "version": "0.1.2",
3
+ "version": "0.1.3",
4
4
  "lockfileVersion": 3,
5
5
  "requires": true,
6
6
  "packages": {
7
7
  "": {
8
8
  "name": "@keyou007/agent-bot",
9
- "version": "0.1.2",
9
+ "version": "0.1.3",
10
10
  "license": "GPL-3.0-only",
11
11
  "dependencies": {
12
12
  "@agentclientprotocol/sdk": "1.2.1",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@keyou007/agent-bot",
3
- "version": "0.1.2",
3
+ "version": "0.1.3",
4
4
  "type": "module",
5
5
  "description": "Using Codex in Lark/Feishu feels just like using native Codex.",
6
6
  "license": "GPL-3.0-only",
@@ -48,10 +48,21 @@ agent-bot init
48
48
 
49
49
  Initialization creates the Agent Bot home, `config.yaml`, `.env`, `data/`, and `logs/` from the bundled examples. If Feishu credentials are absent, it starts Feishu one-click app registration, prints an authorization URL and QR code, waits for the user to approve the request, and stores the returned app ID and secret in `.env`. It then audits the app's currently published tenant permissions, event subscriptions, and callbacks. Core and optional missing items produce separate incremental-configuration URLs so optional approval cannot block core setup.
50
50
 
51
+ After Feishu initialization succeeds, `init` releases its initialization lock and automatically starts the selected profile's server, waiting until it is ready. It does not create another supervisor when that profile is already running. `init --skip-feishu` is the exception: it prepares Console-only files and does not start the server. With `--json`, inspect `server.status` for `started`, `already-running`, or `skipped`.
52
+
51
53
  When running `init` on the user's behalf, relay every exact authorization or incremental-configuration URL and let the user complete it in their own browser. The command waits only for core message receipt and delivery capabilities. Optional capabilities such as group creation, group-title synchronization, reactions, images, and card actions do not block initialization; relay the final affected-feature warnings when they remain unavailable. Neither URL contains the app secret, and the secret itself is never printed.
52
54
 
53
55
  Existing complete Feishu credentials are preserved but still audited and repaired when needed. Missing or incomplete credentials mean app creation did not complete, so a later `init` starts a new registration instead of resuming the previous device code. Once both credentials are durably saved, an interrupted permission audit resumes against the same remote app. `init` also holds a local lock to prevent concurrent registrations. Use `agent-bot init --skip-feishu` only for console-only initialization because it skips both registration and configuration auditing. Use `agent-bot init --reconfigure-feishu` only when the user explicitly wants to replace existing complete credentials. The command respects `AGENT_BOT_HOME`, `AGENT_BOT_CONFIG`, and `--config <path>`. Use `agent-bot init --json` when structured final output helps.
54
56
 
57
+ For an isolated secondary bot, pass its profile directory explicitly on every command:
58
+
59
+ ```powershell
60
+ agent-bot --profile ~/.agent-bot-rescue init
61
+ agent-bot --profile ~/.agent-bot-rescue server status
62
+ ```
63
+
64
+ No `--profile` selects the main profile at `~/.agent-bot` by default. `--profile <directory>` selects that directory's `config.yaml`, `.env`, data, logs, and local control endpoint and propagates the selection to the supervisor and worker. Alternative profiles are not registered by name. Do not combine `--profile` with `--config`.
65
+
55
66
  ## Start with inspection
56
67
 
57
68
  Verify the CLI and current service state before changing anything:
@@ -67,7 +78,7 @@ agent-bot task list
67
78
 
68
79
  Add `--json` to status and list commands when machine-readable output helps. If `agent-bot` is unavailable, report that the CLI is not installed or linked instead of guessing process state.
69
80
 
70
- By default Agent Bot stores user-owned configuration and runtime state in `~/.agent-bot`: config at `~/.agent-bot/config.yaml`, environment variables at `~/.agent-bot/.env`, SQLite state at `~/.agent-bot/data/agent-bot.sqlite`, logs at `~/.agent-bot/logs/agent-bot.log`, and inbound image cache next to the SQLite database. `AGENT_BOT_HOME` changes this root. Use `--config <path>` only when controlling a non-default configuration.
81
+ By default Agent Bot stores user-owned configuration and runtime state in `~/.agent-bot`: config at `~/.agent-bot/config.yaml`, environment variables at `~/.agent-bot/.env`, SQLite state at `~/.agent-bot/data/agent-bot.sqlite`, logs at `~/.agent-bot/logs/agent-bot.log`, and inbound image cache next to the SQLite database. `AGENT_BOT_HOME` changes this root. Prefer `--profile <directory>` when controlling a complete isolated instance; use `--config <path>` only when selecting a non-default configuration without changing the whole profile.
71
82
 
72
83
  ## Manage the service
73
84
 
@@ -80,12 +91,21 @@ agent-bot server restart --reason "reason for restart"
80
91
  agent-bot server stop
81
92
  ```
82
93
 
83
- Treat `server restart` as the normal restart path. It schedules a safe restart and waits for active tasks, pending final-message delivery, and a quiet inbound-message window. The first safe-restart status card is delayed by three seconds so the active task's final response can usually be delivered first; this presentation delay does not postpone scheduler polling.
94
+ Treat `server restart` as the normal restart path. It schedules a safe restart and waits for active tasks, pending final-message delivery, and a quiet inbound-message window. The first safe-restart status card is delayed by three seconds so the active task's final response can usually be delivered first; this presentation delay does not postpone scheduler polling. While the restart is pending, its status card has a bottom `Cancel` button that conditionally cancels that exact schedule and updates the card in place.
84
95
 
85
96
  Use `agent-bot server restart --immediate` only when the user explicitly requests an immediate restart or accepts interruption. Never use `taskkill`, `Stop-Process`, or equivalent commands for routine Agent Bot restart management.
86
97
 
87
98
  `agent-bot console` opens the console UI only when the service is stopped. Do not use `--force` while the service is live unless the user explicitly accepts concurrent state access.
88
99
 
100
+ When a startup card says the Worker exited and the supervisor restarted it, inspect the selected profile's persisted crash evidence before guessing at a cause:
101
+
102
+ - `data/last-crash.json` for PID, exit code, uptime, restart delay, and linked report paths
103
+ - `logs/supervisor.log` for the restart timeline
104
+ - `logs/worker.stderr.log` for Node/V8 fatal output
105
+ - `data/crash-reports/report.*.json` for Node diagnostic reports
106
+
107
+ Normal safe restarts and explicit stops do not overwrite the latest crash record. Every explicit profile keeps its own diagnostic files; use the same `--profile <directory>` selection when correlating service status with those paths.
108
+
89
109
  ## Manage tasks
90
110
 
91
111
  List tasks before resolving a numeric reference because task numbers follow the current list order:
@@ -131,7 +151,7 @@ Messages whose trimmed text starts with `/` are always parsed as Agent Bot comma
131
151
 
132
152
  When a group body has a current task, renaming the Feishu group to `[agent-name] new title` also renames that current task if the prefix matches the task's configured agent. Malformed names, agent mismatches, empty groups, and thread-specific tasks are ignored.
133
153
 
134
- Use `--context <key>` or `--status <status>` to narrow `task list`. Use `--config <path>` before the command when controlling a non-default Agent Bot configuration.
154
+ Use `--context <key>` or `--status <status>` to narrow `task list`. Use `--profile <directory>` before the command when controlling an isolated Agent Bot instance, or `--config <path>` for only a non-default configuration.
135
155
 
136
156
  ## Apply code changes safely
137
157
 
@@ -16,6 +16,7 @@ export interface FeishuAppRegistrationChallenge {
16
16
  export interface FeishuAppCredentials {
17
17
  appId: string;
18
18
  appSecret: string;
19
+ userOpenId?: string;
19
20
  }
20
21
 
21
22
  export interface FeishuAppRegistrationOptions {
@@ -94,7 +95,14 @@ export async function registerFeishuApp(options: FeishuAppRegistrationOptions =
94
95
  if (!errorCode) {
95
96
  const appId = readString(payload, "client_id");
96
97
  const appSecret = readString(payload, "client_secret");
97
- if (appId && appSecret) return { appId, appSecret };
98
+ if (appId && appSecret) {
99
+ const userOpenId = readString(readObject(payload, "user_info"), "open_id");
100
+ return {
101
+ appId,
102
+ appSecret,
103
+ ...(userOpenId ? { userOpenId } : {}),
104
+ };
105
+ }
98
106
  continue;
99
107
  }
100
108
 
@@ -165,6 +173,11 @@ function readString(value: RegistrationPayload, key: string): string {
165
173
  return typeof field === "string" ? field.trim() : "";
166
174
  }
167
175
 
176
+ function readObject(value: RegistrationPayload, key: string): RegistrationPayload {
177
+ const field = value[key];
178
+ return isRecord(field) ? field : {};
179
+ }
180
+
168
181
  function readPositiveInteger(value: RegistrationPayload, key: string): number | undefined {
169
182
  const field = value[key];
170
183
  const parsed = typeof field === "number" ? field : Number(field);
@@ -39,11 +39,13 @@ export interface FeishuCredentialState {
39
39
  status: FeishuCredentialStatus;
40
40
  appId?: string;
41
41
  appSecret?: string;
42
+ userOpenId?: string;
42
43
  }
43
44
 
44
45
  export interface FeishuCredentials {
45
46
  appId: string;
46
47
  appSecret: string;
48
+ userOpenId?: string;
47
49
  }
48
50
 
49
51
  export interface InitializationLock {
@@ -85,17 +87,21 @@ export function readFeishuCredentials(envPath: string, env: NodeJS.ProcessEnv =
85
87
  const fileValues = fs.existsSync(envPath) ? parseDotEnv(fs.readFileSync(envPath, "utf8")) : {};
86
88
  const appId = firstNonBlank(env.FEISHU_APP_ID, fileValues.FEISHU_APP_ID);
87
89
  const appSecret = firstNonBlank(env.FEISHU_APP_SECRET, fileValues.FEISHU_APP_SECRET);
88
- if (appId && appSecret) return { status: "configured", appId, appSecret };
89
- if (appId || appSecret) return { status: "incomplete", appId, appSecret };
90
- return { status: "missing" };
90
+ const userOpenId = firstNonBlank(env.FEISHU_USER_OPEN_ID, fileValues.FEISHU_USER_OPEN_ID);
91
+ const user = userOpenId ? { userOpenId } : {};
92
+ if (appId && appSecret) return { status: "configured", appId, appSecret, ...user };
93
+ if (appId || appSecret) return { status: "incomplete", appId, appSecret, ...user };
94
+ return { status: "missing", ...user };
91
95
  }
92
96
 
93
97
  export function writeFeishuCredentials(envPath: string, credentials: FeishuCredentials): void {
94
98
  assertDotEnvValue("FEISHU_APP_ID", credentials.appId);
95
99
  assertDotEnvValue("FEISHU_APP_SECRET", credentials.appSecret);
100
+ if (credentials.userOpenId) assertDotEnvValue("FEISHU_USER_OPEN_ID", credentials.userOpenId);
96
101
  const original = fs.existsSync(envPath) ? fs.readFileSync(envPath, "utf8") : "";
97
102
  let updated = upsertDotEnvValue(original, "FEISHU_APP_ID", credentials.appId);
98
103
  updated = upsertDotEnvValue(updated, "FEISHU_APP_SECRET", credentials.appSecret);
104
+ updated = upsertDotEnvValue(updated, "FEISHU_USER_OPEN_ID", credentials.userOpenId ?? "");
99
105
 
100
106
  fs.mkdirSync(path.dirname(envPath), { recursive: true });
101
107
  const temporaryPath = `${envPath}.${process.pid}.${Date.now()}.tmp`;
@@ -114,6 +120,7 @@ export function writeFeishuCredentials(envPath: string, credentials: FeishuCrede
114
120
  persisted.status !== "configured"
115
121
  || persisted.appId !== credentials.appId
116
122
  || persisted.appSecret !== credentials.appSecret
123
+ || persisted.userOpenId !== credentials.userOpenId
117
124
  ) {
118
125
  throw new Error("飞书凭据写入后校验失败。");
119
126
  }
@@ -0,0 +1,106 @@
1
+ import { spawn } from "node:child_process";
2
+ import { fileURLToPath } from "node:url";
3
+ import { loadConfig } from "../config/loadConfig.js";
4
+ import type { AppConfig } from "../config/schema.js";
5
+ import { requireServerFeishuTransport } from "../feishu/transport.js";
6
+ import {
7
+ nodeDiagnosticReportArguments,
8
+ prepareCrashReportDirectory,
9
+ resolveSupervisorDiagnosticsPaths,
10
+ } from "../supervision/SupervisorDiagnostics.js";
11
+ import { controlEndpoint } from "./controlProtocol.js";
12
+ import { isServerReachable, isServerRunning } from "./LocalControlClient.js";
13
+
14
+ export interface ServerStartResult {
15
+ status: "started" | "already-running";
16
+ }
17
+
18
+ export type InitializationServerResult =
19
+ | ServerStartResult
20
+ | { status: "skipped"; reason: "feishu-skipped" };
21
+
22
+ export interface ServerStarterDependencies {
23
+ isRunning(endpoint: string): Promise<boolean>;
24
+ isReachable(endpoint: string): Promise<boolean>;
25
+ waitUntilRunning(endpoint: string, timeoutMs: number): Promise<boolean>;
26
+ spawnSupervisor(config: AppConfig): void;
27
+ }
28
+
29
+ const SERVER_START_TIMEOUT_MS = 45_000;
30
+
31
+ interface InitializationServerDependencies {
32
+ loadConfig(configPath?: string): AppConfig;
33
+ startServer(config: AppConfig): Promise<ServerStartResult>;
34
+ }
35
+
36
+ export async function startInitializedServer(
37
+ options: { skipFeishu: boolean; configPath?: string },
38
+ dependencies: InitializationServerDependencies = defaultInitializationDependencies,
39
+ ): Promise<InitializationServerResult> {
40
+ if (options.skipFeishu) {
41
+ return { status: "skipped", reason: "feishu-skipped" };
42
+ }
43
+ return dependencies.startServer(dependencies.loadConfig(options.configPath));
44
+ }
45
+
46
+ export async function startServer(
47
+ config: AppConfig,
48
+ dependencies: ServerStarterDependencies = defaultDependencies,
49
+ ): Promise<ServerStartResult> {
50
+ requireServerFeishuTransport(config.feishu);
51
+ const endpoint = controlEndpoint(config.storage.sqlitePath);
52
+
53
+ if (await dependencies.isRunning(endpoint)) {
54
+ return { status: "already-running" };
55
+ }
56
+ if (await dependencies.isReachable(endpoint)) {
57
+ const running = await dependencies.waitUntilRunning(endpoint, SERVER_START_TIMEOUT_MS);
58
+ if (!running) {
59
+ throw new Error("agent-bot server 已启动,但未能连接飞书机器人。请检查日志。");
60
+ }
61
+ return { status: "started" };
62
+ }
63
+
64
+ dependencies.spawnSupervisor(config);
65
+ const running = await dependencies.waitUntilRunning(endpoint, SERVER_START_TIMEOUT_MS);
66
+ if (!running) {
67
+ throw new Error("已启动 Supervisor,但 server 未在 45 秒内连接飞书机器人。请检查日志。");
68
+ }
69
+ return { status: "started" };
70
+ }
71
+
72
+ const defaultDependencies: ServerStarterDependencies = {
73
+ isRunning: isServerRunning,
74
+ isReachable: isServerReachable,
75
+ waitUntilRunning: waitForServer,
76
+ spawnSupervisor: (config) => {
77
+ const entry = fileURLToPath(new URL("../supervisor.js", import.meta.url));
78
+ const reportDirectory = resolveSupervisorDiagnosticsPaths(config).crashReportDirectory;
79
+ prepareCrashReportDirectory(reportDirectory);
80
+ const child = spawn(process.execPath, [
81
+ ...nodeDiagnosticReportArguments(reportDirectory),
82
+ entry,
83
+ ], {
84
+ cwd: process.cwd(),
85
+ detached: true,
86
+ windowsHide: true,
87
+ stdio: "ignore",
88
+ env: { ...process.env, AGENT_BOT_RESTART_REASON: "通过 agent-bot CLI 启动" },
89
+ });
90
+ child.unref();
91
+ },
92
+ };
93
+
94
+ const defaultInitializationDependencies: InitializationServerDependencies = {
95
+ loadConfig,
96
+ startServer: (config) => startServer(config),
97
+ };
98
+
99
+ async function waitForServer(endpoint: string, timeoutMs: number): Promise<boolean> {
100
+ const deadline = Date.now() + timeoutMs;
101
+ while (Date.now() < deadline) {
102
+ if (await isServerRunning(endpoint)) return true;
103
+ await new Promise((resolve) => setTimeout(resolve, 200));
104
+ }
105
+ return false;
106
+ }
package/src/cli/help.ts CHANGED
@@ -25,7 +25,7 @@ function renderChineseHelp(version: string): string {
25
25
  agent-bot [选项] <命令>
26
26
 
27
27
  常用命令:
28
- init 初始化配置、数据目录和飞书应用
28
+ init 初始化配置和飞书应用,并启动服务
29
29
  console 打开本地 Console
30
30
  server start 在后台启动 Agent Bot
31
31
  server status 查看服务和安全重启状态
@@ -41,6 +41,7 @@ function renderChineseHelp(version: string): string {
41
41
  skills install 安装内置 Skill
42
42
 
43
43
  选项:
44
+ --profile <directory> 使用指定目录中的独立 Profile
44
45
  --config <path> 使用指定配置文件
45
46
  --json 在支持的命令中输出 JSON
46
47
  -h, --help 显示帮助
@@ -48,6 +49,7 @@ function renderChineseHelp(version: string): string {
48
49
 
49
50
  示例:
50
51
  agent-bot init
52
+ agent-bot --profile ~/.agent-bot-rescue init
51
53
  agent-bot server start
52
54
  agent-bot server status
53
55
  agent-bot task list
@@ -63,7 +65,7 @@ Usage:
63
65
  agent-bot [options] <command>
64
66
 
65
67
  Common commands:
66
- init Initialize config, data directories, and the Lark app
68
+ init Initialize the Lark app and start the service
67
69
  console Open the local console
68
70
  server start Start Agent Bot in the background
69
71
  server status Show server and safe-restart status
@@ -79,6 +81,7 @@ Common commands:
79
81
  skills install Install the built-in Skill
80
82
 
81
83
  Options:
84
+ --profile <directory> Use an isolated profile directory
82
85
  --config <path> Use a specific config file
83
86
  --json Print JSON when supported
84
87
  -h, --help Show help
@@ -86,6 +89,7 @@ Options:
86
89
 
87
90
  Examples:
88
91
  agent-bot init
92
+ agent-bot --profile ~/.agent-bot-rescue init
89
93
  agent-bot server start
90
94
  agent-bot server status
91
95
  agent-bot task list
@@ -0,0 +1,59 @@
1
+ import path from "node:path";
2
+ import {
3
+ AGENT_BOT_EXPLICIT_PROFILE_ENV,
4
+ AGENT_BOT_HOME_ENV,
5
+ DEFAULT_CONFIG_FILE,
6
+ resolveUserPath,
7
+ } from "../config/paths.js";
8
+
9
+ export interface ParsedGlobalOptions {
10
+ args: string[];
11
+ configPath?: string;
12
+ profilePath?: string;
13
+ }
14
+
15
+ export interface AppliedProfile {
16
+ homePath: string;
17
+ configPath: string;
18
+ }
19
+
20
+ export function parseGlobalOptions(input: string[]): ParsedGlobalOptions {
21
+ const args = [...input];
22
+ const configPath = removeOption(args, "--config");
23
+ const profilePath = removeOption(args, "--profile");
24
+ if (configPath && profilePath) {
25
+ throw new Error("--profile 和 --config 不能同时使用。Profile 固定使用其目录下的 config.yaml。");
26
+ }
27
+ return {
28
+ args,
29
+ ...(configPath ? { configPath } : {}),
30
+ ...(profilePath ? { profilePath } : {}),
31
+ };
32
+ }
33
+
34
+ export function applyExplicitProfile(
35
+ profilePath: string,
36
+ env: NodeJS.ProcessEnv = process.env,
37
+ baseDirectory = process.cwd(),
38
+ ): AppliedProfile {
39
+ const homePath = resolveUserPath(profilePath, baseDirectory);
40
+ const configPath = path.join(homePath, DEFAULT_CONFIG_FILE);
41
+ env[AGENT_BOT_HOME_ENV] = homePath;
42
+ env.AGENT_BOT_CONFIG = configPath;
43
+ env[AGENT_BOT_EXPLICIT_PROFILE_ENV] = "1";
44
+ delete env.FEISHU_APP_ID;
45
+ delete env.FEISHU_APP_SECRET;
46
+ delete env.FEISHU_USER_OPEN_ID;
47
+ return { homePath, configPath };
48
+ }
49
+
50
+ function removeOption(args: string[], option: string): string | undefined {
51
+ const indexes = args.flatMap((value, index) => value === option ? [index] : []);
52
+ if (indexes.length > 1) throw new Error(`${option} 只能指定一次。`);
53
+ const index = indexes[0];
54
+ if (index === undefined) return undefined;
55
+ const value = args[index + 1];
56
+ if (!value || value.startsWith("--")) throw new Error(`${option} 需要目录或文件路径。`);
57
+ args.splice(index, 2);
58
+ return value;
59
+ }