evolcore 0.0.43-test.4 → 0.0.43-test.6

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 (186) hide show
  1. package/CHANGELOG.md +93 -0
  2. package/bin/ecmsg.js +437 -91
  3. package/dist/agents/baseagent-availability.js +19 -4
  4. package/dist/agents/baseagent.js +2 -2
  5. package/dist/agents/claude-runner.js +19 -4
  6. package/dist/agents/codex/app-server-client.js +14 -3
  7. package/dist/agents/codex-runner.js +18 -23
  8. package/dist/aun/aid/agentmd.js +25 -0
  9. package/dist/aun/aid/control-aid.js +15 -0
  10. package/dist/aun/aid/identity.js +8 -0
  11. package/dist/aun/aid/ownership-operation.js +12 -3
  12. package/dist/aun/group/invite-service.js +3 -2
  13. package/dist/aun/service-proxy.js +18 -6
  14. package/dist/channels/aun.js +99 -23
  15. package/dist/channels/daemon.js +2 -2
  16. package/dist/cli/agent-create.js +19 -7
  17. package/dist/cli/aid-bind-command.js +3 -0
  18. package/dist/cli/aun-commands.js +19 -4
  19. package/dist/cli/code-stats.js +451 -213
  20. package/dist/cli/ctl-command.js +1 -3
  21. package/dist/cli/daemon-commands.js +42 -4
  22. package/dist/cli/directory.js +3 -1
  23. package/dist/cli/ecmsg-gateway.js +206 -0
  24. package/dist/cli/index.js +6 -0
  25. package/dist/cli/init.js +120 -13
  26. package/dist/cli/provider-command.js +82 -5
  27. package/dist/cli/restart-monitor.js +35 -24
  28. package/dist/cli/stats.js +8 -1
  29. package/dist/cli/task-context.js +41 -1
  30. package/dist/cli/watch-logs.js +6 -4
  31. package/dist/config/boot-log.js +16 -3
  32. package/dist/config/builtin-roles.js +2 -2
  33. package/dist/config/config-manager.js +5 -14
  34. package/dist/config/daemon-services.js +1 -0
  35. package/dist/config/peer-role-resolver.js +6 -6
  36. package/dist/config/provider-identity-migration.js +277 -0
  37. package/dist/config/provider-identity.js +37 -0
  38. package/dist/config/provider-ipc-service.js +40 -3
  39. package/dist/config/provider-local-sync.js +155 -0
  40. package/dist/config/providers-config.js +45 -4
  41. package/dist/config/providers-management.js +242 -76
  42. package/dist/config/providers.js +4 -1
  43. package/dist/config/role-service.js +8 -8
  44. package/dist/config/role-store.js +22 -22
  45. package/dist/config/schema-migration.js +143 -86
  46. package/dist/config/snapshot.js +70 -41
  47. package/dist/core/agent-runtime.js +48 -9
  48. package/dist/core/auth/auth-gateway.js +5 -3
  49. package/dist/core/auth/delegation-diagnostics.js +6 -2
  50. package/dist/core/auth/operation-authorizer.js +3 -1
  51. package/dist/core/auth/operation-catalog.js +6 -4
  52. package/dist/core/baseagent-loader.js +114 -11
  53. package/dist/core/channel-loader.js +36 -13
  54. package/dist/core/channel-runtime.js +112 -42
  55. package/dist/core/command/cli-intent-parser.js +2 -1
  56. package/dist/core/command/command-handler.js +16 -11
  57. package/dist/core/command/menu-handler.js +8 -3
  58. package/dist/core/command/menu-protocol.js +80 -7
  59. package/dist/core/command/provider-menu.js +4 -2
  60. package/dist/core/command/role-menu.js +29 -17
  61. package/dist/core/command/slash-handler.js +52 -16
  62. package/dist/core/daemon-control.js +42 -15
  63. package/dist/core/daemon-lifecycle.js +411 -67
  64. package/dist/core/handoff/dispatcher.js +9 -3
  65. package/dist/core/handoff/runtime.js +139 -45
  66. package/dist/core/handoff/store.js +190 -2
  67. package/dist/core/handoff/types.js +5 -0
  68. package/dist/core/initialization/service.js +7 -6
  69. package/dist/core/ipc-registration.js +5 -4
  70. package/dist/core/lifecycle-notice.js +10 -4
  71. package/dist/core/message/aun-ipc-sender.js +83 -5
  72. package/dist/core/message/message-admission.js +2 -0
  73. package/dist/core/message/message-bridge.js +53 -4
  74. package/dist/core/message/message-queue.js +46 -4
  75. package/dist/core/message/pending-hints.js +4 -10
  76. package/dist/core/message/response-engine.js +33 -25
  77. package/dist/core/message/send-options.js +40 -0
  78. package/dist/core/message/send-routing.js +320 -0
  79. package/dist/core/ownership/owner-resolver.js +112 -8
  80. package/dist/core/permission/ec-command-parser.js +159 -16
  81. package/dist/core/permission/readonly-shell-query.js +66 -7
  82. package/dist/core/permission/tool-error-code.js +13 -1
  83. package/dist/core/permission/tool-policy.js +74 -20
  84. package/dist/core/relation/same-owner-proof.js +131 -0
  85. package/dist/core/session/adapters/claude-session-file-adapter.js +24 -0
  86. package/dist/core/session/adapters/codex-session-file-adapter.js +80 -0
  87. package/dist/core/session/adapters/ecagent-session-file-adapter.js +22 -0
  88. package/dist/core/session/adapters/gemini-session-file-adapter.js +39 -0
  89. package/dist/core/session/session-fs-store.js +164 -3
  90. package/dist/core/session/session-idle-monitor.js +103 -17
  91. package/dist/core/session/session-manager.js +105 -18
  92. package/dist/core/thread/thread-route.js +5 -2
  93. package/dist/directory/owner-directory-admission.js +26 -1
  94. package/dist/directory/owner-directory-cache.js +739 -109
  95. package/dist/directory/owner-directory-markdown.js +146 -36
  96. package/dist/directory/owner-directory-query-operation.js +6 -3
  97. package/dist/directory/owner-directory-scope.js +12 -0
  98. package/dist/directory/owner-directory-search.js +5 -1
  99. package/dist/directory/owner-directory-store.js +28 -0
  100. package/dist/ecweb/basic-settings-service.js +15 -1
  101. package/dist/ecweb/message-context-service.js +2 -2
  102. package/dist/ecweb/providers-service.js +3 -1
  103. package/dist/ecweb/runtime/lifecycle.js +26 -15
  104. package/dist/ecweb/runtime/supervisor.js +120 -51
  105. package/dist/index.js +551 -250
  106. package/dist/paths.js +2 -1
  107. package/dist/proxy/manager.js +40 -17
  108. package/dist/proxy/service-supervisor.js +67 -33
  109. package/dist/response-system/engines/v1/proactive-flow.js +4 -0
  110. package/dist/trigger/application-service.js +4 -1
  111. package/dist/trigger/audit.js +19 -4
  112. package/dist/trigger/authorization.js +14 -5
  113. package/dist/trigger/event-source.js +4 -0
  114. package/dist/trigger/feedback.js +26 -2
  115. package/dist/trigger/history.js +176 -7
  116. package/dist/trigger/manager.js +1 -3
  117. package/dist/trigger/scheduler.js +81 -8
  118. package/dist/trigger/system-definitions.js +2 -2
  119. package/dist/trigger/validation.js +4 -0
  120. package/dist/utils/autostart.js +2 -2
  121. package/dist/utils/cross-platform.js +188 -12
  122. package/dist/utils/host-info.js +11 -8
  123. package/dist/utils/npm-ops.js +48 -0
  124. package/dist/utils/process-introspect.js +64 -1
  125. package/dist/utils/public-suffix.js +5811 -0
  126. package/dist/utils/startup-trace.js +160 -19
  127. package/dist/utils/windows-autostart.js +41 -7
  128. package/ecagent/dist/harness/env/nodejs.js +46 -2
  129. package/kits/docs/aun/ABILITY_CALLING.md +6 -6
  130. package/kits/docs/channels/aun.md +1 -1
  131. package/kits/docs/channels/feishu.md +2 -2
  132. package/kits/docs/context-assembly.md +20 -4
  133. package/kits/docs/evolcore/INDEX.md +5 -3
  134. package/kits/docs/evolcore/agent.md +2 -2
  135. package/kits/docs/evolcore/aid.md +8 -2
  136. package/kits/docs/evolcore/ctl.md +15 -5
  137. package/kits/docs/evolcore/directory.md +48 -15
  138. package/kits/docs/evolcore/group.md +8 -8
  139. package/kits/docs/evolcore/memory-consolidation.md +1 -1
  140. package/kits/docs/evolcore/menu-exec-schema-commands.md +1 -1
  141. package/kits/docs/evolcore/menu-protocol.md +32 -3
  142. package/kits/docs/evolcore/msg.md +38 -30
  143. package/kits/docs/evolcore/provider.md +57 -5
  144. package/kits/docs/evolcore/response.md +2 -2
  145. package/kits/docs/evolcore/thread-chain.md +11 -13
  146. package/kits/docs/evolcore/tool-authorization.md +17 -0
  147. package/kits/docs/evolcore/trigger.md +2 -2
  148. package/kits/docs/identity/ROLE_DETAIL.md +1 -1
  149. package/kits/docs/prompt-loading-architecture.md +30 -20
  150. package/kits/eck_manifest.auxiliary.json +5 -5
  151. package/kits/eck_manifest.json +44 -32
  152. package/kits/eck_manifest.memory.json +18 -18
  153. package/kits/eck_message_manifest.json +3 -3
  154. package/kits/rules/01-overview.md +1 -1
  155. package/kits/rules/06-channel.md +7 -8
  156. package/kits/schemas/_meta.json +7 -1
  157. package/kits/schemas/daemon.schema.1.json +5 -0
  158. package/kits/schemas/daemon.schema.2.json +5 -0
  159. package/kits/schemas/daemon.schema.3.json +2 -1
  160. package/kits/schemas/daemon.schema.4.json +2 -1
  161. package/kits/schemas/daemon.schema.5.json +2 -1
  162. package/kits/schemas/daemon.schema.6.json +1 -1
  163. package/kits/schemas/daemon.schema.7.json +1 -1
  164. package/kits/schemas/daemon.schema.8.json +2 -1
  165. package/kits/schemas/daemon.schema.9.json +2 -1
  166. package/kits/schemas/providers.schema.2.json +74 -0
  167. package/kits/schemas/role-registry.schema.1.json +2 -2
  168. package/kits/schemas/single-session.schema.1.json +1 -1
  169. package/kits/schemas/single-session.schema.2.json +1 -1
  170. package/kits/schemas/single-session.schema.3.json +1 -1
  171. package/kits/skills/aid-ability/SKILL.md +7 -7
  172. package/kits/skills/ec-agent-create/SKILL.md +1 -0
  173. package/kits/skills/ec-group/SKILL.md +8 -5
  174. package/kits/skills/ec-group-collaboration/SKILL.md +7 -7
  175. package/kits/skills/ec-service-proxy/SKILL.md +3 -10
  176. package/kits/skills/ec-trigger/SKILL.md +9 -9
  177. package/kits/skills/ec-trigger/references/examples.md +1 -1
  178. package/kits/skills/thread-ops/SKILL.md +10 -10
  179. package/kits/templates/system-fragments/channel.md +5 -5
  180. package/kits/templates/system-fragments/commands.md +7 -6
  181. package/kits/templates/system-fragments/directory-contacts.md +10 -3
  182. package/kits/templates/system-fragments/personal-assistant.md +22 -3
  183. package/kits/templates/system-fragments/reply.md +48 -28
  184. package/kits/templates/system-fragments/session.md +3 -10
  185. package/kits/templates/system-fragments/thread.md +5 -5
  186. package/package.json +4 -4
