MJorgin/dsh-agent-conductor
⚡ DSH 指挥家(动态插件/热更新版):在会话里派活给 11 种外部 agent CLI(Codex/Claude Code/TraeCode…),cordis_define 秒级安装,不碰 profile。
Listed
1
Workflow
Bundle verified
Preview
What it does
Dispatch self-contained tasks from DSH to 11 external agent CLIs (Codex, Claude Code, TraeCode, OpenCode, Gemini, Cursor, Kimi, Qwen, Copilot, WorkBuddy, Grok): a host-only bundle registering the conductor_dispatch tool plus an auto-triggered conductor skill.
Best for
- DSH users who want to delegate a self-contained task to an installed external agent CLI and bring the result back into the conversation.
- Workflows that choose among Codex, Claude Code, TraeCode, OpenCode, Gemini, Cursor, Kimi, Qwen, Copilot, WorkBuddy, or Grok.
- Users who prefer either a host-only dispatch tool or description-triggered conductor skill without adding Web UI.
Not ideal for
- Users without the selected external CLI installed, authenticated, and available on PATH.
- Sensitive tasks that should not be sent to another CLI or charged against that CLI's account quota.
- Workflows requiring a built-in task dashboard or multi-agent squad orchestration; those features are documented as roadmap items.
- Reliability-critical use of Gemini, Cursor, Kimi, Qwen, Copilot, WorkBuddy, or Grok dispatch commands, which the README marks as not yet machine-tested.
README
⚡ dsh-agent-conductor · DSH 指挥家(Skill 版)

让 DeepSeek Harness 的 agent 自动识别派活需求,把任务派给 11 种外部 agent CLI(Codex、Claude Code、TraeCode、OpenCode、Gemini、Cursor、Kimi、Qwen、Copilot、WorkBuddy、Grok)无头执行,结果回传会话。
灵感来自 Multica——把”agent 小队”概念做成一个零安装成本的 DSH 技能。
为什么是 Skill
| profile 插件 / bundle | 动态插件 | Skill(本方案) | |
|---|---|---|---|
| 安装 | 写 profile + 重启 | 会话内定义 | 复制一个文件夹 |
| 触发 | 手动 | 模型调工具 | 描述匹配,模型自动识别 |
| 风险 | 可能影响 Web UI | 会话级、重启消失 | 只读脚本,宿主无感 |
| 结果 | 工具结果 | 工具结果 | stdout 直接成为回答依据 |
一个 SKILL.md + 一个 90 行的 dispatch.py,完事。
安装
把 skills/conductor/ 复制到任意技能根目录(项目级 .dsh/skills/ 或全局 ~/.dsh/skills/):
mkdir -p .dsh/skills/conductor
cp -R skills/conductor/. .dsh/skills/conductor/
装完无需重启——下次对话直接说:
- 「派 codex 把这份 README 翻译成繁体中文」
- 「让 Claude Code 查一下这个报错的成因」
- 「用 Codex 独立实现一个 XXX」
agent 会自动识别(SKILL.md 描述匹配)→ 执行 dispatch.py → 结果回传。
前置:想派谁就装谁的 CLI
# Codex(机器上已有 codex-cli 时软链到 PATH)
ln -s ~/.codex/plugins/.plugin-appserver/codex ~/.local/bin/codex
# Claude Code / OpenCode
npm i -g @anthropic-ai/claude-code
npm i -g opencode-ai
# TraeCode CLI:https://docs.trae.cn/cli_command-line-parameters
Codex 要求在受信任的 git 仓库运行:把
CONDUCTOR_CWD=/path/to/git/repo写进~/.dsh/secrets/media-tools.env。 想让派出的 agent 能写文件:Codex 的~/.codex/config.toml加sandbox_mode = "workspace-write"。 派活消耗对方 CLI 的登录额度。
已验证 vs 待验证
| CLI | 无头命令 | 状态 |
|---|---|---|
| Codex | codex exec "{task}" |
✅ 真机实测(翻译任务已产出交付) |
| Claude Code | claude -p "{task}" --output-format text |
✅ 官方文档 |
| TraeCode | traecli exec "{task}" |
✅ 官方文档 |
| OpenCode | opencode run "{task}" |
✅ 官方文档 |
| Gemini / Cursor / Kimi / Qwen / Copilot / WorkBuddy / Grok | 见 dispatch.py 注册表 |
⏳ 命令形态待实测 |
可选:bundle 安装(host-only)
仓库同时是一个 host-only dsh bundle(声明 dsh.bundle、无任何客户端代码),一条命令把 conductor_dispatch 工具装进 profile:
dsh plugin --profile web add github:MJorgin/dsh-agent-conductor
- 工具与技能共用同一份 CLI 注册表;
- 无 client 半边,不影响 Web UI(早期带面板的客户端版本因此移除,见 git log);
- 面板/任务看板回收等功能走路线图,另行实现。
仓库内容
index.js # bundle 宿主半边:conductor_dispatch 工具(host-only)
cordis.patch.yml # bundle 层(单行,无客户端)
skills/conductor/SKILL.md # 技能定义:触发描述 + 派活规则 + 隐私
skills/conductor/scripts/dispatch.py # 派活引擎(Python 标准库,零依赖)
conductor-dynamic.js # 备选:动态插件版(cordis_define 路线)
路线图
- 面板 UI(可选,动态插件 client 半边)
- 任务看板回收:派活结果写入 dsh-task-board 卡片
- 小队编排:一个任务分发给多个 agent 汇总(Multica squads 形态)
License
相关链接
- 🎨 dsh-media-skills —— 同作者的 DSH 读图/生图插件(GLM-4V-Flash + Qwen3-VL + Gemini 三引擎容错)
- ⚡ 本仓库:dsh-agent-conductor
- 📬 社区收录 PR:awesome-dsh-plugin#664
- 📋 精选列表:awesome-dsh-plugin · 生态索引:dsh-plugin topic
- 🎯 对标:Multica(多 agent 工作台)· dsh-web-ui(任务看板)
Frequently Asked QuestionsFAQ
Use the verified command dsh plugin --profile default add github:MJorgin/dsh-agent-conductor in a DSH-enabled shell. The command resolves the public package metadata and keeps the plugin attached to the catalog identity shown on this page.
Compatibility follows the bundle and profile status shown above. If a profile is not detected, keep the plugin disabled there and check the repository documentation before enabling it in production.
The GitHub link and activity metadata are the source of truth for releases and maintenance. Revisit this page after a new release to confirm the catalog has observed the latest version.