evolcore 0.0.43-test.6 → 0.0.43-test.8
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.
- package/CHANGELOG.md +95 -0
- package/bin/ecmsg.js +188 -58
- package/dist/agent-template/jobs.js +62 -0
- package/dist/agent-template/runtime.js +214 -0
- package/dist/agent-template/service.js +465 -0
- package/dist/agent-template/tool-runner.js +45 -0
- package/dist/agent-template/types.js +5 -0
- package/dist/agents/baseagent-availability.js +1 -1
- package/dist/agents/claude-runner.js +1 -1
- package/dist/agents/codex/app-server-client.js +22 -0
- package/dist/agents/codex-runner.js +69 -2
- package/dist/aun/aid/agentmd.js +56 -1
- package/dist/aun/aid/client.js +3 -1
- package/dist/aun/menu/client.js +3 -2
- package/dist/aun/msg/p2p.js +6 -1
- package/dist/channels/aun.js +277 -49
- package/dist/cli/agent-command.js +5 -0
- package/dist/cli/agent-create.js +7 -3
- package/dist/cli/agent-template.js +124 -0
- package/dist/cli/aun-commands.js +2 -2
- package/dist/cli/ctl-command.js +2 -1
- package/dist/cli/daemon-commands.js +11 -66
- package/dist/cli/daemon-lifecycle-client.js +61 -0
- package/dist/cli/ecmsg-gateway.js +35 -2
- package/dist/cli/events-command.js +109 -0
- package/dist/cli/index.js +60 -14
- package/dist/cli/invoke-command.js +182 -0
- package/dist/cli/managed-command-guard.js +6 -1
- package/dist/cli/net-check.js +1 -1
- package/dist/cli/restart-monitor.js +160 -83
- package/dist/cli/services-command.js +137 -0
- package/dist/cli/team-workspace-command.js +134 -0
- package/dist/cli/thread-command.js +103 -13
- package/dist/cli/watch-msg.js +1 -1
- package/dist/config/boot-log.js +8 -8
- package/dist/config/config-field-policy.js +2 -2
- package/dist/config/config-manager.js +0 -7
- package/dist/config/invoke-ipc-service.js +118 -0
- package/dist/config/schema-migration.js +45 -15
- package/dist/config-store.js +2 -1
- package/dist/core/agent-ipc-registration.js +25 -4
- package/dist/core/agent-reload-coordinator.js +6 -4
- package/dist/core/agent-runtime.js +106 -10
- package/dist/core/auth/delegation-authorization.js +66 -0
- package/dist/core/auth/operation-authorizer.js +2 -0
- package/dist/core/auth/operation-catalog.js +29 -0
- package/dist/core/baseagent-loader.js +60 -130
- package/dist/core/channel-loader.js +10 -1
- package/dist/core/channel-runtime.js +20 -12
- package/dist/core/command/agent-control.js +12 -2
- package/dist/core/command/agent-storage-menu.js +1 -1
- package/dist/core/command/agent-template-menu.js +147 -0
- package/dist/core/command/chatmode-config.js +2 -36
- package/dist/core/command/command-handler.js +80 -17
- package/dist/core/command/data-root-resolver.js +32 -23
- package/dist/core/command/eventcenter-menu.js +468 -0
- package/dist/core/command/menu-catalog.js +15 -0
- package/dist/core/command/menu-handler.js +216 -90
- package/dist/core/command/menu-protocol.js +71 -13
- package/dist/core/command/menu-query-batch.js +194 -0
- package/dist/core/command/slash-gate.js +1 -1
- package/dist/core/command/slash-handler.js +34 -42
- package/dist/core/command/team-workspace-bootstrap.js +350 -0
- package/dist/core/command/{pa-workspace-calendar.js → team-workspace-calendar.js} +7 -7
- package/dist/core/command/team-workspace-initializer.js +2 -0
- package/dist/core/command/{pa-workspace-items.js → team-workspace-items.js} +83 -68
- package/dist/core/command/team-workspace-job-store.js +88 -0
- package/dist/core/command/team-workspace-management-service.js +2 -0
- package/dist/core/command/team-workspace-management-store.js +96 -0
- package/dist/core/command/team-workspace-management.js +265 -0
- package/dist/core/command/team-workspace-members-menu.js +88 -0
- package/dist/core/command/team-workspace-store.js +612 -0
- package/dist/core/command/team-workspace-team.js +193 -0
- package/dist/core/daemon-control.js +22 -5
- package/dist/core/daemon-lifecycle.js +323 -191
- package/dist/core/handoff/runtime.js +45 -13
- package/dist/core/invoke/executors/index.js +13 -0
- package/dist/core/invoke/executors/media.js +283 -0
- package/dist/core/invoke/executors/text.js +198 -0
- package/dist/core/invoke/invoke-service.js +157 -0
- package/dist/core/invoke/style-router.js +48 -0
- package/dist/core/invoke/types.js +19 -0
- package/dist/core/ipc-registration.js +50 -7
- package/dist/core/legacy-rename.js +41 -0
- package/dist/core/memory/consolidation.js +7 -5
- package/dist/core/message/aun-ipc-sender.js +252 -17
- package/dist/core/message/im-renderer.js +116 -85
- package/dist/core/message/message-bridge.js +4 -0
- package/dist/core/message/message-queue.js +66 -15
- package/dist/core/message/message-utils.js +10 -2
- package/dist/core/message/peer-mode.js +7 -34
- package/dist/core/message/pending-hints.js +29 -5
- package/dist/core/message/response-engine.js +194 -61
- package/dist/core/message/send-options.js +7 -4
- package/dist/core/message/send-routing.js +50 -5
- package/dist/core/ownership/owner-resolver.js +7 -0
- package/dist/core/pack-auth.js +94 -0
- package/dist/core/pack-install.js +194 -0
- package/dist/core/permission/ec-command-parser.js +51 -17
- package/dist/core/permission/protected-paths.js +12 -2
- package/dist/core/permission/shell-environment.js +9 -0
- package/dist/core/rate-window.js +48 -0
- package/dist/core/relation/peer-identity.js +28 -0
- package/dist/core/session/session-file-health.js +243 -0
- package/dist/core/session/session-fs-store.js +67 -28
- package/dist/core/session/session-idle-monitor.js +59 -19
- package/dist/core/session/session-manager.js +13 -4
- package/dist/core/task/task-recovery-service.js +13 -2
- package/dist/core/thread/command-parser.js +9 -2
- package/dist/core/thread/thread-operation.js +21 -2
- package/dist/core/thread/thread-route.js +13 -2
- package/dist/core/thread/thread-service.js +52 -3
- package/dist/directory/owner-directory-admission.js +40 -53
- package/dist/directory/owner-directory-cache.js +89 -113
- package/dist/directory/owner-directory-query-operation.js +8 -10
- package/dist/eck/kit-renderer.js +7 -5
- package/dist/eck/message-renderer.js +2 -0
- package/dist/ecweb/basic-settings-service.js +1 -1
- package/dist/ecweb/message-context-service.js +0 -4
- package/dist/ecweb/runtime/lifecycle.js +6 -2
- package/dist/ecweb/runtime/supervisor.js +19 -4
- package/dist/event-center/admission-materializer.js +124 -0
- package/dist/event-center/bus-gate.js +154 -0
- package/dist/event-center/bus-host.js +307 -0
- package/dist/event-center/bus-resolver.js +120 -0
- package/dist/event-center/center-config.js +127 -0
- package/dist/event-center/daemon.js +44 -0
- package/dist/event-center/directory-source.js +55 -0
- package/dist/event-center/dispatcher.js +157 -0
- package/dist/event-center/event-log.js +110 -0
- package/dist/event-center/index-generator.js +73 -0
- package/dist/event-center/ipc-operation.js +423 -0
- package/dist/event-center/ledger.js +52 -0
- package/dist/event-center/pack-loader.js +207 -0
- package/dist/event-center/pack-manager.js +85 -0
- package/dist/event-center/registry.js +463 -0
- package/dist/event-center/runtime.js +837 -0
- package/dist/event-center/script-runner.js +356 -0
- package/dist/event-center/types.js +51 -0
- package/dist/event-center/validation.js +435 -0
- package/dist/index.js +424 -135
- package/dist/ipc.js +106 -12
- package/dist/paths.js +20 -0
- package/dist/product.js +14 -0
- package/dist/proxy/manager.js +5 -1
- package/dist/proxy/service-supervisor.js +13 -4
- package/dist/response-system/engines/v1/index.js +0 -1
- package/dist/response-system/engines/v1/proactive-flow.js +4 -2
- package/dist/response-system/modes/single-session/index.js +1 -1
- package/dist/services/dispatcher.js +100 -0
- package/dist/services/idempotency.js +90 -0
- package/dist/services/identity.js +52 -0
- package/dist/services/index-generator.js +70 -0
- package/dist/services/index.js +449 -0
- package/dist/services/ipc-operation.js +550 -0
- package/dist/services/ledger.js +52 -0
- package/dist/services/message-log.js +112 -0
- package/dist/services/pack-manager.js +215 -0
- package/dist/services/reply.js +55 -0
- package/dist/services/router.js +98 -0
- package/dist/services/script-runner.js +422 -0
- package/dist/services/service-payload.js +70 -0
- package/dist/services/types.js +18 -0
- package/dist/services/validation.js +297 -0
- package/dist/trigger/application-service.js +18 -0
- package/dist/trigger/event-source.js +1 -1
- package/dist/trigger/ipc-service.js +3 -1
- package/dist/trigger/scheduler.js +38 -0
- package/dist/trigger/script-sandbox.js +170 -24
- package/dist/utils/cross-platform.js +24 -10
- package/dist/utils/evolcore-version.js +69 -27
- package/dist/utils/instance-registry.js +19 -13
- package/dist/utils/npm-ops.js +2 -1
- package/dist/utils/package-version-info.js +6 -3
- package/dist/utils/process-introspect.js +45 -9
- package/dist/utils/startup-trace.js +74 -37
- package/dist/utils/windows-shell-trust.js +80 -6
- package/kits/docs/INDEX.md +2 -2
- package/kits/docs/aun/ABILITY_CALLING.md +9 -15
- package/kits/docs/context-assembly.md +1 -1
- package/kits/docs/evolcore/INDEX.md +3 -1
- package/kits/docs/evolcore/ability.md +4 -0
- package/kits/docs/evolcore/agent.md +22 -1
- package/kits/docs/evolcore/aid.md +1 -1
- package/kits/docs/evolcore/event-center.md +227 -0
- package/kits/docs/evolcore/file-navigation.md +10 -264
- package/kits/docs/evolcore/fs.md +5 -3
- package/kits/docs/evolcore/group.md +1 -1
- package/kits/docs/evolcore/memory-architecture.md +2 -0
- package/kits/docs/evolcore/menu-protocol.md +28 -1
- package/kits/docs/evolcore/msg.md +21 -9
- package/kits/docs/evolcore/provider.md +3 -1
- package/kits/docs/evolcore/response.md +5 -5
- package/kits/docs/evolcore/services.md +294 -0
- package/kits/docs/evolcore/task.md +2 -0
- package/kits/docs/evolcore/team-workspace.md +41 -0
- package/kits/docs/evolcore/thread-chain.md +15 -3
- package/kits/eck_manifest.json +26 -0
- package/kits/rules/02-navigation.md +10 -1
- package/kits/rules/06-channel.md +1 -0
- package/kits/schemas/_meta.json +17 -6
- package/kits/schemas/agent-config.schema.19.json +5 -7
- package/kits/schemas/agent-config.schema.20.json +936 -0
- package/kits/schemas/relation-config.schema.12.json +2 -3
- package/kits/schemas/role-config.schema.2.json +4 -4
- package/kits/skills/.switches.json +1 -5
- package/kits/skills/ability/SKILL.md +56 -0
- package/kits/skills/ability/references/calling.md +56 -0
- package/kits/skills/{ec-ability → ability}/references/contract-checklist.md +1 -1
- package/kits/skills/{ec-ability → ability}/references/development.md +9 -33
- package/kits/skills/{ec-ability → ability}/references/management.md +2 -2
- package/kits/skills/{ec-ability → ability}/references/recovery.md +1 -1
- package/kits/skills/{ec-ability → ability}/references/runtime-protocol.md +2 -0
- package/kits/skills/ec-agent-create/SKILL.md +0 -1
- package/kits/skills/ec-group/SKILL.md +5 -8
- package/kits/skills/ec-group-collaboration/SKILL.md +7 -7
- package/kits/skills/ec-service-proxy/SKILL.md +34 -5
- package/kits/skills/ec-trigger/SKILL.md +4 -4
- package/kits/skills/personal-assistant/SKILL.md +6 -6
- package/kits/skills/personal-assistant/references/02-bootstrap.md +4 -4
- package/kits/skills/personal-assistant/scripts/clean.mjs +4 -4
- package/kits/skills/personal-assistant/scripts/init.mjs +2 -2
- package/kits/skills/personal-assistant/scripts/pa.mjs +4 -4
- package/kits/skills/thread-ops/SKILL.md +10 -10
- package/kits/templates/message-fragments/item.md +1 -1
- package/kits/templates/system-fragments/channel.md +3 -3
- package/kits/templates/system-fragments/commands.md +5 -3
- package/kits/templates/system-fragments/reply.md +1 -5
- package/kits/templates/system-fragments/thread.md +13 -10
- package/package.json +5 -6
- package/scripts/agent-template/index.mjs +40 -0
- package/scripts/agent-template/inspect.mjs +240 -0
- package/scripts/agent-template/overlay.mjs +71 -0
- package/scripts/agent-template/pack.mjs +169 -0
- package/scripts/agent-template/shared/common.mjs +235 -0
- package/scripts/agent-template/shared/evolcore.mjs +75 -0
- package/scripts/agent-template/shared/plan.mjs +129 -0
- package/scripts/agent-template/shared/team-schema.json +70 -0
- package/scripts/agent-template/shared/template-contract.mjs +154 -0
- package/scripts/agent-template/shared/template-package.mjs +265 -0
- package/scripts/agent-template/shared/template-runtime.mjs +80 -0
- package/scripts/agent-template/shared/template.mjs +142 -0
- package/dist/cli/pa-workspace-command.js +0 -225
- package/dist/core/command/pa-workspace-store.js +0 -468
- package/dist/core/relation/pa-team.js +0 -132
- package/kits/docs/evolcore/pa-workspace.md +0 -51
- package/kits/skills/aid-ability/SKILL.md +0 -244
- package/kits/skills/ec-ability/SKILL.md +0 -67
- package/kits/skills/ec-ability/references/workflows.md +0 -15
|
@@ -65,7 +65,9 @@ Provider 不再创建独立的长期迁移备份,版本查看、恢复和保
|
|
|
65
65
|
|
|
66
66
|
引用更新与 aliases 清理作为同一事务提交,providers.json 最后写入。配置无法读取、迁移冲突或并发写入时拒绝提交;提交失败回滚,异常中断由下次启动恢复。成功后旧 ID 不再可用;重复启动无变更时不产生新备份。外部脚本应改用固定 ID,历史备份不重写。启动收尾不导入本机连接、不修改默认基座或模型,也不展开环境变量。
|
|
67
67
|
|
|
68
|
-
托管 Codex 使用解析后的固定 Provider ID 生成运行时 model_provider
|
|
68
|
+
托管 Codex 使用解析后的固定 Provider ID 生成运行时 model_provider。Codex 会拒绝仅靠 thread/resume 参数切换旧 thread 的 Provider;EvolCore 在续聊、任务恢复和压缩前,持有 thread 操作锁,检查 rollout 元数据和 SQLite 索引中的 Provider。与当前配置不一致时,先确认已有运行时已释放,再备份并同步更新两处 Provider,保留原 thread ID、EC 会话绑定及历史字节,随后 resume 并核验返回的 thread ID 和 Provider。不会修改用户原生 Codex config.toml 的 model_provider/model_providers。模型目录查询与推理使用相同的运行时命名规则。
|
|
69
|
+
|
|
70
|
+
修复的备份和中断恢复记录保存在 rollout 相邻的 `.provider-repair/` 目录(完整目录名为 `<rollout文件名>.provider-repair`)。文件替换与 SQLite 提交之间发生中断时,下次恢复会先核对记录并完成同步;检测到较新的文件或索引、无法释放的运行时、不匹配的身份或不支持的存储格式时停止并报告原因,不覆盖数据或更换 thread。这里只处理 EC 已绑定的会话;模型输入在修复及恢复校验完成后提交。
|
|
69
71
|
|
|
70
72
|
## 完整对象示例
|
|
71
73
|
|
|
@@ -34,18 +34,18 @@ ec response config set <key> <value> --mode <mode-id> --self <aid> [--peer <X>]
|
|
|
34
34
|
|
|
35
35
|
| 模式 id | 显示名 | 场景 | 用途 |
|
|
36
36
|
|---------|--------|------|------|
|
|
37
|
-
| `single-session` | 单会话模式 | 私聊/群聊 | 单会话直接处理;具体投递方式由 `chatmode` 的 `interactive` / `proactive`
|
|
37
|
+
| `single-session` | 单会话模式 | 私聊/群聊 | 单会话直接处理;具体投递方式由 `chatmode` 的 `interactive` / `proactive` 决定 |
|
|
38
38
|
|
|
39
39
|
当前注册表只内置 `single-session`。历史的 `interactive` / `proactive` 已合并为该模式下的
|
|
40
40
|
`chatmode` 流程,不再是可传给 `ec response set` 的 mode id。
|
|
41
41
|
|
|
42
|
-
|
|
42
|
+
聊天模式仅有 interactive/proactive。PA 与其他 Agent 共用 proactive 的执行流、工具门禁、ECK manifest/vars、文件、审批/提问及现有 notify,不增加专用模式或配置选项。
|
|
43
43
|
|
|
44
|
-
|
|
44
|
+
在 active AUN 人类 Owner 私聊主会话及话题中,若当前 Agent 是名录指定的个人助理,且名录 Owner 与当前 Ownership 共识一致,则该轮 proactive 过程活动经可靠 activity outbox 使用 message.send(type=activity) 投递;自动最终正文在任务成功提交后以 type=custom、kind=agent_final、text=正文发送一次,同样使用 activity outbox。最终候选按输出阶段及文本/工具边界判定,不重复发送同正文的 activity 或普通 text。其他 proactive 场景继续使用 thought.put,包括非 PA、群聊、第三方私聊、辅助会话及 PA 身份无法确认的情况。PA Team 普通成员不等于个人助理。投递方式在任务开始时确定,身份变化对下一任务生效。
|
|
45
45
|
|
|
46
|
-
|
|
46
|
+
正式回复始终由托管 ecmsg send 显式发送;自动 activity/custom 发送失败不会降级为普通文本消息。群聊固定 proactive;当前 schema 拒绝写入 interactive 群聊配置,已发布旧 schema 的 group=interactive 仅在读取时归一为 proactive。
|
|
47
47
|
|
|
48
|
-
proactive
|
|
48
|
+
proactive 遵守 `show_activities`:`all` 投递全部活动,`text` 只投递模型文本,`none` 不投递活动(含最终模型文本);这些活动根据上述条件走 message.send 或 thought.put。未显式配置时,群聊默认 `none`,私聊默认 `all`;显式配置仍按关系 > Agent > defaults 覆盖。群聊通过 Menu 或 `ec config` 调整,私聊也可使用 `/activity all|text|none`。本地任务活动记录、正式 `ecmsg send` 和任务状态通知不受此参数影响。
|
|
49
49
|
|
|
50
50
|
## 作用域(越具体越优先:关系 > agent > 全局)
|
|
51
51
|
|
|
@@ -0,0 +1,294 @@
|
|
|
1
|
+
# 服务路由(`ec services`)
|
|
2
|
+
|
|
3
|
+
> 完整设计见仓库 `docs/services/`;Schema 见 `docs/services/schema/`。
|
|
4
|
+
|
|
5
|
+
Agent 怎么建服务包、写处理脚本、让对端调到你。
|
|
6
|
+
|
|
7
|
+
## 一、先判断该不该用
|
|
8
|
+
|
|
9
|
+
| 要做的事 | 用什么 |
|
|
10
|
+
| --- | --- |
|
|
11
|
+
| 到点执行(每天 9 点、每隔 30 分钟) | `ec trigger`,不是服务 |
|
|
12
|
+
| 对端发消息给我,我跑确定性逻辑并**回结果** | **服务** |
|
|
13
|
+
| 我要主动通知别人 | 事件中心(`ec events`)或 `ecmsg` |
|
|
14
|
+
| 消息绝不能丢、必须有应答 | **服务**(走普通持久消息) |
|
|
15
|
+
| 广播给很多人 | 事件中心,不是服务 |
|
|
16
|
+
|
|
17
|
+
一句话区分:**服务是点对点调用,事件是广播通知。**
|
|
18
|
+
|
|
19
|
+
| | 服务 `services/` | 事件 `events/` |
|
|
20
|
+
| --- | --- | --- |
|
|
21
|
+
| 传输 | 普通持久消息 | AUN pubsub(volatile) |
|
|
22
|
+
| 会丢吗 | 不会 | 会 |
|
|
23
|
+
| 有应答吗 | 有,`.result` | 无 |
|
|
24
|
+
|
|
25
|
+
## 二、目录
|
|
26
|
+
|
|
27
|
+
```
|
|
28
|
+
$AGENT_DIR/services/
|
|
29
|
+
├── services-config.json # 总开关 + 限流
|
|
30
|
+
└── <服务包名>/
|
|
31
|
+
├── pack.json
|
|
32
|
+
├── ledger.jsonl
|
|
33
|
+
├── scripts/
|
|
34
|
+
└── logs/
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
包名用英文短横线,如 `order`、`inventory`。
|
|
38
|
+
|
|
39
|
+
`services/` 是 **L 类受保护路径**——托管会话里不能直接 `Write` / `cp`。装包走 daemon:
|
|
40
|
+
|
|
41
|
+
```bash
|
|
42
|
+
ec services pack add <包名> --from <源目录>
|
|
43
|
+
ec services pack remove <包名> [--purge]
|
|
44
|
+
ec services pack list
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
`services-config.json` 装好后基本不用改:
|
|
48
|
+
|
|
49
|
+
```json
|
|
50
|
+
{
|
|
51
|
+
"v": 1,
|
|
52
|
+
"enabled": true,
|
|
53
|
+
"rateLimit": {
|
|
54
|
+
"service": { "perMinute": 50, "perHour": 1000 },
|
|
55
|
+
"builtin": { "perMinute": 20, "perHour": 200 }
|
|
56
|
+
}
|
|
57
|
+
}
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
`enabled=false` 时所有 `services.*` 静默丢弃(总闸,用 `ec services enable` 打开)。`rateLimit` 按调用方 AID 独立计,`service` 管业务调用、`builtin` 管内置查询;缺省值即上表所列,省掉这个键等价于用缺省。
|
|
61
|
+
|
|
62
|
+
## 三、你的服务叫什么
|
|
63
|
+
|
|
64
|
+
调用名由**本机名片**决定:
|
|
65
|
+
|
|
66
|
+
```bash
|
|
67
|
+
ec aid agentmd set <本AID> type services
|
|
68
|
+
ec aid agentmd set <本AID> exttype order
|
|
69
|
+
```
|
|
70
|
+
|
|
71
|
+
之后对端能调 `services.order.*`。第三段由你在 `pack.json` 里定:
|
|
72
|
+
|
|
73
|
+
```
|
|
74
|
+
services.<exttype>.<action>
|
|
75
|
+
↑ ↑
|
|
76
|
+
名片 exttype 你定的 action
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
**`exttype` 的含义取决于 `type`**:`agent` 下是 baseagent 类型(`Claude Code`),
|
|
80
|
+
`services` 下是服务类型(`order`),`human` 下是前端类型,`host` 下是运行时。
|
|
81
|
+
两者必须一起读,不能单独解释。
|
|
82
|
+
|
|
83
|
+
## 四、专职 与 兼职
|
|
84
|
+
|
|
85
|
+
**专职**——整个 AID 是服务节点:
|
|
86
|
+
|
|
87
|
+
```bash
|
|
88
|
+
ec aid agentmd set <本AID> type services
|
|
89
|
+
ec aid agentmd set <本AID> exttype order
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
效果:只有 Owner 的消息进模型,其他人发普通消息会被回一句"我是服务节点"。
|
|
93
|
+
|
|
94
|
+
**兼职**——正常 agent,顺便提供服务。名片保持 `type=agent`,只建包,
|
|
95
|
+
`requires.type` 写 `["services","agent"]`。聊天、话题、模型一切照旧,**另外**能应答 `services.*`。
|
|
96
|
+
|
|
97
|
+
> 兼职是推荐做法。**不用为提供服务另开一个 AID。**
|
|
98
|
+
|
|
99
|
+
## 五、最小可用包
|
|
100
|
+
|
|
101
|
+
`services/order/pack.json`:
|
|
102
|
+
|
|
103
|
+
```json
|
|
104
|
+
{
|
|
105
|
+
"v": 1,
|
|
106
|
+
"name": "订单受理",
|
|
107
|
+
"requires": { "type": ["services", "agent"], "exttype": "order" },
|
|
108
|
+
"listen": [
|
|
109
|
+
{
|
|
110
|
+
"type": "services.order.create",
|
|
111
|
+
"handler": { "script": "scripts/on-create.mjs", "runtime": "node", "timeoutMs": 15000 }
|
|
112
|
+
}
|
|
113
|
+
],
|
|
114
|
+
"reply": { "allowed": true }
|
|
115
|
+
}
|
|
116
|
+
```
|
|
117
|
+
|
|
118
|
+
约束:
|
|
119
|
+
|
|
120
|
+
- `requires` **必填**,匹配的是**本机名片**,不是消息
|
|
121
|
+
- `listen[].type` 必须是 `services[.<段>[.<段>]]`,末段可写 `*`
|
|
122
|
+
- `handler.script` 必须在 `scripts/` 下,禁止绝对路径、`..`、符号链接
|
|
123
|
+
- `runtime` ∈ `node` / `python` / `bash` / `powershell`;省略时按扩展名推断
|
|
124
|
+
- 同包内 `type` 重复 → 整包 invalid;跨包重复 → 两个包都 invalid
|
|
125
|
+
- 一个包校验失败只废这个包,其余照常
|
|
126
|
+
|
|
127
|
+
装好后:`ec services reload` → `ec services status` 确认 `status=active`。
|
|
128
|
+
|
|
129
|
+
## 六、`requires` 写什么
|
|
130
|
+
|
|
131
|
+
**限制这个包能在什么名片的 AID 上生效。**
|
|
132
|
+
|
|
133
|
+
| 写法 | 含义 |
|
|
134
|
+
| --- | --- |
|
|
135
|
+
| `{"type":"services","exttype":"order"}` | 只在名片 `type=services` + `exttype=order` 时生效 |
|
|
136
|
+
| `{"type":"services","exttype":"*"}` | 任何 services AID |
|
|
137
|
+
| `{"type":["services","agent"],"exttype":"order"}` | services 和 agent 都生效 |
|
|
138
|
+
| `{"type":"*","exttype":"*"}` | 完全放开 |
|
|
139
|
+
|
|
140
|
+
**不匹配不是报错**:包加载但状态 `skipped`,什么也不做。所以拷包给别人是安全的。
|
|
141
|
+
|
|
142
|
+
## 七、怎么调别人
|
|
143
|
+
|
|
144
|
+
```bash
|
|
145
|
+
ec services describe <aid> # 对方有什么
|
|
146
|
+
ec services schema <aid> <type> # 参数结构
|
|
147
|
+
ec services call <aid> <type> --data '<json>' # 发起调用
|
|
148
|
+
```
|
|
149
|
+
|
|
150
|
+
`call` 默认等结果,30 秒超时:
|
|
151
|
+
|
|
152
|
+
```json
|
|
153
|
+
{ "ok": true, "data": { "order_id": "O-1" } }
|
|
154
|
+
```
|
|
155
|
+
|
|
156
|
+
| 选项 | 作用 |
|
|
157
|
+
| --- | --- |
|
|
158
|
+
| `--timeout 60` | 自定等待时长;超时**不重试**,退出码 2 |
|
|
159
|
+
| `--encrypted` | 加密调用,回复也加密 |
|
|
160
|
+
| `--no-wait` | 只发不等 |
|
|
161
|
+
|
|
162
|
+
**超时后不要直接重发**,先查一次确认是否已执行,否则会重复。
|
|
163
|
+
|
|
164
|
+
## 八、脚本契约
|
|
165
|
+
|
|
166
|
+
### stdin(一个 JSON)
|
|
167
|
+
|
|
168
|
+
```json
|
|
169
|
+
{
|
|
170
|
+
"v": 1,
|
|
171
|
+
"service": { "name": "订单受理", "dir": "…/services/order" },
|
|
172
|
+
"message": {
|
|
173
|
+
"type": "services.order.create",
|
|
174
|
+
"requestId": "01J…",
|
|
175
|
+
"from": "alice.agentid.cn",
|
|
176
|
+
"receivedAt": 1794115720000,
|
|
177
|
+
"encrypted": false,
|
|
178
|
+
"data": { "sku": "A-1" }
|
|
179
|
+
},
|
|
180
|
+
"agent": { "aid": "self.agentid.cn", "dir": "…", "type": "services", "exttype": "order" },
|
|
181
|
+
"paths": { "ledger": "…/ledger.jsonl", "logs": "…/logs" }
|
|
182
|
+
}
|
|
183
|
+
```
|
|
184
|
+
|
|
185
|
+
**没有 `threadId` / `topicName` / `chatmode`**——服务调用不是聊天。
|
|
186
|
+
判断来源用 `message.from`。
|
|
187
|
+
|
|
188
|
+
### stdout(最后一行)
|
|
189
|
+
|
|
190
|
+
```json
|
|
191
|
+
{"outcome":"success","data":{"order_id":"O-1"}}
|
|
192
|
+
{"outcome":"error","error":{"code":"OUT_OF_STOCK","message":"库存不足"}}
|
|
193
|
+
{"outcome":"noop"}
|
|
194
|
+
```
|
|
195
|
+
|
|
196
|
+
对端收到 `type` = 原 type + `.result`,`request_id` 原样带回。
|
|
197
|
+
`services.order.create` → `services.order.create.result`。失败同 type,`ok:false` + `error.code`。
|
|
198
|
+
|
|
199
|
+
`result` 是保留段名:`listen` 不能写以 `.result` 结尾的 type;`services.order.*`
|
|
200
|
+
不匹配 `services.order.result`。
|
|
201
|
+
|
|
202
|
+
### 限制
|
|
203
|
+
|
|
204
|
+
| 项 | 值 |
|
|
205
|
+
| --- | --- |
|
|
206
|
+
| 超时 | 默认 30s,`timeoutMs` ∈ [1s, 300s] |
|
|
207
|
+
| 输出上限 | 1 MiB,超出截断 |
|
|
208
|
+
| 环境变量 | `EC_SELF_AID` / `EC_PACK_DIR` / `EC_SERVICE_TYPE` / `EC_REQUEST_ID` |
|
|
209
|
+
| 密钥清理 | 所有 `*_API_KEY` / `*_TOKEN` 被移除 |
|
|
210
|
+
| 沙箱 | 非 fullaccess 走 trigger 同款沙箱;Windows 上 `runtime` 必须是原生可执行文件 |
|
|
211
|
+
|
|
212
|
+
最后一条容易踩,但**不是「`.mjs` 不能跑」**:要求的是 `runtime` 是可执行文件(`"node"` →
|
|
213
|
+
`node.exe`),脚本扩展名不受限,`.mjs` / `.js` / `.cjs` 都能跑。
|
|
214
|
+
|
|
215
|
+
**Windows 沙箱依赖 Codex**:借用 `@openai/codex`(`codex.exe sandbox` + NTFS ACL),
|
|
216
|
+
Codex 只当沙箱宿主,与 baseagent 无关。没装时返回 `SCRIPT_SANDBOX_UNAVAILABLE`(126),
|
|
217
|
+
按报错装 `npm install -g @openai/codex`。Linux 用系统 `bubblewrap`,macOS 无后端、一律拒跑。
|
|
218
|
+
|
|
219
|
+
**沙箱不可用时 daemon 会降级为无沙箱执行**,并在三处留痕:`logger.warn`
|
|
220
|
+
(`reason=sandbox-fallback`)、`handled` 日志的 `sandbox_absent` 字段、附带的原始错误。
|
|
221
|
+
此时脚本能读到本不该读的文件——排查先看 `logs/` 有没有 `sandbox_absent`。
|
|
222
|
+
|
|
223
|
+
**回复由 daemon 代发**,脚本不要自己调 `ecmsg`。加密态跟随来信、不带话题信息、
|
|
224
|
+
自动带 `request_id` 与 `replyToMessageId`。
|
|
225
|
+
|
|
226
|
+
## 九、准入与限流
|
|
227
|
+
|
|
228
|
+
服务调用**认联系人配置**,与普通消息一致。陌生人调用会收到:
|
|
229
|
+
|
|
230
|
+
```json
|
|
231
|
+
{ "ok": false, "error": { "code": "NOT_AUTHORIZED" }, "request_contact": "<你的Owner>" }
|
|
232
|
+
```
|
|
233
|
+
|
|
234
|
+
**不会自动建联系人申请**,对方需自己 `ec directory request` 找你的 Owner。
|
|
235
|
+
|
|
236
|
+
内置查询(`ping`/`list`/`describe`/`schema`/`skill`)**免准入**,但受限流。
|
|
237
|
+
|
|
238
|
+
| 类别 | 额度(按来源 AID 独立计) |
|
|
239
|
+
| --- | --- |
|
|
240
|
+
| 内置查询 | 20 次/分、200 次/时 |
|
|
241
|
+
| 业务调用 | 50 次/分、1000 次/时 |
|
|
242
|
+
|
|
243
|
+
超限回 `RATE_LIMITED`,带 `retry_after` 秒数。
|
|
244
|
+
|
|
245
|
+
## 十、保留字
|
|
246
|
+
|
|
247
|
+
保留字**只占两段形式** `services.<保留字>`:
|
|
248
|
+
|
|
249
|
+
| type | 归谁 |
|
|
250
|
+
| --- | --- |
|
|
251
|
+
| `services.ping` / `services.list` / `services.describe` / `services.schema` / `services.skill` | 内置 |
|
|
252
|
+
| `services.order.list` | 你的包(`list` 在 action 位) |
|
|
253
|
+
| `services.list.create` | 你的包(三段不进保留字判定) |
|
|
254
|
+
|
|
255
|
+
`exttype` 可以设成这些名字,但 `services.<该名字>` 会被内置抢走,其余照常。
|
|
256
|
+
`ec services doctor` 会告警这种部分遮蔽。
|
|
257
|
+
|
|
258
|
+
## 十一、排查
|
|
259
|
+
|
|
260
|
+
```
|
|
261
|
+
ec services status # 包状态:active / skipped / invalid
|
|
262
|
+
ec services doctor <包名> # requires、保留字遮蔽、脚本、路径
|
|
263
|
+
ec services ledger <包名> --tail 20
|
|
264
|
+
ec services tail <包名>
|
|
265
|
+
```
|
|
266
|
+
|
|
267
|
+
| 症状 | 先看 |
|
|
268
|
+
| --- | --- |
|
|
269
|
+
| 包不生效 | `ec services status` 里是不是 `skipped`;`requires` 与本机名片对不对 |
|
|
270
|
+
| 对端调不通 | 你的 `exttype`(`ec aid agentmd get <你自己>`);`services-config.json` 的 `enabled` |
|
|
271
|
+
| 脚本没跑 | `listen` 的 `type` 是否与对方发的完全一致;`filter` 筛掉了? |
|
|
272
|
+
| 脚本失败 | `logs/` 里 `handled` 的 `exit` 和 `cmd` |
|
|
273
|
+
| 收不到回复 | `reply.allowed` 是不是 `false`(默认就是) |
|
|
274
|
+
| `RATE_LIMITED` | 超限,看 `retry_after` |
|
|
275
|
+
|
|
276
|
+
## 十二、不要做的事
|
|
277
|
+
|
|
278
|
+
1. **不要在没有幂等的操作上依赖去重**。daemon 按 `(from, request_id)` 去重 24 小时,
|
|
279
|
+
超出窗口的重试会重新执行。
|
|
280
|
+
2. **不要在脚本里自己发回复**。输出 `outcome` 让 daemon 发,否则话题、加密态、
|
|
281
|
+
`request_id` 都会错。
|
|
282
|
+
3. **注意保留字只占两段形式**。`exttype` 设成 `list` 时 `services.list` 被内置抢走,
|
|
283
|
+
但 `services.list.create` 仍路由到你的包。
|
|
284
|
+
4. **不要指望服务调用带话题**。它不是聊天,没有 `threadId`。
|
|
285
|
+
5. **不要在一个包里给同一个 `type` 写两条 `listen`**。
|
|
286
|
+
6. **不要在两个包里写同一个 `type`**。两个包都会 invalid。
|
|
287
|
+
|
|
288
|
+
## 十三、相关文档
|
|
289
|
+
|
|
290
|
+
| 文档 | 用途 |
|
|
291
|
+
| --- | --- |
|
|
292
|
+
| `$KITS_DOCS/evolcore/event-center.md` | 事件中心(广播通知,可能丢) |
|
|
293
|
+
| `$KITS_DOCS/evolcore/trigger.md` | 定时触发器,到点执行用这个 |
|
|
294
|
+
| `$KITS_DOCS/evolcore/aid.md` | 名片字段(`type` / `exttype`)怎么改 |
|
|
@@ -2,6 +2,8 @@
|
|
|
2
2
|
|
|
3
3
|
`ec task resume` 统一恢复暂停任务和基础设施异常中断任务。它定位已有会话并读取会话持久化的任务、路由、加密和 baseagent 绑定;恢复时继续原 provider 会话。
|
|
4
4
|
|
|
5
|
+
Codex 原 thread 保存的 Provider 与当前有效注册表选择不一致时,runner 会在提交恢复输入前备份并原位同步 rollout 和 SQLite 索引。原 Codex thread ID、EC 会话及恢复任务的代际校验保持不变;数据冲突或运行时无法释放时停止恢复,不新建替代 thread。详见 `provider.md`。
|
|
6
|
+
|
|
5
7
|
```text
|
|
6
8
|
ec task resume <sessionId>
|
|
7
9
|
ec task resume <sessionId> --format json
|
|
@@ -0,0 +1,41 @@
|
|
|
1
|
+
# `ec team`
|
|
2
|
+
|
|
3
|
+
Team Workspace 是每个 Agent 的共享产物区。默认目录为 `$EVOLCORE_HOME/agents/<agentAid>/workspace`,唯一绑定状态为 `$EVOLCORE_HOME/agents/<agentAid>/data/team-workspace-state.json`。初始化只由当前 Agent Owner 的 AUN 私聊按需触发,会创建 `capture/`、`output/` 和 `.workspace/marker.json`;导航不在工作区内保存副本。旧版 `$EVOLCORE_HOME/team-workspaces/<agentAid>` 仅在绑定仍指向该默认路径时自动迁移,目标目录已存在或身份 marker 不匹配时不会覆盖任何内容。
|
|
4
|
+
|
|
5
|
+
Agent 发布产物的常用流程是:确认文件已经写入工作区,读取现有导航,再按稳定 ID 增量发布。upsert 只新增或替换指定 ID,不会删除其他入口:
|
|
6
|
+
|
|
7
|
+
```bash
|
|
8
|
+
ec team navigation show
|
|
9
|
+
ec team navigation update --upsert-json '[{"id":"qa-report","title":"测试报告","path":"output/qa/report.md","kind":"file","order":30}]'
|
|
10
|
+
```
|
|
11
|
+
|
|
12
|
+
`id` 是后续更新和删除用的稳定键;同一产物更新标题、路径或排序时应复用原 ID。`path` 必须是已存在的工作区内相对路径,`kind` 只能是 `file` 或 `directory`,且必须与目标一致。命令不传 `--expected-revision` 时会读取当前 revision 后提交;并发写入发生冲突时,重新 `show`、合并变化后重试。需要固定基线时,可从 `show` 结果取 revision 显式传入。
|
|
13
|
+
|
|
14
|
+
删除入口必须显式指定稳定 ID;遗漏字段不会被解释为删除:
|
|
15
|
+
|
|
16
|
+
```bash
|
|
17
|
+
ec team navigation update --remove-ids-json '["qa-report"]'
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
只有有意重建整张导航时才使用 replace;它会删除 JSON 中没有列出的所有入口:
|
|
21
|
+
|
|
22
|
+
```bash
|
|
23
|
+
ec team navigation update --replace-json '[{"id":"capture","title":"输入资料","path":"capture","kind":"directory","order":10}]'
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
`upsert`、`remove` 和 `replace` 每次只允许选择一种模式。入口 ID 和路径必须各自唯一。暂时还不存在的目标可以通过 `availability: "unavailable"` 和 `reason` 先登记,目标就绪后再用相同 ID upsert 为正常入口。
|
|
27
|
+
|
|
28
|
+
成员配置保存在 Agent `config.json` 的 `team` AID 数组中。每个成员必须同时是当前 Agent 联系人簿中的 active AUN 私聊联系人;联系人簿由现有 Contact Book API 读取,当前落盘文件为 `peers.json`(旧 `contact.json` 已迁移)。Core 不接受群组、未接受或被阻止联系人:
|
|
29
|
+
|
|
30
|
+
```bash
|
|
31
|
+
ec team members show
|
|
32
|
+
ec team members update --members-json '["reviewer.agentid.cn","writer.agentid.cn"]'
|
|
33
|
+
```
|
|
34
|
+
|
|
35
|
+
App 可使用 `menu.query name=team-workspace args={view:"members",managementVersion:1}` 查询成员,以及 `menu.action` 的 `add-members`、`remove-members`、`replace-members` 管理成员。写操作必须传 `managementVersion:1`、`members` 数组和查询返回的 `membersRevision`(作为 `expectedRevision`);版本过期返回 `CONFLICT`。成员仍只存于当前 Agent 的 `config.json.team`。Menu 查询结合联系人信息展示名称与状态,允许 Owner 移除失效联系人。
|
|
36
|
+
|
|
37
|
+
成员查询可作为 `menu.query name=menu args.view=queries` 的一项,与模型、Agent、Role 设置一次获取:`{itemId:"members",name:"team-workspace",args:{view:"members",managementVersion:1}}`。每项独立返回结果,members 仍只允许当前 Agent Owner 的 AUN 私聊。批量规则见 [Menu Protocol](menu-protocol.md)。
|
|
38
|
+
|
|
39
|
+
`team-workspace` Menu 只接受当前 Agent Owner 的 AUN 私聊请求。Owner 校验来自已验证的 `principalId` 和 Ownership;普通成员、群聊、控制通道和参数中自报的 AID 都不能打开 Menu 或获得 fileRoot。Menu 协议为 `evol.team-workspace`,管理视图为 `evol.team-workspace-management`。App 请求参数、响应结构、文件访问和初始化轮询见 [Team Workspace Menu 协议 v1](../../../docs/personal-assistant/team-workspace-v1/menu-protocol.md)。
|
|
40
|
+
|
|
41
|
+
`ec team` CLI 也要求当前会话是该 Agent Owner 的 AUN 私聊。命令只输出 JSON,适合 Agent 通过当前受管会话调用;它不会接受调用者自行传入目标 AID。初始化命令为 `ec team workspace init [--workspace <绝对路径>]`;导航操作需要已初始化的工作区,成员配置读写不依赖工作区初始化。
|
|
@@ -133,16 +133,28 @@ ec thread delete <threadId> # 软删除:session 文件移入 _trash/,索
|
|
|
133
133
|
|
|
134
134
|
删除后历史仍可通过 `ec thread history <threadId>` 读取(直接读 messages.jsonl,不依赖索引)。
|
|
135
135
|
|
|
136
|
-
##
|
|
136
|
+
## 跨话题发送(话题链核心)
|
|
137
137
|
|
|
138
|
-
|
|
138
|
+
跨话题发送分两种:
|
|
139
|
+
|
|
140
|
+
| 形态 | 写法 | 目标 | 用途 |
|
|
141
|
+
|---|---|---|---|
|
|
142
|
+
| 跨话题委派 | `ecmsg send '<text>' --thread <话题id>` | 该话题的对端 | 把任务交给另一个话题里的对端推进 |
|
|
143
|
+
| 跨话题自派 | `ecmsg send '<text>' --thread <话题id> --to <本端AID>` | 该话题下的本端自己 | 对端是人、不会自己推进时,由本端自己接手 |
|
|
144
|
+
|
|
145
|
+
不带 `--thread` 的 `ecmsg send '<text>'` 是普通回复,只发当前会话对端/群。
|
|
146
|
+
|
|
147
|
+
跨话题自派的派活通知按话题对端类型送达:对端是人类时发普通 text,对端是 agent 时发 notice(`subtype=self_dispatch`),避免被当成一条要执行的聊天消息。
|
|
139
148
|
|
|
140
149
|
```bash
|
|
141
|
-
#
|
|
150
|
+
# 跨话题委派(本端/对端由话题推断)
|
|
142
151
|
ecmsg send '<消息内容>' --thread <threadId>
|
|
143
152
|
|
|
144
153
|
# 自定义复查周期(缺省 20m)
|
|
145
154
|
ecmsg send '<消息内容>' --thread <threadId> --check-every 30m
|
|
155
|
+
|
|
156
|
+
# 跨话题自派(投给该话题下的本端自己)
|
|
157
|
+
ecmsg send '<消息内容>' --thread <threadId> --to <本端AID>
|
|
146
158
|
```
|
|
147
159
|
|
|
148
160
|
注意事项:
|
package/kits/eck_manifest.json
CHANGED
|
@@ -72,6 +72,32 @@
|
|
|
72
72
|
},
|
|
73
73
|
"description": "本机技能"
|
|
74
74
|
},
|
|
75
|
+
{
|
|
76
|
+
"id": "services-index",
|
|
77
|
+
"type": "file",
|
|
78
|
+
"file": "$AGENT_DIR/services/.index.md",
|
|
79
|
+
"order": 20.65,
|
|
80
|
+
"needsInjection": false,
|
|
81
|
+
"optional": true,
|
|
82
|
+
"when": {
|
|
83
|
+
"var": "hasServicePacks",
|
|
84
|
+
"eq": true
|
|
85
|
+
},
|
|
86
|
+
"description": "可用服务清单"
|
|
87
|
+
},
|
|
88
|
+
{
|
|
89
|
+
"id": "events-index",
|
|
90
|
+
"type": "file",
|
|
91
|
+
"file": "$AGENT_DIR/events/.index.md",
|
|
92
|
+
"order": 20.7,
|
|
93
|
+
"needsInjection": false,
|
|
94
|
+
"optional": true,
|
|
95
|
+
"when": {
|
|
96
|
+
"var": "hasEventPacks",
|
|
97
|
+
"eq": true
|
|
98
|
+
},
|
|
99
|
+
"description": "已订阅事件清单"
|
|
100
|
+
},
|
|
75
101
|
{
|
|
76
102
|
"id": "soul",
|
|
77
103
|
"type": "directory",
|
|
@@ -29,6 +29,15 @@
|
|
|
29
29
|
|
|
30
30
|
> ⚠️ **只有上表这些别名能在 manifest 的** `path` **字段里用**。
|
|
31
31
|
|
|
32
|
+
### Agent 产物目录
|
|
33
|
+
|
|
34
|
+
面向 Owner 交付、需要在 App 助理团队产物入口浏览的文件,保存到当前 Agent 的
|
|
35
|
+
`$AGENT_DIR/output/`(即 `$EVOLCORE_HOME/agents/<selfAid>/output/`),可按任务建立子目录。
|
|
36
|
+
此目录随 Agent 固定,不随当前项目或个人助理工作区切换。App 对每个 Agent 分别通过
|
|
37
|
+
`agent-data-root` 和 `file` Menu 读取;加入助理团队不改变目标 Agent 的访问权限。
|
|
38
|
+
项目源码和工作文件仍按任务指定位置保存。已注册工作区的旧 `output/` 会在初始化时
|
|
39
|
+
迁入 Agent 的 `output/`,旧位置保留兼容目录链接;原栏目注册和逻辑路径继续有效。
|
|
40
|
+
|
|
32
41
|
## 路径注册表机制
|
|
33
42
|
|
|
34
43
|
路径用 `$名称` 引用,不写死实际路径。
|
|
@@ -84,4 +93,4 @@ agent 级索引范围:`$CURRENT_PROJECT` + `$AGENT_DIR`。
|
|
|
84
93
|
> 源码中也**没有任何地方读回它们**。要真实路径就按上面 1-3 步自己算,
|
|
85
94
|
> 或直接读 `src/paths.ts`。
|
|
86
95
|
|
|
87
|
-
参数加载优先级:evolcore 动态注入 > 环境变量 > 硬编码默认值。
|
|
96
|
+
参数加载优先级:evolcore 动态注入 > 环境变量 > 硬编码默认值。
|
package/kits/rules/06-channel.md
CHANGED
|
@@ -24,6 +24,7 @@
|
|
|
24
24
|
- interactive:直接输出即回复
|
|
25
25
|
- proactive:用 `ecmsg send` 正式回复,见 `[reply]` 段
|
|
26
26
|
- **发消息只有 `ecmsg` 一个入口**:文字、文件、图片、语音、链接、@某人、加密、联系第三方,全部用 `ecmsg send`。本端恒为当前会话本端,无需指定
|
|
27
|
+
- **跨话题发送分两种**:`--thread <话题id>` 是**跨话题委派**,目标是该话题的对端;`--thread <话题id> --to <本端AID>` 是**跨话题自派**,目标是该话题下的本端自己,用于「对端是人、不会自己推进」的分叉场景
|
|
27
28
|
|
|
28
29
|
### 命令返回值
|
|
29
30
|
|
package/kits/schemas/_meta.json
CHANGED
|
@@ -11,12 +11,17 @@
|
|
|
11
11
|
"history": []
|
|
12
12
|
},
|
|
13
13
|
"agent-config": {
|
|
14
|
-
"currentVersion":
|
|
14
|
+
"currentVersion": 20,
|
|
15
15
|
"history": [
|
|
16
|
+
{
|
|
17
|
+
"version": 20,
|
|
18
|
+
"date": "2026-11-07",
|
|
19
|
+
"description": "新增 Team Workspace 成员 team 配置"
|
|
20
|
+
},
|
|
16
21
|
{
|
|
17
22
|
"version": 19,
|
|
18
23
|
"date": "2026-11-05",
|
|
19
|
-
"description": "
|
|
24
|
+
"description": "私聊支持 interactive/proactive;群聊固定 proactive;PA activity 自动按身份投递"
|
|
20
25
|
},
|
|
21
26
|
{
|
|
22
27
|
"version": 18,
|
|
@@ -41,7 +46,7 @@
|
|
|
41
46
|
{
|
|
42
47
|
"version": 12,
|
|
43
48
|
"date": "2026-11-05",
|
|
44
|
-
"description": "
|
|
49
|
+
"description": "私聊支持 interactive/proactive;群聊固定 proactive;PA activity 自动按身份投递"
|
|
45
50
|
},
|
|
46
51
|
{
|
|
47
52
|
"version": 11,
|
|
@@ -74,19 +79,25 @@
|
|
|
74
79
|
"schema": "role-config",
|
|
75
80
|
"version": 2,
|
|
76
81
|
"date": "2026-11-05",
|
|
77
|
-
"description": "
|
|
82
|
+
"description": "私聊角色策略支持 interactive/proactive;群聊固定 proactive,兼容 v1 角色读取"
|
|
78
83
|
},
|
|
79
84
|
{
|
|
80
85
|
"schema": "relation-config",
|
|
81
86
|
"version": 12,
|
|
82
87
|
"date": "2026-11-05",
|
|
83
|
-
"description": "
|
|
88
|
+
"description": "私聊支持 interactive/proactive;群聊固定 proactive;PA activity 自动按身份投递"
|
|
89
|
+
},
|
|
90
|
+
{
|
|
91
|
+
"schema": "agent-config",
|
|
92
|
+
"version": 20,
|
|
93
|
+
"date": "2026-11-07",
|
|
94
|
+
"description": "新增 Team Workspace 成员 team 配置"
|
|
84
95
|
},
|
|
85
96
|
{
|
|
86
97
|
"schema": "agent-config",
|
|
87
98
|
"version": 19,
|
|
88
99
|
"date": "2026-11-05",
|
|
89
|
-
"description": "
|
|
100
|
+
"description": "私聊支持 interactive/proactive;群聊固定 proactive;PA activity 自动按身份投递"
|
|
90
101
|
},
|
|
91
102
|
{
|
|
92
103
|
"schema": "agent-config",
|
|
@@ -46,7 +46,7 @@
|
|
|
46
46
|
"const": 19,
|
|
47
47
|
"default": 19,
|
|
48
48
|
"x-merge": "scalar",
|
|
49
|
-
"description": "配置 Schema
|
|
49
|
+
"description": "配置 Schema 版本;私聊支持 interactive/proactive,群聊固定 proactive"
|
|
50
50
|
},
|
|
51
51
|
"aid": {
|
|
52
52
|
"type": "string",
|
|
@@ -681,14 +681,12 @@
|
|
|
681
681
|
"private": {
|
|
682
682
|
"enum": [
|
|
683
683
|
"interactive",
|
|
684
|
-
"proactive"
|
|
685
|
-
"paactive"
|
|
684
|
+
"proactive"
|
|
686
685
|
],
|
|
687
686
|
"description": "人类私聊场景的投递方式",
|
|
688
687
|
"x-enumDescriptions": {
|
|
689
688
|
"interactive": "同步交互:输出即回复",
|
|
690
|
-
"proactive": "主动推送:CLI 回复 + 思考投影"
|
|
691
|
-
"paactive": "PA 模式:文本作为 activity,正式回复使用 CLI"
|
|
689
|
+
"proactive": "主动推送:CLI 回复 + 思考投影"
|
|
692
690
|
}
|
|
693
691
|
},
|
|
694
692
|
"group": {
|
|
@@ -713,7 +711,7 @@
|
|
|
713
711
|
}
|
|
714
712
|
},
|
|
715
713
|
"additionalProperties": false,
|
|
716
|
-
"description": "场景投递表:私聊支持 interactive/proactive
|
|
714
|
+
"description": "场景投递表:私聊支持 interactive/proactive;群聊及非人类私聊固定 proactive。个人助理与本人 Owner 的 AUN 私聊中,proactive activity 自动使用消息投递。"
|
|
717
715
|
},
|
|
718
716
|
"mentionMode": {
|
|
719
717
|
"type": "string",
|
|
@@ -776,7 +774,7 @@
|
|
|
776
774
|
],
|
|
777
775
|
"default": "all",
|
|
778
776
|
"x-merge": "scalar",
|
|
779
|
-
"description": "中间输出展示范围;群聊 proactive 默认 none
|
|
777
|
+
"description": "中间输出展示范围;群聊 proactive 默认 none,显式配置可覆盖。",
|
|
780
778
|
"x-enumDescriptions": {
|
|
781
779
|
"all": "文本 + activity",
|
|
782
780
|
"text": "仅文本",
|