package/bin/ecmsg.js CHANGED
@@ -1,26 +1,30 @@
1
1
  #!/usr/bin/env node
2
2
  /**
3
- * `ecmsg` —— `ec msg` 的轻量等价入口。
3
+ * `ecmsg` —— 统一发送网关。
4
4
  *
5
- * 动机:`ec msg send` 单次约 1.4s,其中 95% 是 CLI 模块图加载
6
- * (agent-delegation 单模块 382ms、task-context 429ms、aun-commands 更重)。
7
- * daemon 侧本来就自己解析 argv(aun-ipc-sender 调 resolveManagedSendArgv),
8
- * CLI 只负责透传,所以这条命令不需要那套模块。
5
+ * 设计依据:`docs/send-routing/unified-send-routing-plan.md`
9
6
  *
10
- * 语义:`ecmsg <args...>` ≡ `ec msg <args...>`。例如
11
- * ecmsg send <from> <to> --content 'hi' ≡ ec msg send <from> <to> --content 'hi'
7
+ * 职责边界(第一期):
8
+ * - 只做**路由**:解析目标三元组、判跨话题、决定复查与加密,然后分派给
9
+ * 现有的内部发送通道。
10
+ * - 不改写任何内部通道的实现。`ec msg send` / `ec group send` / `ec ctl send`
11
+ * 全部保持原状可用。
12
12
  *
13
- * 为什么必须走 ec-command-parser 归一而不是自己拼字符串:委托审批按「规范化
14
- * argv 的 sha256」arm(codex-runner 的 armApprovedDelegationCommand)。`ecmsg`
15
- * 必须归一到 `['ec','msg',...]`,才能与策略层 arm 的哈希对上;否则 daemon 返回
16
- * INVALID_DELEGATION,且会绕过复合命令拦截与会话身份绑定,成为冒充发送的后门。
13
+ * 为什么必须有这一层:
14
+ * 模型面对三种写法时必须先判断"用哪种",判断错就失败。网关把判断收敛为一
15
+ * 次确定性解析,并把"跨话题才要复查""同话题不许建复查""加密看对端是否 AUN"
16
+ * 这些条件约束全部在参数层消化,不下放给模型记规则。
17
17
  *
18
- * 性能约束:本文件只允许 import node 内建模块 + ec-command-parser(纯函数,
19
- * 实测 8ms)。**不要** import agent-delegation.js(382ms)——哈希算法在下面
20
- * 内联实现,与 hashDelegatedCommandArgv 逐字节一致,改动时两处必须同步。
18
+ * 委托哈希约束(关键):
19
+ * 审批按「规范化 argv 的 sha256」arm(codex-runner 的
20
+ * armApprovedDelegationCommand),而 `ec-command-parser` 把 `ecmsg` 归一为
21
+ * `['ec','msg',...]`。网关必须用归一化后的 argv 计算哈希,否则 daemon 侧
22
+ * 算不出匹配的 arm,必然 INVALID_DELEGATION。
23
+ *
24
+ * 本文件只负责 IO:读环境、加载 dist 模块、IPC、渲染回执。
25
+ * 参数解析与下游 argv 构造在 `dist/cli/ecmsg-gateway.js`(纯函数,可单测)。
21
26
  */
