@zoraxylia/dsh-codex-adapter 0.1.0 → 0.1.1

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 (66) hide show
  1. package/.claude-plugin/marketplace.json +2 -2
  2. package/.claude-plugin/plugin.json +2 -2
  3. package/.mcp.json +1 -1
  4. package/README.de.md +32 -32
  5. package/README.es.md +32 -32
  6. package/README.fr.md +32 -32
  7. package/README.hi.md +32 -32
  8. package/README.id.md +32 -32
  9. package/README.ja.md +32 -32
  10. package/README.ko.md +32 -32
  11. package/README.md +33 -33
  12. package/README.pt.md +32 -32
  13. package/README.ru.md +32 -32
  14. package/README.th.md +32 -32
  15. package/README.tr.md +32 -32
  16. package/README.vi.md +32 -32
  17. package/README.zh-TW.md +32 -32
  18. package/README.zh.md +33 -33
  19. package/agy/agents/ds-flash.md +1 -1
  20. package/agy/agents/ds-pro.md +1 -1
  21. package/agy/skills/dsh-playbook/SKILL.md +1 -1
  22. package/codex/agents/ds-flash.toml +2 -2
  23. package/codex/agents/ds-pro.toml +2 -2
  24. package/codex/prompts/dsh-playbook.md +1 -1
  25. package/commands/off.md +1 -1
  26. package/commands/playbook.md +1 -1
  27. package/cordis.patch.yml +2 -2
  28. package/grok/agents/ds-flash.md +1 -1
  29. package/grok/agents/ds-pro.md +1 -1
  30. package/grok/commands/dsh-config.md +1 -1
  31. package/grok/commands/dsh-playbook.md +2 -2
  32. package/grok/commands/dsh-status.md +1 -1
  33. package/lib/client.js +37 -27
  34. package/lib/server.mjs +22 -22
  35. package/package.json +6 -5
  36. package/scripts/bump-version.mjs +79 -0
  37. package/scripts/fake-agy.sh +3 -3
  38. package/scripts/release-local.mjs +2 -2
  39. package/scripts/smoke-bundle.mjs +2 -2
  40. package/scripts/smoke-pack.mjs +4 -4
  41. package/scripts/smoke.mjs +3 -3
  42. package/scripts/verify-wpc10-client.mjs +2 -2
  43. package/scripts/verify-wpc14-proc-endpoints.mjs +6 -6
  44. package/scripts/verify-wpc9-guardrails.mjs +10 -10
  45. package/src/cli-workers.mjs +1 -1
  46. package/src/client/index.tsx +34 -32
  47. package/src/cwd-lock.mjs +1 -1
  48. package/src/hub/index.mjs +10 -10
  49. package/src/hub-client.mjs +4 -4
  50. package/src/install/install.mjs +35 -32
  51. package/src/jobs.mjs +2 -2
  52. package/src/multimodal.mjs +18 -18
  53. package/src/origin-guard.mjs +8 -8
  54. package/src/plugin-env.mjs +2 -2
  55. package/src/proc-kill.mjs +5 -5
  56. package/src/provider-probe.mjs +3 -3
  57. package/src/server.mjs +4 -4
  58. package/src/status-shard.mjs +2 -2
  59. package/src/vision-route.mjs +3 -3
  60. package/statusline/statusline.sh +1 -1
  61. package/statusline/worker-segment.sh +3 -3
  62. package/worker.cordis.yml +1 -1
  63. /package/docs/images/{dsh-crew-host.png → dsh-adapter-host.png} +0 -0
  64. /package/docs/images/{dsh-crew-jobs.png → dsh-adapter-jobs.png} +0 -0
  65. /package/docs/images/{dsh-crew-logo.png → dsh-adapter-logo.png} +0 -0
  66. /package/docs/images/{dsh-crew-overview.png → dsh-adapter-overview.png} +0 -0
package/README.zh.md CHANGED
@@ -1,11 +1,11 @@
1
1
  <p align="center">
2
- <img src="./docs/images/dsh-crew-logo.png" alt="DSH Crew" width="120" />
2
+ <img src="./docs/images/dsh-adapter-logo.png" alt="DSH Adapter" width="120" />
3
3
  </p>
4
4
 
5
- <h1 align="center">DSH Crew</h1>
5
+ <h1 align="center">DSH Adapter</h1>
6
6
 
7
7
  <p align="center">
8
- <sub><a href="https://github.com/ZSeven-W/dsh-crew">dsh-crew</a>(MIT)的独立分支 &mdash; 见 <a href="./NOTICE">NOTICE</a>。</sub>
8
+ <sub><a href="https://github.com/ZSeven-W/dsh-crew">dsh-adapter</a>(MIT)的独立分支 &mdash; 见 <a href="./NOTICE">NOTICE</a>。</sub>
9
9
  </p>
10
10
 
11
11
  <p align="center">
@@ -28,13 +28,13 @@
28
28
  <br />
29
29
 
30
30
  <p align="center">
31
- <img src="./docs/images/dsh-crew-overview.png" alt="DSH Crew 设置页" width="100%" />
31
+ <img src="./docs/images/dsh-adapter-overview.png" alt="DSH Adapter 设置页" width="100%" />
32
32
  </p>
33
- <p align="center"><sub>DSH Crew 设置页 —— 宿主集成、派发策略、执行方式与多模态桥</sub></p>
33
+ <p align="center"><sub>DSH Adapter 设置页 —— 宿主集成、派发策略、执行方式与多模态桥</sub></p>
34
34
 
35
- ## 为什么用 DSH Crew
35
+ ## 为什么用 DSH Adapter
36
36
 
37
- DSH Crew 是 [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness)(DSH,开源 agent harness)的插件,它让 DSH agent 可以从 Claude Code、Codex、Antigravity 与 Grok 里被派活:orchestrator 的模型不变,活由真正的 DSH agent 去干——用的是这套 harness 的工具、沙箱、预设与会话历史——而在宿主里它仍然是一个带实时进度的原生子代理。
37
+ DSH Adapter 是 [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness)(DSH,开源 agent harness)的插件,它让 DSH agent 可以从 Claude Code、Codex、Antigravity 与 Grok 里被派活:orchestrator 的模型不变,活由真正的 DSH agent 去干——用的是这套 harness 的工具、沙箱、预设与会话历史——而在宿主里它仍然是一个带实时进度的原生子代理。
38
38
 
