nikou-cli 0.1.17 → 0.1.18
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/README.md +7 -5
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -168,21 +168,23 @@ Hook 支持三种启动模式：
|
|
|
168
168
|
|
|
169
169
|
| 角色 | 运行内容 | 部署边界 |
|
|
170
170
|
| --- | --- | --- |
|
|
171
|
-
|
|
|
172
|
-
|
|
|
171
|
+
| 知识库宿主机主节点 | 飞书接入、任务路由、Worker 注册 | 与知识库 Worker 部署在同一台知识库宿主机，不按树莓派处理 |
|
|
172
|
+
| 知识库宿主机 Worker | Claude Worker、知识库群聊任务 | 唯一的知识库 Claude Worker，关闭单聊路由 |
|
|
173
173
|
| 个人节点 | Kiro/Codex 等个人 Worker | 仅处理对应宿主的单聊和绑定任务 |
|
|
174
174
|
|
|
175
|
-
|
|
175
|
+
当前知识库宿主机同时托管主节点和唯一的知识库 Worker，两个 systemd 服务均配置为开机自启。发布新版本后，在同一台知识库宿主机安装对应版本，并按顺序重启两个服务：
|
|
176
176
|
|
|
177
177
|
```bash
|
|
178
178
|
npm install -g nikou-cli@<version> --force --registry=https://registry.npmjs.org/
|
|
179
179
|
nikou-cli --version
|
|
180
|
+
systemctl restart com.vangelis.agent-block.hook.master.service
|
|
180
181
|
systemctl restart ai-hook-claude.service
|
|
181
|
-
systemctl is-
|
|
182
|
+
systemctl is-enabled com.vangelis.agent-block.hook.master.service ai-hook-claude.service
|
|
183
|
+
systemctl is-active com.vangelis.agent-block.hook.master.service ai-hook-claude.service
|
|
182
184
|
node -e 'const s=require("/root/.nikou-block/state/worker.json"); console.log({pid:s.pid,status:s.status,engine:s.engine,slaveConnectionStatus:s.slaveConnectionStatus})'
|
|
183
185
|
```
|
|
184
186
|
|
|
185
|
-
|
|
187
|
+
验收时应确认两个服务均为 `enabled/active`，主节点监听端口和状态文件正常，Worker 使用目标版本、`engine=claude`、`slaveConnectionStatus=online`，并在主节点日志中确认该 Worker 的 `p2p_enabled=false`。同时确认不存在旧的 `ai-hook-knowledge.service`，以及主节点上只有这一个知识库 Claude Worker。FastGPT/知识库平台容器按各自仓库与服务说明单独部署。
|
|
186
188
|
|
|
187
189
|
群聊发送 `@机器人 绑定: <目录>` 时，主节点会先检查当前用户是否已经绑定该目录；已有绑定会直接返回当前绑定状态卡片。当前用户已有其他目录时，会通过卡片确认“覆盖原绑定”或“新增绑定目录”；覆盖操作会在新目录校验成功后再撤销旧绑定。一个群可以保留多个用户、多个目录的 Agent 绑定，绑定指令不会广播给其他 Worker 抢占。
|
|
188
190
|
|