22
27
  import net from 'node:net';
23
- import fs from 'node:fs';
24
28
  import path from 'node:path';
25
29
  import crypto from 'node:crypto';
26
30
  import { fileURLToPath, pathToFileURL } from 'node:url';
@@ -33,27 +37,51 @@ const ENV_CODEX_SESSION_TOKEN = 'EVOLCORE_CODEX_SESSION_TOKEN';
33
37
  const ENV_TASK_RUNTIME_CONTEXT = 'EVOLCORE_TASK_RUNTIME_CONTEXT';
34
38
  const ENV_SESSION_ID = 'EVOLCORE_SESSION_ID';
35
39
  const ENV_EXECUTION_SPEC = 'EVOLCORE_DELEGATED_EXECUTION_SPEC';
36
- /** 与 src/product.ts 的 MAIN_CLI_BIN 一致。 */
37
40
  const MAIN_CLI_BIN = 'ec';
38
41
 
39
- function fail(message) {
40
- process.stderr.write(`❌ ${message}\n`);
41
- process.exit(1);
42
- }
42
+ const HELP = `用法: ecmsg send '<正文>' [选项]
43
+ ecmsg send '<正文>' --thread <话题id>
44
+ ecmsg send '<正文>' --to <对端ID>
45
+
46
+ 发送目标(三选一,优先级从高到低):
47
+ (省略) 回复当前会话的对端/群
48
+ --thread <话题id> 发到指定话题;只接受 thread-… 或 main:<aidA>:<aidB>
49
+ --to <对端ID> 发到指定对端(群 AID 或对方 AID,按本地关系判定类型)
50
+ --from <本端AID> 可省略;出现时必须等于当前会话本端(--self 同义)
51
+
52
+ 复查:
53
+ 跨话题(对端或话题与会话不同)自动创建复查 Trigger,默认 20m;
54
+ --check-every <时长> 自定义复查周期(5m/30m/2h/1d)
55
+ 同话题永不创建复查;此时传 --check-every 只在回执里说明,不报错。
56
+
57
+ 加密:
58
+ --encrypt yes|no|auto 默认 auto:被对端消息触发时跟随该消息,否则明文
59
+ 只有目标对端在 AUN 网络上才能加密;非 AUN 目标用 yes 会被拒绝。
60
+
61
+ 正文来源:
62
+ '<正文>' 位置参数
63
+ --text-from-file <path> 从文件读取
64
+ --file <path> 附件(可配 --as image|video|voice|file、--text 说明)
65
+ --link <url> [--title T] 链接卡片
66
+ --payload '<json>' 自定义 payload
67
+
68
+ @提及(仅群聊;私聊带 --mention 会被拒绝):
69
+ --mention '<aid1>,<aid2>' @指定成员,逗号分隔
70
+ --mention-all @所有人
71
+
72
+ 其它:
73
+ --format json 输出 JSON 回执
74
+ --help 显示本帮助
75
+
76
+ 示例:
77
+ ecmsg send '收到,稍后回你'
78
+ ecmsg send '问题已记录' --thread thread-1793851439746-7477-6351
79
+ ecmsg send '进度如何' --to wang.agentid.pub --check-every 10m
80
+ ecmsg send '报告在这里' --file ./report.md --as file
81
+ `;
82
+
83
+ // ── 委托哈希(与 agent-delegation.ts 逐字节一致,改动时两处必须同步) ──
43
84
 