39
39
  干活的是 DSH agent,不是一次裸的模型调用。档位(`flash` / `pro`)决定这个 agent 从 harness 已配置的模型阵容里拿到多强的能力(目前是 DeepSeek V4 Flash 与 V4 Pro)——DSH 那边换模型,这边不用改。
40
40
 
@@ -83,7 +83,7 @@ DSH 用的模型是纯文本的。`describe_image` 现在只要有 key 就优先
83
83
 
84
84
  ### 📋 任务看板
85
85
 
86
- DSH Crew 面板同时是任务看板:每个 worker 任务——运行中或已结束——都带着档位、effort、实时进度与 token 列在板上,被持有的 workspace 会显示持有者;中途消失的任务(比如 hub 重启)会作为孤儿 ghost 浮出,而不是无声消失。
86
+ DSH Adapter 面板同时是任务看板:每个 worker 任务——运行中或已结束——都带着档位、effort、实时进度与 token 列在板上,被持有的 workspace 会显示持有者;中途消失的任务(比如 hub 重启)会作为孤儿 ghost 浮出,而不是无声消失。
87
87
 
88
88
  </td>
89
89
  </tr>
@@ -122,14 +122,14 @@ Claude Code / Codex / Antigravity / Grok(orchestrator,模型不变)
122
122
  派发是可以铺开的。下面这次,18 个 worker 并行翻译这份 README:宿主把它们算作自己的子代理,harness 则把它们当作真实会话来跑。
123
123
 
124
124
  <p align="center">
125
- <img src="./docs/images/dsh-crew-host.png" alt="Claude Code" width="100%" />
125
+ <img src="./docs/images/dsh-adapter-host.png" alt="Claude Code" width="100%" />
126
126
  </p>
127
- <p align="center"><sub>Claude Code 里,dsh-crew worker 就是原生子代理;状态栏段实时显示在跑的档位、耗时与 token。</sub></p>
127
+ <p align="center"><sub>Claude Code 里,dsh-adapter worker 就是原生子代理;状态栏段实时显示在跑的档位、耗时与 token。</sub></p>
128
128
 
129
129
  <p align="center">
130
- <img src="./docs/images/dsh-crew-jobs.png" alt="DSH Crew" width="100%" />
130
+ <img src="./docs/images/dsh-adapter-jobs.png" alt="DSH Adapter" width="100%" />
131
131
  </p>
132
- <p align="center"><sub>DSH Crew 面板从 harness 一侧看同一次运行:每个任务由哪个宿主派出、档位与推理强度、实时进度与 token 消耗。</sub></p>
132
+ <p align="center"><sub>DSH Adapter 面板从 harness 一侧看同一次运行:每个任务由哪个宿主派出、档位与推理强度、实时进度与 token 消耗。</sub></p>
133
133
 
134
134
  <p align="center"><sub>面板同时是任务看板:运行中与已结束的任务都带着档位、进度与 token 留在板上,被持有的 workspace 会标出持有者,中途消失的任务(hub 重启)会作为孤儿 ghost 浮出,而不是无声消失。</sub></p>
135
135
 
@@ -145,7 +145,7 @@ dsh web
145
145
  或者从源码树本地开发:
146
146
 
147
147
  ```bash
148
- dsh plugin --profile web add link:/path/to/dsh-crew
148
+ dsh plugin --profile web add link:/path/to/dsh-adapter
149
149
  dsh web
150
150
  ```
151
151
 
@@ -155,7 +155,7 @@ dsh web
155
155
 
156
156
  在 hub 模式下 — 即上面的安装方式 — worker 运行在 DSH 实例内部,使用 DSH 实例已配置的 DeepSeek 凭据。无需额外设置。
157
157
 
