dsh-loop-engine 1.0.0-rc12 → 1.0.0-rc14
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 +3 -5
- package/README.zh.md +13 -0
- package/lib/client.js +88 -36919
- package/lib/index.js +149 -81
- package/package.json +2 -1
package/README.md
CHANGED
|
@@ -34,12 +34,10 @@ matched — a mismatch fails loudly at boot or session resume:
|
|
|
34
34
|
|
|
35
35
|
| dsh-loop-engine | Requires harness |
|
|
36
36
|
|---|---|
|
|
37
|
-
| 1.0.0-
|
|
38
|
-
| 1.0.0-
|
|
39
|
-
| 1.0.0-rc10 | **0.1.2-rc.1** |
|
|
40
|
-
| 1.0.0-rc7 | 0.1.1-rc.2 |
|
|
37
|
+
| 1.0.0-rc8 and later | **0.1.2-rc.1** |
|
|
38
|
+
| 1.0.0-rc7 and earlier | 0.1.1-rc.2 |
|
|
41
39
|
|
|
42
|
-
- **1.0.0-
|
|
40
|
+
- **1.0.0-rc8 and later is not compatible with harness 0.1.1-rc.2 or earlier.** It uses
|
|
43
41
|
the 0.1.2 persistence seam (`SessionPersistence.create` / `open` +
|
|
44
42
|
`SessionHandle`), the `installSection` settings API, `ToolCallId`, and
|
|
45
43
|
`Session.snapshotEvents()` — none of which exist in older harnesses.
|
package/README.zh.md
CHANGED
|
@@ -21,6 +21,19 @@ dsh plugin --profile web add dsh-loop-engine
|
|
|
21
21
|
- 使用 Pi 引擎时需要以 `pi` 要求的方式完成认证(其自身的 `~/.pi/agent/auth.json`,或提供方的 API-key 环境变量,如 `ANTHROPIC_API_KEY`)。
|
|
22
22
|
- 使用 Kimi Code 引擎时需要本机已安装并登录 `kimi` CLI(例如 `kimi login`),且在 `PATH` 上(或在组合条目里用 `kimiBin` 固定为绝对路径)。
|
|
23
23
|
|
|
24
|
+
## 版本兼容
|
|
25
|
+
|
|
26
|
+
`dsh-loop-engine` 与 harness **独立**版本(`1.0.0-rcN`),但通过 `peerDependencies` 绑定到特定 harness 版本;两者必须匹配——不匹配会在启动或会话恢复时响亮地失败:
|
|
27
|
+
|
|
28
|
+
| dsh-loop-engine | 需要 harness |
|
|
29
|
+
|---|---|
|
|
30
|
+
| 1.0.0-rc8 及以后 | **0.1.2-rc.1** |
|
|
31
|
+
| 1.0.0-rc7 及更早 | 0.1.1-rc.2 |
|
|
32
|
+
|
|
33
|
+
- **1.0.0-rc8 及以后不兼容 harness 0.1.1-rc.2 或更早版本。** 它使用 0.1.2 的持久化 seam(`SessionPersistence.create` / `open` + `SessionHandle`)、`installSection` settings API、`ToolCallId` 与 `Session.snapshotEvents()` —— 这些在更老的 harness 里都不存在。
|
|
34
|
+
- 要在更老的 harness 上使用本插件,请安装与之匹配的 loop-engine 版本(例如 harness 0.1.1-rc.2 用 `npm i dsh-loop-engine@1.0.0-rc7`)。
|
|
35
|
+
- 每个 tag 的 GitHub Release 正文会写明它针对的 harness 版本。
|
|
36
|
+
|
|
24
37
|
## 使用方法
|
|
25
38
|
|
|
26
39
|
1. 在 **Settings → Loop engine** 选择引擎——`in-process`(默认)、`claude-code`、`codex`、`pi` 或 `kimi`——然后重启 `dsh web`。
|