44
- const HELP = [
45
- '用法: ecmsg <msg 子命令及参数>',
46
- ' ecmsg 等价于 ec msg,参数原样透传:',
47
- '',
48
- " ecmsg send <from> <to> --content '正文'",
49
- ' ecmsg send <from> <to> --file <path>',
50
- ' ecmsg history <from> <to> --limit 20',
51
- '',
52
- '非托管环境请直接使用 ec msg。',
53
- '',
54
- ].join('\n');
55
-
56
- /** 与 hashDelegatedCommandSpec 一致:v1 + 直接序列化原对象(顺序敏感,不可重排)。 */
57
85
  function hashExecutionSpec(spec) {
58
86
  if (!spec || typeof spec !== 'object') return undefined;
59
87
  const values = [
@@ -77,10 +105,6 @@ function hashExecutionSpec(spec) {
77
105
  .digest('hex');
78
106
  }
79
107
 
80
- /**
81
- * 与 src/core/auth/agent-delegation.ts 的 hashDelegatedCommandArgv 逐字节一致。
82
- * v1 无执行规格;v2 绑定执行规格(argv 必须与之相同)。
83
- */
84
108
  function hashDelegatedCommandArgv(argv, executionSpec) {
85
109
  if (!Array.isArray(argv) || argv.length === 0) return undefined;
86
110
  if (argv.some(value => typeof value !== 'string' || value.includes('\0'))) return undefined;
@@ -94,7 +118,7 @@ function hashDelegatedCommandArgv(argv, executionSpec) {
94
118
  .digest('hex');
95
119
  }
96
120
 
97
- /** 读执行规格:仅在 argv 完全匹配当前命令时才生效(同 readDelegatedExecutionSpec)。 */
121
+ /** 读执行规格:仅在 argv 完全匹配当前命令时才生效。 */
98
122
  function readDelegatedExecutionSpec(normalizedArgv, env) {
99
123
  const raw = env[ENV_EXECUTION_SPEC]?.trim();
100
124
  if (!raw || raw.length > 16 * 1024) return undefined;
@@ -109,19 +133,8 @@ function readDelegatedExecutionSpec(normalizedArgv, env) {
109
133
  return spec;
110
134
  }
111
135
 
112
- /**
113
- * 复用 dist/paths.js 的端点解析(实测 7ms)。
114
- *
115
- * 不要在这里手写管道名:root 的规范化规则(大小写、尾分隔符、canonical 变体)
116
- * 一旦漂移,就会连不上 daemon。用官方实现是唯一可靠做法。
117
- */
118
- async function resolveSocketPath() {
119
- const pathsUrl = pathToFileURL(path.join(repoRoot, 'dist', 'paths.js')).href;
120
- const { resolvePaths } = await import(pathsUrl);
121
- return resolvePaths().socket;
122
- }
136
+ // ── daemon IPC ──
123
137
 
124
- /** 一次请求一个连接:与 src/ipc.ts 的 ipcQueryOnce 同协议(单行 JSON + \n)。 */
125
138
  function queryDaemonOnce(socketPath, payload, timeoutMs = 120_000) {
126
139
  return new Promise(resolve => {
127
140
  let settled = false;
@@ -131,7 +144,7 @@ function queryDaemonOnce(socketPath, payload, timeoutMs = 120_000) {
131
144
  if (settled) return;
132
145
  settled = true;
133
146
  if (timer) clearTimeout(timer);
134
- try { socket.destroy(); } catch {}
147
+ try { socket.destroy(); } catch { /* ignore */ }
135
148
  resolve(value);
136
149
  };
137
150
  const socket = net.createConnection(socketPath);
@@ -148,82 +161,415 @@ function queryDaemonOnce(socketPath, payload, timeoutMs = 120_000) {
148
161
  });
149
162
  }
150
163
 
164
+ const distUrl = relative => pathToFileURL(path.join(repoRoot, 'dist', relative)).href;
165
+ const BUILD_HINT = 'ecmsg 需要已构建的 dist,请先 npm run build';
166
+
167
+ async function loadDist(relative) {
168
+ try {
169
+ return await import(distUrl(relative));
170
+ } catch {
171
+ return undefined;
172
+ }
173
+ }
174
+
175
+ /**
176
+ * 判定 `--to` 的目标是私聊还是群。
177
+ *
178
+ * AID 的字面形态**从来不是证据**(`aun/group/identity.ts` 的既定原则:
179
+ * 数字 base 也可能是人,`g-` 前缀不是保留给群的)。依据按可信度排序:
180
+ *
181
+ * 1. 目标就是当前会话对端 —— 路由上下文本身就是证据
182
+ * 2. 本地关系记录的 targetKind / 验签通过的 agent.md type
183
+ * 3. 兜底私聊 —— 群关系必然在本地留痕(不是成员发不了),查不到就不是群
184
+ *
185
+ * 第 3 条同时覆盖"首次联系一个人":这时关系记录还不存在,按私聊发出,
186
+ * 会话随首条消息建立。
187
+ */
188
+ async function resolveTargetPeerKind(runtime, targetId) {
189
+ const currentKind = runtime.chatType === 'group' ? 'group' : 'private';
190
+ if (runtime.channel !== 'aun') return currentKind;
191
+
192
+ const normalize = value => String(value ?? '').trim().replace(/^@/, '').toLowerCase();
193
+ const currentPeerId = currentPeerIdOf(runtime);
194
+ if (normalize(targetId) === normalize(currentPeerId)) return currentKind;
195
+
196
+ const peerIdentity = await loadDist('core/relation/peer-identity.js');
197
+ try {
198
+ const local = peerIdentity?.readAunPeerKind?.(runtime.selfAid, targetId)?.kind;
199
+ if (local === 'private' || local === 'group') return local;
200
+ } catch { /* 本地证据不可用不算错误,继续往下判 */ }
201
+ try {
202
+ const remote = await peerIdentity?.resolveAunPeerKind?.(runtime.selfAid, targetId);
203
+ if (remote?.kind === 'private' || remote?.kind === 'group') return remote.kind;
204
+ } catch { /* 网络不可用时不阻塞发送,按私聊兜底 */ }
205
+ return 'private';
206
+ }
207
+
208
+ // ── 当前对端 ──
209
+
210
+ /**
211
+ * 当前会话对端的原生 ID。
212
+ *
213
+ * 群会话里 `runtime.peerId` 是发言人(入站消息的 userId),不是群;群 ID 在
214
+ * `peerKey`(`aun#<群AID>`)里。私聊的 peerId 才是对端。优先取 peerKey:它与授权层
215
+ * 判定「当前关系」用的是同一个字段,trigger / handoff 来源的会话也由它携带。
216
+ * peerKey 缺失时才回落:群用 channelId,私聊用 peerId。
217
+ */
218
+ function currentPeerIdOf(runtime) {
219
+ const key = typeof runtime.peerKey === 'string' ? runtime.peerKey : '';
220
+ const idx = key.indexOf('#');
221
+ if (idx > 0) {
222
+ try {
223
+ const id = decodeURIComponent(key.slice(idx + 1));
224
+ if (id) return id;
225
+ } catch { /* peerKey 格式异常:按缺失处理,走下面的回落 */ }
226
+ }
227
+ return runtime.chatType === 'group'
228
+ ? (runtime.channelId ?? '')
229
+ : (runtime.peerId ?? runtime.channelId ?? '');
230
+ }
231
+
232
+ // ── 错误输出 ──
233
+
234
+ let jsonOutput = false;
235
+
236
+ function fail(message, code, extra = {}) {
237
+ if (jsonOutput) {
238
+ process.stdout.write(`${JSON.stringify({ ok: false, code: code ?? 'ECMSG_FAILED', error: message, ...extra })}\n`);
239
+ } else {
240
+ // 错误码在文本模式下也要可见:排查时靠它区分"参数写错"和"被权限拒绝"。
241
+ process.stderr.write(`❌ ${message}${code ? ` [${code}]` : ''}\n`);
242
+ if (extra.hint) process.stderr.write(` ${extra.hint}\n`);
243
+ }
244
+ process.exit(1);
245
+ }
246
+
247
+ /** `--format json` 的预扫描:参数解析失败时也要按 JSON 报错,所以先看一遍。 */
248
+ function wantsJsonOutput(args) {
249
+ for (let index = 0; index < args.length; index++) {
250
+ const token = args[index];
251
+ if (token === '--') return false;
252
+ if (token === '--format') return args[index + 1] === 'json';
253
+ if (token.startsWith('--format=')) return token.slice('--format='.length) === 'json';
254
+ }
255
+ return false;
256
+ }
257
+
258
+ // ── 主流程 ──
259
+
151
260
  async function main() {
152
- const args = process.argv.slice(2);
153
- if (args.length === 0 || args.includes('--help') || args.includes('-h')) {
261
+ const argv = process.argv.slice(2);
262
+ if (argv.length === 0) { process.stdout.write(HELP); return; }
263
+ if (argv[0] === '--help' || argv[0] === '-h' || argv[0] === 'help') {
154
264
  process.stdout.write(HELP);
155
265
  return;
156
266
  }
157
267
 
268
+ const sub = argv[0];
269
+ if (sub !== 'send') {
270
+ fail(`ecmsg 目前只支持 send(收到 ${sub})`, 'NOT_IMPLEMENTED',
271
+ { hint: sub === 'history' ? '查看历史请用 ec msg history' : '用 --help 查看发送用法' });
272
+ }
273
+
274
+ const routing = await loadDist('core/message/send-routing.js');
275
+ const gateway = await loadDist('cli/ecmsg-gateway.js');
276
+ if (!routing || !gateway) fail(BUILD_HINT, 'BUILD_REQUIRED');
277
+
278
+ jsonOutput = wantsJsonOutput(argv.slice(1));
279
+ const parsed = gateway.parseGatewayArgs(argv.slice(1));
280
+ if (!parsed.ok) fail(parsed.error, 'INVALID_ARGUMENT');
281
+ const { route: routeOpts, passthrough, text } = parsed;
282
+ if (routeOpts.help) { process.stdout.write(HELP); return; }
283
+ jsonOutput = jsonOutput || routeOpts.format === 'json';
284
+
158
285
  const sessionId = process.env[ENV_SESSION_ID]?.trim();
159
286
  const delegationToken = process.env[ENV_DELEGATION_TOKEN]?.trim()
160
287
  || process.env[ENV_CODEX_SESSION_TOKEN]?.trim();
161
- if (!sessionId) fail('ecmsg 只能在托管会话内使用(缺少 EVOLCORE_SESSION_ID)。宿主终端请用 ec msg。');
162
- if (!delegationToken) fail('ecmsg 需要会话委托凭证(缺少 EVOLCORE_DELEGATION_TOKEN)。请改用 ec msg。');
163
-
164
- // 归一化:['ecmsg','send','A','B'] -> ['ec','msg','send','A','B']
165
- const parserUrl = pathToFileURL(path.join(repoRoot, 'dist', 'core', 'permission', 'ec-command-parser.js')).href;
166
- let normalizeEvolcoreCommandArgv;
167
- try {
168
- ({ normalizeEvolcoreCommandArgv } = await import(parserUrl));
169
- } catch {
170
- fail('ecmsg 需要已构建的 dist。请先 npm run build,或改用 ec msg。');
171
- }
172
- const normalizedArgv = normalizeEvolcoreCommandArgv(['ecmsg', ...args]);
173
- if (normalizedArgv[0] !== MAIN_CLI_BIN || normalizedArgv[1] !== 'msg') {
174
- fail(`无法把参数规范化为 ec msg:${JSON.stringify(normalizedArgv.slice(0, 4))}`);
288
+ if (!sessionId) {
289
+ fail('ecmsg 只能在 EvolCore 托管会话内使用(缺少 EVOLCORE_SESSION_ID)。宿主终端请用 ec msg send。',
290
+ 'NO_SESSION');
175
291
  }
292
+ if (!delegationToken) fail('ecmsg 需要会话委托凭证(缺少 EVOLCORE_DELEGATION_TOKEN)。', 'DELEGATION_REQUIRED');
176
293
 
177
- const executionSpec = readDelegatedExecutionSpec(normalizedArgv, process.env);
178
- const delegationCommandHash = hashDelegatedCommandArgv(normalizedArgv, executionSpec);
179
-
180
- // daemon 按 resolveManagedSendArgv(params.argv) 解析,argv[0] 必须是 'msg'。
181
- const daemonArgv = normalizedArgv.slice(1);
182
-
183
- const runtimeCtx = (() => {
294
+ const runtime = (() => {
184
295
  const raw = process.env[ENV_TASK_RUNTIME_CONTEXT];
185
296
  if (!raw) return undefined;
186
297
  try { return JSON.parse(raw); } catch { return undefined; }
187
298
  })();
299
+ if (!runtime?.selfAid || !runtime?.channel || !runtime?.chatType) {
300
+ fail('运行时上下文不完整(缺少 selfAid/channel/chatType),无法确定本端与对端',
301
+ 'CONTEXT_INCOMPLETE');
302
+ }
303
+
304
+ // 空字符串也算"有正文"会把空消息推给下游;这里按去空白后的内容判断。
305
+ const hasBody = text.some(part => part.trim().length > 0)
306
+ || passthrough.some(flag => gateway.BODY_FLAGS.has(flag));
307
+ if (!hasBody) fail('缺少正文', 'INVALID_ARGUMENT', { hint: "例:ecmsg send '收到'" });
308
+
309
+ // 话题索引:--thread 是独立话题、或 --to 需要判断"是不是首次联系"时才真读盘,
310
+ // 其余情况零 IO。
311
+ const deps = {};
312
+
313
+ // --to 的目标类型:下游按它选 msg send / group send,必须解析而不是沿用
314
+ // 当前会话的类型——否则"在私聊会话里给群发"会走成私聊,"在群会话里给个人发"
315
+ // 会走成群消息。
316
+ if (routeOpts.to !== undefined && String(routeOpts.to).trim()) {
317
+ const peerKind = await resolveTargetPeerKind(runtime, String(routeOpts.to).trim());
318
+ deps.resolveTarget = id => ({ channelType: runtime.channel, peerKind, id });
319
+ }
320
+ // `--thread main:<a>:<b>` 的对端类型:主话题 id 里只有两个 AID,群的主话题同样写成
321
+ // main:<self>:<群AID>。类型按关系证据解析(与 --to 同一套),再同步注入给纯函数;
322
+ // 否则网关会把群主话题当私聊,下游走 msg scope 被判 TOPIC_NOT_FOUND。
323
+ if (typeof routeOpts.thread === 'string' && routeOpts.thread.trim()) {
324
+ const topicIds = await loadDist('core/thread/topic-id.js');
325
+ const threadValue = routeOpts.thread.trim();
326
+ const mainPeer = topicIds?.isMainTopicId?.(threadValue)
327
+ ? topicIds.mainTopicPeer(threadValue, runtime.selfAid)
328
+ : undefined;
329
+ if (mainPeer) {
330
+ const mainPeerKind = await resolveTargetPeerKind(runtime, mainPeer);
331
+ deps.resolvePeerKind = () => mainPeerKind;
332
+ }
333
+ }
334
+ const needsThreadModule = gateway.needsThreadIndexLookup(routeOpts.thread)
335
+ || routeOpts.to !== undefined;
336
+ if (needsThreadModule) {
337
+ const threadModule = await loadDist('core/thread/thread-service.js');
338
+ if (!threadModule && gateway.needsThreadIndexLookup(routeOpts.thread)) {
339
+ fail(BUILD_HINT, 'BUILD_REQUIRED');
340
+ }
341
+ if (threadModule) {
342
+ let entry;
343
+ try {
344
+ entry = threadModule.ThreadService.findThreadById(runtime.selfAid, routeOpts.thread);
345
+ } catch {
346
+ entry = undefined;
347
+ }
348
+ deps.resolveThread = threadId => {
349
+ if (!entry || entry.threadId !== threadId) return undefined;
350
+ return {
351
+ threadId: entry.threadId,
352
+ selfAid: runtime.selfAid,
353
+ peer: {
354
+ channelType: entry.channelType ?? 'aun',
355
+ peerKind: entry.peerKind,
356
+ id: entry.peer,
357
+ },
358
+ };
359
+ };
360
+ // 查不到主会话 = 还没跟这个人聊过,按首次联系处理;查询异常一律按"已存在"放行,
361
+ // 判定权仍归下游。
362
+ deps.mainSessionExists = peer => {
363
+ try {
364
+ return !!threadModule.ThreadService.findMainSessionEntry(runtime.selfAid, peer.id);
365
+ } catch {
366
+ return true;
367
+ }
368
+ };
369
+ }
370
+ }
371
+
372
+ const outcome = routing.resolveSendRoute(
373
+ {
374
+ thread: routeOpts.thread,
375
+ to: routeOpts.to,
376
+ from: routeOpts.from,
377
+ checkEvery: routeOpts.checkEvery,
378
+ encrypt: routeOpts.encrypt,
379
+ noEncrypt: routeOpts.noEncrypt === true,
380
+ // auto 的判据:本轮是否带着入站消息的加密态。有该状态说明是回复对端消息,
381
+ // 沿用它的加密方式;没有(如 trigger 唤醒发起)则明文。
382
+ inboundTriggered: runtime.inboundEncrypted !== undefined,
383
+ inboundEncrypted: runtime.inboundEncrypted === true,
384
+ },
385
+ {
386
+ selfAid: runtime.selfAid,
387
+ channelType: runtime.channel,
388
+ chatType: runtime.chatType === 'group' ? 'group' : 'private',
389
+ peerId: currentPeerIdOf(runtime),
390
+ threadId: routing.isThreadTopicId(runtime.threadId) ? runtime.threadId : undefined,
391
+ },
392
+ deps,
393
+ );
394
+
395
+ if (!outcome.ok) fail(outcome.message, outcome.code, outcome.hint ? { hint: outcome.hint } : {});
188
396
 
189
- const result = await queryDaemonOnce(await resolveSocketPath(), {
397
+ // ── 分派 ──
398
+ const dispatch = gateway.decideDispatch(outcome, text, passthrough, runtime.channel);
399
+ if (dispatch.kind === 'reject') {
400
+ fail(dispatch.message, dispatch.code, dispatch.hint ? { hint: dispatch.hint } : {});
401
+ }
402
+ if (dispatch.kind === 'session') {
403
+ await dispatchSessionChannel(outcome, text, runtime, sessionId, delegationToken, routing, argv);
404
+ return;
405
+ }
406
+
407
+ const daemonArgv = dispatch.argv;
408
+
409
+ // 委托哈希必须覆盖**实际下发的 argv**:daemon 在 `aun-msg-send` 带 argv 时按
410
+ // `['ec', ...cmd.argv]` 重算并比对(ipc.ts 的 DELEGATED_ARGV_ENDPOINTS 闸门)。
411
+ // 网关下发的 argv 与调用方写的简化式不同(补了 from/to 与加密二态),
412
+ // 拿简化式算哈希必然 command_hash_mismatch。
413
+ if (readDelegatedExecutionSpec([MAIN_CLI_BIN, ...daemonArgv], process.env)) {
414
+ // 被安全输出 helper 包过的调用带执行规格,daemon 侧无对应字段可比对,这里无法绑定。
415
+ fail('ecmsg 不支持在安全输出包装内调用', 'UNSUPPORTED_WRAPPER');
416
+ }
417
+ const delegationCommandHash = hashDelegatedCommandArgv([MAIN_CLI_BIN, ...daemonArgv]);
418
+
419
+ let socketPath;
420
+ try {
421
+ const paths = await loadDist('paths.js');
422
+ socketPath = paths.resolvePaths().socket;
423
+ } catch {
424
+ fail(BUILD_HINT, 'BUILD_REQUIRED');
425
+ }
426
+
427
+ const result = await queryDaemonOnce(socketPath, {
190
428
  type: 'aun-msg-send',
191
429
  argv: daemonArgv,
192
430
  delegationToken,
193
431
  ...(delegationCommandHash ? { delegationCommandHash } : {}),
194
432
  originSessionId: sessionId,
195
- ...(runtimeCtx?.messageId ? { originMessageId: runtimeCtx.messageId } : {}),
433
+ ...(runtime.messageId ? { originMessageId: runtime.messageId } : {}),
196
434
  ...(process.env.EVOLCORE_DAEMON_RUNTIME_EPOCH
197
435
  ? { daemonRuntimeEpoch: process.env.EVOLCORE_DAEMON_RUNTIME_EPOCH }
198
436
  : {}),
199
437
  });
200
438
 
201
- if (!result) fail('无法连接 EvolCore daemon(AUN_DAEMON_UNAVAILABLE)。');
439
+ if (!result) fail('无法连接 EvolCore daemon(AUN_DAEMON_UNAVAILABLE)', 'DAEMON_UNAVAILABLE');
202
440
  if (!result.ok) {
203
- fail([
441
+ fail(
442
+ [result.error ?? 'Send failed',
443
+ result.request_id ? `request_id=${result.request_id}` : '',
444
+ result.detail_code ? `detail_code=${result.detail_code}` : ''].filter(Boolean).join(' · '),
204
445
  result.code ?? 'AUN_SEND_FAILED',
205
- result.error ?? 'Send failed',
206
- result.request_id ? `request_id=${result.request_id}` : '',
207
- result.detail_code ? `detail_code=${result.detail_code}` : '',
208
- ].filter(Boolean).join(' · '));
446
+ result.contact_request ? { contact_request: result.contact_request } : {},
447
+ );
209
448
  }
210
449
 
211
- const formatIndex = args.indexOf('--format');
212
- const wantJson = formatIndex >= 0 && args[formatIndex + 1] === 'json';
213
- if (wantJson) {
214
- process.stdout.write(`${JSON.stringify(result)}\n`);
450
+ renderReceipt(outcome, result, routing, gateway);
451
+ }
452
+
453
+ /**
454
+ * 回执:路由信息前置且为实际生效值。
455
+ *
456
+ * 调用方在发送前不一定知道(或记错了)from/to,回执回显是唯一确认手段;
457
+ * 由系统补全的项标注来源(会话/传入/推导),让调用方知道该核对什么。
458
+ */
459
+ function renderReceipt(route, result, routing, gateway) {
460
+ const routeLine = routing.formatRouteReceipt(route);
461
+
462
+ if (jsonOutput) {
463
+ process.stdout.write(`${JSON.stringify({
464
+ ok: true,
465
+ from: route.self,
466
+ to: route.peer.id,
467
+ thread: route.threadId,
468
+ chatType: route.peer.peerKind,
469
+ crossTopic: route.crossTopic,
470
+ firstContact: route.firstContact,
471
+ checkEveryMs: route.checkEveryMs,
472
+ checkEveryDefaulted: route.checkEveryDefaulted,
473
+ checkEveryIgnored: route.checkEveryIgnored,
474
+ encrypt: route.encrypt,
475
+ encryptResolved: route.encryptResolved,
476
+ message_id: result.message_id,
477
+ seq: result.seq,
478
+ status: result.status,
479
+ trigger_id: result.trigger_id,
480
+ })}\n`);
215
481
  return;
216
482
  }
483
+
217
484
  if (result.request_id) {
218
- process.stdout.write(`sent message_id=${result.message_id ?? '-'} request_id=${result.request_id} state=${result.request_state ?? '-'}\n`);
485
+ process.stdout.write(
486
+ `✓ 已发送 ${routeLine} message_id=${result.message_id ?? '-'}`
487
+ + ` request_id=${result.request_id} state=${result.request_state ?? '-'}\n`,
488
+ );
219
489
  return;
220
490
  }
491
+
221
492
  const seq = result.seq ?? result.message?.seq ?? '-';
222
- process.stdout.write(`✓ 已发送 message_id=${result.message_id ?? '-'} seq=${seq} status=${result.status ?? '-'}\n`);
223
- if (result.trigger_id) process.stdout.write(`✓ 复查 Trigger ${result.trigger_id}\n`);
224
- else if (result.trigger_error) {
225
- process.stderr.write(`⚠ 复查 Trigger 未创建: ${result.trigger_error}(消息已发出,需要复查请手动 ec trigger create)\n`);
493
+ process.stdout.write(
494
+ `✓ 已发送 ${routeLine} message_id=${result.message_id ?? '-'} seq=${seq} status=${result.status ?? '-'}\n`,
495
+ );
496
+
497
+ if (route.firstContact) {
498
+ process.stdout.write('· 首次联系:目标会话随本条建立,本次不建复查\n');
499
+ } else if (route.crossTopic) {
500
+ const duration = gateway.formatDuration(route.checkEveryMs);
501
+ const label = route.checkEveryDefaulted ? `默认 ${duration}` : duration;
502
+ process.stdout.write(`✓ 已建复查(${label}) trigger_id=${result.trigger_id ?? '(未返回)'}\n`);
503
+ }
504
+ if (route.checkEveryIgnored && !route.firstContact) process.stdout.write('· 同话题,未创建复查\n');
505
+ if (result.trigger_error) {
506
+ process.stderr.write(`⚠ 复查 Trigger 未创建: ${result.trigger_error}\n`);
507
+ }
508
+ }
509
+
510
+ /**
511
+ * 非 AUN 渠道的发送分派。
512
+ *
513
+ * 现状(P3 实测结论):非 AUN 只有 `ctl send` 一条通道,而它的目标**固定为
514
+ * 当前会话的 channelId**(`command-handler.ts` 的 `/send` 分支直接用
515
+ * `session.channelId`,不接受目标参数)。因此:
516
+ *
517
+ * - 同话题(目标就是当前会话对端)→ 可以发,走 ctl。
518
+ * - 跨话题(目标不是当前对端)→ 无可用通道,明确失败。
519
+ *
520
+ * 不做"降级发到当前会话"——那会把消息发给错的联系人,比失败危险得多。
521
+ * 非 AUN 跨话题能力待后续接入(见计划 P3-5)。
522
+ *
523
+ * 委托凭证:`ctl` 分支用 `validate()`(消费审批语义),但会话级 grant 命中
524
+ * `activeHashBySession` 时 `commandHash` 不参与判定,因此这里只需带上 token。
525
+ */
526
+ async function dispatchSessionChannel(route, text, runtime, sessionId, delegationToken, routing, cliArgv) {
527
+ const body = text.join(' ');
528
+
529
+ let socketPath;
530
+ try {
531
+ const paths = await loadDist('paths.js');
532
+ socketPath = paths.resolvePaths().socket;
533
+ } catch {
534
+ fail(BUILD_HINT, 'BUILD_REQUIRED');
535
+ }
536
+
537
+ // 关键:同话题走 ctl 通道,但委托哈希不能交给 ipc 层按 `['ec','ctl','send',...]`
538
+ // 自动推导——策略层 arm 的是 `['ec','msg','send',...]`(ecmsg 归一到 ec msg)。
539
+ // 必须显式传入同一个归一化 argv 的哈希,否则必然 command_hash_mismatch。
540
+ const parser = await loadDist('core/permission/ec-command-parser.js');
541
+ if (!parser) fail(BUILD_HINT, 'BUILD_REQUIRED');
542
+ const normalizedArgv = parser.canonicalizeEvolcoreCommandArgv(['ecmsg', ...cliArgv]);
543
+ const executionSpec = readDelegatedExecutionSpec(normalizedArgv, process.env);
544
+ const delegationCommandHash = hashDelegatedCommandArgv(normalizedArgv, executionSpec);
545
+
546
+ const result = await queryDaemonOnce(socketPath, {
547
+ type: 'ctl',
548
+ argv: ['ctl', 'send', body],
549
+ sessionId,
550
+ delegationToken,
551
+ ...(delegationCommandHash ? { delegationCommandHash } : {}),
552
+ }, 30_000);
553
+
554
+ if (!result) fail('无法连接 EvolCore daemon(DAEMON_UNAVAILABLE)', 'DAEMON_UNAVAILABLE');
555
+ if (!result.ok) fail(result.error ?? 'Send failed', result.code ?? 'SEND_FAILED');
556
+
557
+ const routeLine = routing.formatRouteReceipt(route);
558
+ if (jsonOutput) {
559
+ process.stdout.write(`${JSON.stringify({
560
+ ok: true,
561
+ from: route.self,
562
+ to: route.peer.id,
563
+ thread: route.threadId,
564
+ chatType: route.peer.peerKind,
565
+ crossTopic: false,
566
+ message_id: null,
567
+ status: 'sent',
568
+ })}\n`);
569
+ return;
226
570
  }
571
+ // ctl 通道没有 message_id,如实写出而不是假装有
572
+ process.stdout.write(`✓ 已发送 ${routeLine} status=sent message_id=n/a\n`);
227
573
  }
228
574
 
229
575
  void main();
@@ -1,7 +1,7 @@
1
1
  import { normalizeBaseagent } from './baseagent.js';
2
- import { commandExists } from '../utils/cross-platform.js';
3
- import { getCodexAppServerAvailability } from './codex-runner.js';
4
- import { probeBundledClaudeVersion, resolveBundledClaudeExecutable } from './claude-runner.js';
2
+ import { commandExists, commandExistsAsync } from '../utils/cross-platform.js';
3
+ import { getCodexAppServerAvailability, getCodexAppServerAvailabilityAsync } from './codex-runner.js';
4
+ import { probeBundledClaudeVersion, probeBundledClaudeVersionAsync, resolveBundledClaudeExecutable } from './claude-runner.js';
5
5
  /**
6
6
  * Claude 的检测判据就是执行判据:会话只会在 Windows 上跑内置的、与 SDK 锁定版本
7
7
  * 配套的 claude.exe。PATH 里的全局 claude 执行层从不使用,因此不能作为可用判据——
@@ -35,6 +35,21 @@ export function detectBaseagentDetails(codexAvailability = getCodexAppServerAvai
35
35
  const claude = claudeExecutable();
36
36
  const claudeVersion = claude ? probeBundledClaudeVersion() : undefined;
37
37
  const gemini = commandExists('gemini');
38
+ return baseagentDetails(codexAvailability, claude, claudeVersion, gemini);
39
+ }
40
+ export async function detectBaseagentDetailsAsync() {
41
+ const [codex, claude, gemini] = await Promise.all([
42
+ getCodexAppServerAvailabilityAsync(),
43
+ (process.platform === 'win32'
44
+ ? Promise.resolve(resolveBundledClaudeExecutable())
45
+ : commandExistsAsync('claude').then(found => found ? 'claude' : undefined))
46
+ .then(async (executable) => ({ executable,
47
+ version: executable ? await probeBundledClaudeVersionAsync() : undefined })),
48
+ commandExistsAsync('gemini'),
49
+ ]);
50
+ return baseagentDetails(codex, claude.executable, claude.version, gemini);
51
+ }
52
+ function baseagentDetails(codexAvailability, claude, claudeVersion, gemini) {
38
53
  return [
39
54
  {
40
55
  id: 'claude',
@@ -132,6 +147,6 @@ export async function getBaseagentSnapshot(options = {}) {
132
147
  }
133
148
  const detections = options.probe === false
134
149
  ? null
135
- : detectBaseagentDetails();
150
+ : await detectBaseagentDetailsAsync();
136
151
  return buildBaseagentSnapshot(config ?? {}, detections, options.loaded);
137
152
  }
@@ -543,8 +543,8 @@ export function resolveOpenaiConfig(config, override, runtime) {
543
543
  authType: 'apiKey',
544
544
  authSource: 'agent-config',
545
545
  baseUrl: provider.baseUrl,
546
- provider: providerId,
547
- providerId,
546
+ provider: provider.providerId,
547
+ providerId: provider.providerId,
548
548
  headers: provider.headers,
549
549
  queryParams: provider.queryParams,
550
550
  model: override?.model || config.agents?.codex?.model || codexSettings.model