158
- 仅 standalone 回落方案需要自己的 key:从宿主派发任务而没有 DSH 实例运行时,会启动一个独立的 worker runtime 进程。从 [platform.deepseek.com](https://platform.deepseek.com) 取 API key,写入 `~/.config/dsh-crew/.env`:
158
+ 仅 standalone 回落方案需要自己的 key:从宿主派发任务而没有 DSH 实例运行时,会启动一个独立的 worker runtime 进程。从 [platform.deepseek.com](https://platform.deepseek.com) 取 API key,写入 `~/.config/dsh-adapter/.env`:
159
159
 
160
160
  ```
161
161
  DEEPSEEK_API_KEY=sk-...
@@ -169,7 +169,7 @@ node scripts/smoke.mjs
169
169
 
170
170
  smoke 测试会挑一条可用的路径派一个廉价任务——DSH 实例在跑就走 hub,否则走 standalone——并打印实际用的是哪条。十几秒内看到 `smoke test passed — configuration OK` 即配置成功。失败会打印具体原因,且只针对实际测的那条路径。
171
171
 
172
- 然后打开 设置 → DSH Crew,一键装好宿主集成——Claude Code、Codex、Antigravity、Grok,或用命令行驱动同一个安装器:
172
+ 然后打开 设置 → DSH Adapter,一键装好宿主集成——Claude Code、Codex、Antigravity、Grok,或用命令行驱动同一个安装器:
173
173
 
174
174
  ```bash
175
175
  node src/install/cli.mjs claude # Claude Code 插件:marketplace + 权限白名单 + HUD 状态段
@@ -196,7 +196,7 @@ node src/install/cli.mjs uninstall-claude
196
196
 
197
197
  一键安装(二选一):
198
198
 
199
- - **DSH 设置页**(已装 hub 模式时):设置 → DSH Crew → "安装到 Claude Code"
199
+ - **DSH 设置页**(已装 hub 模式时):设置 → DSH Adapter → "安装到 Claude Code"
200
200
  - **命令行**:`node src/install/cli.mjs all`
201
201
 
202
202
  两者做同样的事:注册本地 marketplace(父目录 `dsh-plugins/` 为 marketplace 根) + `claude plugin install` + MCP 工具权限白名单 + claude-hud worker 状态段配置(改动前自动备份 settings.json,幂等)。**安装后重启会话生效**。
@@ -208,7 +208,7 @@ node src/install/cli.mjs uninstall-claude
208
208
  - **HUD 状态栏段**:`⚙dsh 1▶pro 2m14s 21.7k/606 ✓3`(当前档位 / 耗时 / token 占用 / 完成计数)
209
209
  - 本地开发用 `statusline/statusline.sh` 或 `statusline/worker-segment.sh` 可独立集成
210
210
  - **超长任务**:CC 对 MCP 调用有超时限制(`MCP_TOOL_TIMEOUT` 可调),长任务可让 orchestrator 用 `dsh_spawn_worker` + `dsh_worker_result(wait_seconds)` 轮询
211
- - **本地开发调试**:`claude --plugin-dir /path/to/dsh-crew` 临时加载
211
+ - **本地开发调试**:`claude --plugin-dir /path/to/dsh-adapter` 临时加载
212
212
 
213
213
 
214
214
  ### 会话命令
@@ -217,10 +217,10 @@ node src/install/cli.mjs uninstall-claude
217
217
 
218
218
  | 命令 | 作用 |
219
219
  |---|---|
220
- | `/dsh-crew:config` | 查看或设置本会话默认值:`tier=flash\|pro`、`effort=off\|high\|max`、`mode=auto\|hub\|standalone`、`timeout=<秒>`、`policy=auto\|flash-only\|pro-only`、`escalate=true\|false`、`origin_depth_limit=<1-32>`、`preset_flash/preset_pro=<preset id|default>`、`reset` |
221
- | `/dsh-crew:on` · `/dsh-crew:off` | 开关本会话的派发(关闭是硬开关,工具层直接拒绝) |
222
- | `/dsh-crew:status` | worker 任务实时状态:档位、进度、tokens、当前工具 |
223
- | `/dsh-crew:playbook` | 派发最佳实践:flash vs pro 选择、自包含任务简报、并行、结果验证、护栏 |
220
+ | `/dsh-adapter:config` | 查看或设置本会话默认值:`tier=flash\|pro`、`effort=off\|high\|max`、`mode=auto\|hub\|standalone`、`timeout=<秒>`、`policy=auto\|flash-only\|pro-only`、`escalate=true\|false`、`origin_depth_limit=<1-32>`、`preset_flash/preset_pro=<preset id|default>`、`reset` |
221
+ | `/dsh-adapter:on` · `/dsh-adapter:off` | 开关本会话的派发(关闭是硬开关,工具层直接拒绝) |
222
+ | `/dsh-adapter:status` | worker 任务实时状态:档位、进度、tokens、当前工具 |
223
+ | `/dsh-adapter:playbook` | 派发最佳实践:flash vs pro 选择、自包含任务简报、并行、结果验证、护栏 |
224
224
 
225
225
  ## Codex
226
226
 
@@ -270,7 +270,7 @@ Codex 侧装的是三条 prompt:
270
270
  node src/install/cli.mjs agy
271
271
  ```
272
272
 
273
- 把 dsh-crew MCP server 注册进 `~/.gemini/config/mcp_config.json`,并把 `ds-flash` / `ds-pro` agent 与 `dsh-config`、`dsh-status`、`dsh-playbook` skill 装进 `~/.gemini/config/`(改动前自动备份)。安装后重启会话生效。
273
+ 把 dsh-adapter MCP server 注册进 `~/.gemini/config/mcp_config.json`,并把 `ds-flash` / `ds-pro` agent 与 `dsh-config`、`dsh-status`、`dsh-playbook` skill 装进 `~/.gemini/config/`(改动前自动备份)。安装后重启会话生效。
274
274
 
275
275
  ### 使用
276
276
 
@@ -299,7 +299,7 @@ node src/install/cli.mjs agy
299
299
  node src/install/cli.mjs grok
300
300
  ```
301
301
 
302
- 把 `[mcp_servers.dsh-crew]` 段写入 `~/.grok/config.toml`,并把 `ds-flash` / `ds-pro` agent 与 `/dsh-config`、`/dsh-status`、`/dsh-playbook` 命令装进 `~/.grok/`(改动前自动备份)。
302
+ 把 `[mcp_servers.dsh-adapter]` 段写入 `~/.grok/config.toml`,并把 `ds-flash` / `ds-pro` agent 与 `/dsh-config`、`/dsh-status`、`/dsh-playbook` 命令装进 `~/.grok/`(改动前自动备份)。
303
303
 
304
304
  ### 使用
305
305
 
@@ -331,7 +331,7 @@ node src/install/cli.mjs grok
331
331
  | `dsh_worker_cancel` | 取消指定 job,终止其 runtime 进程 |
332
332
  | `dsh_worker_config` | 查看/设置本会话默认值(tier、effort、mode、timeout、policy、escalation),并列出 `worker_profiles` |
333
333
 
334
- 进度同时镜像到 `~/.config/dsh-crew/status.d/`(每个写入方一个分片文件,statusline / 外部监控可读)。
334
+ 进度同时镜像到 `~/.config/dsh-adapter/status.d/`(每个写入方一个分片文件,statusline / 外部监控可读)。
335
335
 
336
336
  ## 派发护栏
337
337
 
@@ -342,7 +342,7 @@ node src/install/cli.mjs grok
342
342
 
343
343
  ## 派发手册(playbook)
344
344
 
345
- 如何把活派好——flash vs pro、自包含任务简报、安全并行、结果验证,以及上面的护栏——随包按宿主分发:`/dsh-crew:playbook`(Claude Code skill)、`/dsh-playbook`(Codex prompt、Antigravity skill、Grok 命令)。
345
+ 如何把活派好——flash vs pro、自包含任务简报、安全并行、结果验证,以及上面的护栏——随包按宿主分发:`/dsh-adapter:playbook`(Claude Code skill)、`/dsh-playbook`(Codex prompt、Antigravity skill、Grok 命令)。
346
346
 
347
347
  ## 显式 CLI 后端
348
348
 
@@ -352,7 +352,7 @@ node src/install/cli.mjs grok
352
352
 
353
353
  **DeepSeek 是纯文本模型**,不支持图片输入与生图输出。本插件通过 MCP 工具把这两项能力外借过来:
354
354
 
355
- **原生视觉优先**:当视觉 provider 是内置 CLI(或显式 `native`)时,`describe_image` 会先试 DeepSeek 自己的视觉模型 `deepseek-v4-flash-vision-exp`(直接 API 调用;key 来自 `DEEPSEEK_API_KEY` 或 `~/.config/dsh-crew/.env`)。任何失败都会优雅回落到下面的 CLI provider 链,这条链原样保留作为兜底。生图不受影响——原生模型只看图。
355
+ **原生视觉优先**:当视觉 provider 是内置 CLI(或显式 `native`)时,`describe_image` 会先试 DeepSeek 自己的视觉模型 `deepseek-v4-flash-vision-exp`(直接 API 调用;key 来自 `DEEPSEEK_API_KEY` 或 `~/.config/dsh-adapter/.env`)。任何失败都会优雅回落到下面的 CLI provider 链,这条链原样保留作为兜底。生图不受影响——原生模型只看图。
356
356
 
357
357
  | 工具 | 说明 |
358
358
  |---|---|
@@ -363,7 +363,7 @@ node src/install/cli.mjs grok
363
363
 
364
364
  ### 配置
365
365
 
366
- 在 **DSH 设置页 → DSH Crew → 多模态**(或直接编辑 `~/.config/dsh-crew/config.json`)配置:
366
+ 在 **DSH 设置页 → DSH Adapter → 多模态**(或直接编辑 `~/.config/dsh-adapter/config.json`)配置:
367
367
 
368
368
  **视觉 provider**(看图):
369
369
 
@@ -407,15 +407,15 @@ node src/install/cli.mjs grok
407
407
 
408
408
  ## Hub 模式
409
409
 
410
- 本包同时是合法的 DSH bundle(`dsh.bundle` + `cordis.patch.yml`)。执行 `dsh plugin add dsh-crew` 装进 DSH Web profile 后:
410
+ 本包同时是合法的 DSH bundle(`dsh.bundle` + `cordis.patch.yml`)。执行 `dsh plugin add dsh-adapter` 装进 DSH Web profile 后:
411
411
 
412
412
  - **Worker 会话一等公民化**:以 first-class session 运行在 DSH host 里(`agents.create` + per-session model/effort waterfall + 默认 preset),出现在 Web UI 会话列表,随时可点开围观完整执行过程
413
413
  - **按工作目录归类**:Web UI 中按 cwd 管理 worker 会话
414
414
  - **Loopback API**:
415
- - `POST/GET /_dsh/dsh-crew/jobs`:spawn 任务、列表、长轮询结果、cancel
416
- - `GET /_dsh/dsh-crew/ping`:健康探测(MCP shim 靠它判断 hub 是否在跑)
417
- - `POST /_dsh/dsh-crew/install`:一键安装宿主集成——Claude Code / Codex / Antigravity / Grok(即 `src/install/` 的后端)
418
- - **自动探测**:各宿主的 MCP shim 自动探测 hub(`DSHPLUGIN_CREW_HUB` 环境变量,默认 `http://127.0.0.1:3080`)
415
+ - `POST/GET /_dsh/dsh-adapter/jobs`:spawn 任务、列表、长轮询结果、cancel
416
+ - `GET /_dsh/dsh-adapter/ping`:健康探测(MCP shim 靠它判断 hub 是否在跑)
417
+ - `POST /_dsh/dsh-adapter/install`:一键安装宿主集成——Claude Code / Codex / Antigravity / Grok(即 `src/install/` 的后端)
418
+ - **自动探测**:各宿主的 MCP shim 自动探测 hub(`DSHPLUGIN_ADAPTER_HUB` 环境变量,默认 `http://127.0.0.1:3080`)
419
419
  - DSH Web 在跑 → job 进 hub 模式(`mode: "hub"`)
420
420
  - 没跑 → 回落 standalone runtime
421
421
 
@@ -439,7 +439,7 @@ node src/install/cli.mjs grok
439
439
 
440
440
  ### 跑着 DSH Web → Hub 模式自动启用
441
441
 
442
- - **现状**:若 `dsh plugin add dsh-crew` 装进 DSH Web profile,job 以一等公民会话跑在 host 里,出现在 Web UI 会话列表
442
+ - **现状**:若 `dsh plugin add dsh-adapter` 装进 DSH Web profile,job 以一等公民会话跑在 host 里,出现在 Web UI 会话列表
443
443
  - **建议**:本地开发迭代时推荐启用 hub 模式,worker 进度可在 Web UI 完整围观;跨机器协作或无 Web UI 环境用派发宿主壳方案
444
444
 
445
445
  ### 已知事项
@@ -7,7 +7,7 @@ subagent: true
7
7
 
8
8
  You are a thin dispatcher. You NEVER do the task yourself.
9
9
 
10
- 1. Take the task you were given and pass it VERBATIM (plus any file paths / context you were given) to the `dsh_run_worker` tool (provided by the dsh-crew MCP server) with:
10
+ 1. Take the task you were given and pass it VERBATIM (plus any file paths / context you were given) to the `dsh_run_worker` tool (provided by the dsh-adapter MCP server) with:
11
11
  - `tier`: "flash"
12
12
  - `effort`: omit it entirely (the session/global default applies) unless the task explicitly names an effort level
13
13
  - `cwd`: the current project directory
@@ -7,7 +7,7 @@ subagent: true
7
7
 
8
8
  You are a thin dispatcher. You NEVER do the task yourself.
9
9
 
10
- 1. Take the task you were given and pass it VERBATIM (plus any file paths / context you were given) to the `dsh_run_worker` tool (provided by the dsh-crew MCP server) with:
10
+ 1. Take the task you were given and pass it VERBATIM (plus any file paths / context you were given) to the `dsh_run_worker` tool (provided by the dsh-adapter MCP server) with:
11
11
  - `tier`: "pro"
12
12
  - `effort`: omit it entirely (the session/global default applies) unless the task explicitly names an effort level
13
13
  - `cwd`: the current project directory
@@ -5,7 +5,7 @@ description: How to dispatch well — choosing flash vs pro, writing self-contai
5
5
 
6
6
  When the user asks how to dispatch work to DSH workers — tier choice, writing a brief, parallelism, verifying results, guardrails — answer from the playbook below. Point to the relevant section rather than reciting it whole.
7
7
 
8
- # DSH Crew — Dispatch Playbook
8
+ # DSH Adapter — Dispatch Playbook
9
9
 
10
10
  How to delegate work to DSH workers well. The tool descriptions carry the mechanics; this playbook is the decision layer.
11
11
 
@@ -16,8 +16,8 @@ You are a thin dispatcher. You NEVER do the task yourself.
16
16
  Do not edit files, run commands, or answer from your own knowledge.
17
17
  """
18
18
 
19
- [mcp_servers.dsh-crew]
19
+ [mcp_servers.dsh-adapter]
20
20
  command = "node"
21
- args = ["/Users/fini/workspace/dsh-plugins/dsh-crew/src/server.mjs"]
21
+ args = ["/Users/fini/workspace/dsh-plugins/dsh-adapter/src/server.mjs"]
22
22
  default_tools_approval_mode = "approve"
23
23
  tool_timeout_sec = 3600
@@ -16,8 +16,8 @@ You are a thin dispatcher. You NEVER do the task yourself.
16
16
  Do not edit files, run commands, or answer from your own knowledge.
17
17
  """
18
18
 
19
- [mcp_servers.dsh-crew]
19
+ [mcp_servers.dsh-adapter]
20
20
  command = "node"
21
- args = ["/Users/fini/workspace/dsh-plugins/dsh-crew/src/server.mjs"]
21
+ args = ["/Users/fini/workspace/dsh-plugins/dsh-adapter/src/server.mjs"]
22
22
  default_tools_approval_mode = "approve"
23
23
  tool_timeout_sec = 3600
@@ -1,6 +1,6 @@
1
1
  When the user asks how to dispatch work to DSH workers — tier choice, writing a brief, parallelism, verifying results, guardrails — answer from the playbook below. Point to the relevant section rather than reciting it whole.
2
2
 
3
- # DSH Crew — Dispatch Playbook
3
+ # DSH Adapter — Dispatch Playbook
4
4
 
5
5
  How to delegate work to DSH workers well. The tool descriptions carry the mechanics; this playbook is the decision layer.
6
6
 
package/commands/off.md CHANGED
@@ -2,4 +2,4 @@
2
2
  description: Disable DSH worker dispatch for this session (hard switch, enforced at the tool layer)
3
3
  ---
4
4
 
5
- Call the `dsh_worker_config` tool with `{"enabled": false}`. Then confirm in one sentence that worker dispatch is off for this session and that `/dsh-crew:on` turns it back on. Reply in the language the user is writing in. Do nothing else.
5
+ Call the `dsh_worker_config` tool with `{"enabled": false}`. Then confirm in one sentence that worker dispatch is off for this session and that `/dsh-adapter:on` turns it back on. Reply in the language the user is writing in. Do nothing else.
@@ -4,7 +4,7 @@ description: How to dispatch well — choosing flash vs pro, writing self-contai
4
4
 
5
5
  When the user asks how to dispatch work to DSH workers — tier choice, writing a brief, parallelism, verifying results, guardrails — answer from the playbook below. Point to the relevant section rather than reciting it whole.
6
6
 
7
- # DSH Crew — Dispatch Playbook
7
+ # DSH Adapter — Dispatch Playbook
8
8
 
9
9
  How to delegate work to DSH workers well. The tool descriptions carry the mechanics; this playbook is the decision layer.
10
10
 
package/cordis.patch.yml CHANGED
@@ -1,4 +1,4 @@
1
- # dsh-crew bundle patch: mounts the workers-hub host plugin into the profile.
1
+ # dsh-adapter bundle patch: mounts the workers-hub host plugin into the profile.
2
2
  - insert:
3
- - id: dsh-crew-hub
3
+ - id: dsh-adapter-hub
4
4
  name: '@zoraxylia/dsh-codex-adapter'
@@ -8,7 +8,7 @@ permission_mode: default
8
8
 
9
9
  You are a thin dispatcher. You NEVER do the task yourself.
10
10
 
11
- 1. Take the task you were given and pass it VERBATIM (plus any file paths / context you were given) to the `dsh-crew__dsh_run_worker` tool (the dsh-crew MCP server is registered as a user MCP server; its tools are namespaced `dsh-crew__<tool>`) with:
11
+ 1. Take the task you were given and pass it VERBATIM (plus any file paths / context you were given) to the `dsh-adapter__dsh_run_worker` tool (the dsh-adapter MCP server is registered as a user MCP server; its tools are namespaced `dsh-adapter__<tool>`) with:
12
12
  - `tier`: "flash"
13
13
  - `effort`: omit it entirely (the session/global default applies) unless the task explicitly names an effort level
14
14
  - `cwd`: the current project directory
@@ -8,7 +8,7 @@ permission_mode: default
8
8
 
9
9
  You are a thin dispatcher. You NEVER do the task yourself.
10
10
 
11
- 1. Take the task you were given and pass it VERBATIM (plus any file paths / context you were given) to the `dsh-crew__dsh_run_worker` tool (the dsh-crew MCP server is registered as a user MCP server; its tools are namespaced `dsh-crew__<tool>`) with:
11
+ 1. Take the task you were given and pass it VERBATIM (plus any file paths / context you were given) to the `dsh-adapter__dsh_run_worker` tool (the dsh-adapter MCP server is registered as a user MCP server; its tools are namespaced `dsh-adapter__<tool>`) with:
12
12
  - `tier`: "pro"
13
13
  - `effort`: omit it entirely (the session/global default applies) unless the task explicitly names an effort level
14
14
  - `cwd`: the current project directory
@@ -4,6 +4,6 @@ description: Show or set this session's DSH worker defaults (tier / effort / mod
4
4
 
5
5
  User input: $ARGUMENTS
6
6
 
7
- Parse the input into key=value pairs. Accepted keys: `enabled=true|false`, `tier=flash|pro`, `effort=off|high|max`, `mode=auto|hub|standalone`, `timeout=<seconds>`, `policy=auto|flash-only|pro-only`, `escalate=true|false`, `origin_depth_limit=<1-32>`, `preset_flash=<preset id|default>`, `preset_pro=<preset id|default>`, `reset`. Map them onto the `dsh-crew__dsh_worker_config` tool arguments (tier→default_tier, effort→default_effort, timeout→default_timeout_seconds, policy→tier_policy, escalate→escalate_on_failure, origin_depth_limit and preset_flash/preset_pro pass through unchanged) and call it. With no arguments, call the tool with no arguments to read the current configuration.
7
+ Parse the input into key=value pairs. Accepted keys: `enabled=true|false`, `tier=flash|pro`, `effort=off|high|max`, `mode=auto|hub|standalone`, `timeout=<seconds>`, `policy=auto|flash-only|pro-only`, `escalate=true|false`, `origin_depth_limit=<1-32>`, `preset_flash=<preset id|default>`, `preset_pro=<preset id|default>`, `reset`. Map them onto the `dsh-adapter__dsh_worker_config` tool arguments (tier→default_tier, effort→default_effort, timeout→default_timeout_seconds, policy→tier_policy, escalate→escalate_on_failure, origin_depth_limit and preset_flash/preset_pro pass through unchanged) and call it. With no arguments, call the tool with no arguments to read the current configuration.
8
8
 
9
9
  Then show the returned configuration (including `hub_reachable`) as one compact table, and name the fields that changed if anything did. Reply in the language the user is writing in. Do nothing else.
@@ -4,9 +4,9 @@ description: How to dispatch well — choosing flash vs pro, writing self-contai
4
4
 
5
5
  When the user asks how to dispatch work to DSH workers — tier choice, writing a brief, parallelism, verifying results, guardrails — answer from the playbook below. Point to the relevant section rather than reciting it whole.
6
6
 
7
- In this host the dsh-crew MCP tools are namespaced: wherever the playbook says `dsh_run_worker`, call `dsh-crew__dsh_run_worker`, and likewise for the other five tools.
7
+ In this host the dsh-adapter MCP tools are namespaced: wherever the playbook says `dsh_run_worker`, call `dsh-adapter__dsh_run_worker`, and likewise for the other five tools.
8
8
 
9
- # DSH Crew — Dispatch Playbook
9
+ # DSH Adapter — Dispatch Playbook
10
10
 
11
11
  How to delegate work to DSH workers well. The tool descriptions carry the mechanics; this playbook is the decision layer.
12
12
 
@@ -2,4 +2,4 @@
2
2
  description: Show live status of DSH worker jobs
3
3
  ---
4
4
 
5
- Call the `dsh-crew__dsh_worker_status` tool and present the result as one compact table: job id, tier/effort, status (including the current tool), progress, tokens, task summary. If there are no jobs, say so in one line. Reply in the language the user is writing in. Do nothing else.
5
+ Call the `dsh-adapter__dsh_worker_status` tool and present the result as one compact table: job id, tier/effort, status (including the current tool), progress, tokens, task summary. If there are no jobs, say so in one line. Reply in the language the user is writing in. Do nothing else.
package/lib/client.js CHANGED
@@ -341,9 +341,9 @@ function dueProcProbes(ghosts, probedAt, now) {
341
341
  //#endregion
342
342
  //#region src/client/index.tsx
343
343
  const inject = ["slots", "locale"];
344
- const API = "/_dsh/dsh-crew";
345
- const COLLAPSE_PREFIX = "dsh-crew.settings.collapse.";
346
- const WS_COLLAPSE_PREFIX = "dsh-crew.jobs.collapse.";
344
+ const API = "/_dsh/dsh-adapter";
345
+ const COLLAPSE_PREFIX = "dsh-adapter.settings.collapse.";
346
+ const WS_COLLAPSE_PREFIX = "dsh-adapter.jobs.collapse.";
347
347
  const collapseSessionMemory = {};
348
348
  function readCollapsed(key, defaultCollapsed = false) {
349
349
  let stored = null;
@@ -361,7 +361,7 @@ function persistCollapsed(key, collapsed) {
361
361
  collapseSessionMemory[key] = collapsed;
362
362
  }
363
363
  }
364
- const GHOST_STORE_KEY = "dsh-crew.jobs.ghosts";
364
+ const GHOST_STORE_KEY = "dsh-adapter.jobs.ghosts";
365
365
  const ghostSessionMemory = {};
366
366
  function readGhosts() {
367
367
  try {
@@ -380,7 +380,7 @@ function writeGhosts(ghosts) {
380
380
  Object.assign(ghostSessionMemory, ghosts);
381
381
  }
382
382
  }
383
- /** Section open state + toggle, persisted under dsh-crew.settings.collapse.<section>. */
383
+ /** Section open state + toggle, persisted under dsh-adapter.settings.collapse.<section>. */
384
384
  function useCollapseSection(section, defaultCollapsed = false) {
385
385
  const [collapsed, setCollapsed] = (0, react.useState)(() => readCollapsed(COLLAPSE_PREFIX + section, defaultCollapsed));
386
386
  return [collapsed, (0, react.useCallback)(() => {
@@ -389,7 +389,7 @@ function useCollapseSection(section, defaultCollapsed = false) {
389
389
  persistCollapsed(COLLAPSE_PREFIX + section, next);
390
390
  }, [section, collapsed])];
391
391
  }
392
- /** Per-workspace job-group collapse, persisted under dsh-crew.jobs.collapse.<workspaceKey> (WPC13). */
392
+ /** Per-workspace job-group collapse, persisted under dsh-adapter.jobs.collapse.<workspaceKey> (WPC13). */
393
393
  function useWorkspaceCollapse(wsKey) {
394
394
  const [collapsed, setCollapsed] = (0, react.useState)(() => readCollapsed(WS_COLLAPSE_PREFIX + wsKey));
395
395
  return [collapsed, (0, react.useCallback)(() => {
@@ -400,8 +400,8 @@ function useWorkspaceCollapse(wsKey) {
400
400
  }
401
401
  const COPY = {
402
402
  zh: {
403
- label: "DSH Crew",
404
- title: "DSH Crew",
403
+ label: "DSH Adapter",
404
+ title: "DSH Adapter",
405
405
  intro: "把 Claude Code / Codex 的子任务派给本实例的 DSH agent,在宿主里显示为原生子代理、进度可见。配置派发默认值、执行方式,以及接入视觉与生图能力,一键装进宿主。",
406
406
  integrations: "集成",
407
407
  collapse: "折叠",
@@ -412,14 +412,16 @@ const COPY = {
412
412
  install: "安装",
413
413
  update: "更新",
414
414
  restore: "还原",
415
- confirmRestore: (name) => `确定从 ${name} 移除 dsh-crew 集成?(settings 会先备份)`,
415
+ confirmRestore: (name) => `确定从 ${name} 移除 dsh-adapter 集成?(settings 会先备份)`,
416
416
  globalConfig: "全局配置",
417
- globalHint: "修改即时保存到 ~/.config/dsh-crew/config.json;CC / Codex 的新会话自动读取为默认值(会话内可用 /dsh-crew:config 临时覆盖)。",
417
+ globalHint: "修改即时保存到 ~/.config/dsh-adapter/config.json;CC / Codex 的新会话自动读取为默认值(会话内可用 /dsh-adapter:config 临时覆盖)。",
418
418
  tier: "默认档位",
419
419
  effort: "默认推理",
420
420
  mode: "执行模式",
421
421
  timeout: "默认超时(秒)",
422
422
  hubUrl: "Hub 地址",
423
+ tierFlash: "flash · 默认",
424
+ tierPro: "pro · 备选",
423
425
  tierPolicy: "档位策略",
424
426
  escalate: "失败升档",
425
427
  tierPolicyDesc: {
@@ -453,7 +455,7 @@ const COPY = {
453
455
  imagegenModel: "生图模型(留空=不提供生图)",
454
456
  visionCmd: "视觉命令(可选)",
455
457
  imagegenCmd: "生图命令(可选)",
456
- apiFormHint: "走 OpenAI 兼容接口:视觉调 {base}/chat/completions(图片以 base64 内联),生图调 {base}/images/generations。Key 保存在本机 ~/.config/dsh-crew/config.json,不会外发到第三方。",
458
+ apiFormHint: "走 OpenAI 兼容接口:视觉调 {base}/chat/completions(图片以 base64 内联),生图调 {base}/images/generations。Key 保存在本机 ~/.config/dsh-adapter/config.json,不会外发到第三方。",
457
459
  cliFormHint: "命令经 bash 执行,占位符会被安全引用后代入。视觉: {image} {question} {model},stdout 即答案;生图: {prompt} {output} {size},命令须把图片写到 {output}。两条命令至少填一条。",
458
460
  saveProvider: "保存",
459
461
  cancel: "取消",
@@ -527,7 +529,7 @@ const COPY = {
527
529
  procKillDone: "已向失联进程发送终止信号",
528
530
  procKillAlreadyGone: "进程已不存在(可能已自行退出)",
529
531
  procAliveBadgeTip: (pid) => `任务已失联,但其工作进程仍在运行(pid ${pid}):很可能是派活宿主崩溃后留下的孤儿进程`,
530
- procKillTip: (pid) => `杀死 pid ${pid}:先读取命令行校验确为 dsh-crew 工作进程(DSH 运行时 / agy / grok),再 SIGTERM,约 3 秒后仍存活则 SIGKILL`,
532
+ procKillTip: (pid) => `杀死 pid ${pid}:先读取命令行校验确为 dsh-adapter 工作进程(DSH 运行时 / agy / grok),再 SIGTERM,约 3 秒后仍存活则 SIGKILL`,
531
533
  finishedJobs: "已结束",
532
534
  noCwdGroup: "(未指定工作区)",
533
535
  lockBadgeTip: (h) => `「${h?.cwd ?? "此工作区"}」正被运行中任务持锁(job ${h?.jobId} · backend ${h?.backend} · 开始于 ${h?.startedAt}):对该 cwd 的再次派发会被拒绝,除非传 allow_concurrent_cwd: true。`,
@@ -555,20 +557,20 @@ const COPY = {
555
557
  restore: "删除 ~/.codex/ 下的 ds-flash / ds-pro 角色与 dsh 命令文件(角色文件先备份)"
556
558
  },
557
559
  agy: {
558
- install: "把 dsh-crew MCP server 注册进 ~/.gemini/config/mcp_config.json,并将 ds-flash / ds-pro 代理与 dsh-config / dsh-status skills 复制到 ~/.gemini/config/agents 与 skills(修改前自动备份)",
560
+ install: "把 dsh-adapter MCP server 注册进 ~/.gemini/config/mcp_config.json,并将 ds-flash / ds-pro 代理与 dsh-config / dsh-status skills 复制到 ~/.gemini/config/agents 与 skills(修改前自动备份)",
559
561
  update: "重新覆盖 MCP 配置、代理与 skills(插件路径或配置变更后用);原文件先备份",
560
- restore: "从 ~/.gemini/config 移除 dsh-crew 的 mcp_config.json 条目、ds-flash / ds-pro 代理与 dsh-config / dsh-status skills(修改前备份)"
562
+ restore: "从 ~/.gemini/config 移除 dsh-adapter 的 mcp_config.json 条目、ds-flash / ds-pro 代理与 dsh-config / dsh-status skills(修改前备份)"
561
563
  },
562
564
  grok: {
563
- install: "把 dsh-crew MCP server 段写入 ~/.grok/config.toml,并将 ds-flash / ds-pro 代理与 dsh-config / dsh-status 命令复制到 ~/.grok/agents 与 commands(修改前自动备份)。提示:grok 出于安全设计,在未信任的项目目录里不会启动仓库级 MCP server —— 全局安装不受影响,但在未信任目录里用 grok mcp doctor 检查时会看到 \"folder untrusted\",换个目录或加 --trust 即可。",
565
+ install: "把 dsh-adapter MCP server 段写入 ~/.grok/config.toml,并将 ds-flash / ds-pro 代理与 dsh-config / dsh-status 命令复制到 ~/.grok/agents 与 commands(修改前自动备份)。提示:grok 出于安全设计,在未信任的项目目录里不会启动仓库级 MCP server —— 全局安装不受影响,但在未信任目录里用 grok mcp doctor 检查时会看到 \"folder untrusted\",换个目录或加 --trust 即可。",
564
566
  update: "重新覆盖 config.toml 的 MCP 段、代理与命令(插件路径或配置变更后用);原文件先备份",
565
- restore: "从 ~/.grok 移除 dsh-crew 的 config.toml 段、ds-flash / ds-pro 代理与 dsh-config / dsh-status 命令(修改前备份)"
567
+ restore: "从 ~/.grok 移除 dsh-adapter 的 config.toml 段、ds-flash / ds-pro 代理与 dsh-config / dsh-status 命令(修改前备份)"
566
568
  }
567
569
  }
568
570
  },
569
571
  en: {
570
- label: "DSH Crew",
571
- title: "DSH Crew",
572
+ label: "DSH Adapter",
573
+ title: "DSH Adapter",
572
574
  intro: "Dispatch Claude Code / Codex subtasks to DSH agents within this instance, displayed as native subagents in the host with live progress. Configure dispatch defaults, execution mode, and vision/image generation (via subscription CLI or your own OpenAI API), then one-click install into the host.",
573
575
  integrations: "Integrations",
574
576
  collapse: "Collapse",
@@ -579,14 +581,16 @@ const COPY = {
579
581
  install: "Install",
580
582
  update: "Update",
581
583
  restore: "Restore",
582
- confirmRestore: (name) => `Remove the dsh-crew integration from ${name}? (settings are backed up first)`,
584
+ confirmRestore: (name) => `Remove the dsh-adapter integration from ${name}? (settings are backed up first)`,
583
585
  globalConfig: "Global configuration",
584
- globalHint: "Changes save instantly to ~/.config/dsh-crew/config.json; new CC / Codex sessions pick them up as defaults (override per session with /dsh-crew:config).",
586
+ globalHint: "Changes save instantly to ~/.config/dsh-adapter/config.json; new CC / Codex sessions pick them up as defaults (override per session with /dsh-adapter:config).",
585
587
  tier: "Default tier",
586
588
  effort: "Default effort",
587
589
  mode: "Mode",
588
590
  timeout: "Timeout (s)",
589
591
  hubUrl: "Hub URL",
592
+ tierFlash: "flash · default",
593
+ tierPro: "pro · alternate",
590
594
  tierPolicy: "Tier policy",
591
595
  escalate: "Escalate on failure",
592
596
  tierPolicyDesc: {
@@ -620,7 +624,7 @@ const COPY = {
620
624
  imagegenModel: "Image-gen model (empty = no image generation)",
621
625
  visionCmd: "Vision command (optional)",
622
626
  imagegenCmd: "Image-gen command (optional)",
623
- apiFormHint: "OpenAI-compatible: vision calls {base}/chat/completions (image inlined as base64), image-gen calls {base}/images/generations. The key is stored locally in ~/.config/dsh-crew/config.json and never sent to third parties.",
627
+ apiFormHint: "OpenAI-compatible: vision calls {base}/chat/completions (image inlined as base64), image-gen calls {base}/images/generations. The key is stored locally in ~/.config/dsh-adapter/config.json and never sent to third parties.",
624
628
  cliFormHint: "Commands run via bash with shell-quoted placeholders. Vision: {image} {question} {model}, stdout is the answer; image-gen: {prompt} {output} {size}, the command must write the image to {output}. Fill in at least one command.",
625
629
  saveProvider: "Save",
626
630
  cancel: "Cancel",
@@ -722,14 +726,14 @@ const COPY = {
722
726
  restore: "Delete ds-flash / ds-pro roles and dsh prompts from ~/.codex/ (roles backed up first)"
723
727
  },
724
728
  agy: {
725
- install: "Register the dsh-crew MCP server in ~/.gemini/config/mcp_config.json and copy ds-flash / ds-pro agents plus dsh-config / dsh-status skills into ~/.gemini/config/agents and skills (backed up first)",
729
+ install: "Register the dsh-adapter MCP server in ~/.gemini/config/mcp_config.json and copy ds-flash / ds-pro agents plus dsh-config / dsh-status skills into ~/.gemini/config/agents and skills (backed up first)",
726
730
  update: "Re-write the MCP entry, agents and skills (after path/config changes); originals backed up",
727
- restore: "Remove the dsh-crew mcp_config.json entry, ds-flash / ds-pro agents and dsh-config / dsh-status skills from ~/.gemini/config (backed up first)"
731
+ restore: "Remove the dsh-adapter mcp_config.json entry, ds-flash / ds-pro agents and dsh-config / dsh-status skills from ~/.gemini/config (backed up first)"
728
732
  },
729
733
  grok: {
730
- install: "Write the dsh-crew MCP server section into ~/.grok/config.toml and copy ds-flash / ds-pro agents plus dsh-config / dsh-status commands into ~/.grok/agents and commands (backed up first). Note: by security design grok does not start repo-level MCP servers in untrusted project directories — a global install is unaffected, but grok mcp doctor reports \"folder untrusted\" in an untrusted directory; change directory or pass --trust.",
734
+ install: "Write the dsh-adapter MCP server section into ~/.grok/config.toml and copy ds-flash / ds-pro agents plus dsh-config / dsh-status commands into ~/.grok/agents and commands (backed up first). Note: by security design grok does not start repo-level MCP servers in untrusted project directories — a global install is unaffected, but grok mcp doctor reports \"folder untrusted\" in an untrusted directory; change directory or pass --trust.",
731
735
  update: "Re-write the config.toml MCP section, agents and commands (after path/config changes); originals backed up",
732
- restore: "Remove the dsh-crew config.toml section, ds-flash / ds-pro agents and dsh-config / dsh-status commands from ~/.grok (backed up first)"
736
+ restore: "Remove the dsh-adapter config.toml section, ds-flash / ds-pro agents and dsh-config / dsh-status commands from ~/.grok (backed up first)"
733
737
  }
734
738
  }
735
739
  }
@@ -1764,7 +1768,13 @@ function WorkersPanel({ ctx }) {
1764
1768
  }), /* @__PURE__ */ (0, react_jsx_runtime.jsx)(CustomSelect, {
1765
1769
  value: config.default_tier,
1766
1770
  onChange: (v) => field("default_tier", v),
1767
- options: [{ value: "flash" }, { value: "pro" }]
1771
+ options: [{
1772
+ value: "flash",
1773
+ label: copy.tierFlash
1774
+ }, {
1775
+ value: "pro",
1776
+ label: copy.tierPro
1777
+ }]
1768
1778
  })]
1769
1779
  }),
1770
1780
  /* @__PURE__ */ (0, react_jsx_runtime.jsxs)("label", {
@@ -2635,7 +2645,7 @@ function apply(ctx) {
2635
2645
  function register() {
2636
2646
  return ctx.slots.register({
2637
2647
  name: "settings.section",
2638
- id: "dsh-crew",
2648
+ id: "dsh-adapter",
2639
2649
  order: 65,
2640
2650
  label: () => {
2641
2651
  const base = COPY[ctx.locale.getLocale().active === "zh" ? "zh" : "en"].label;