SeverusZh/dsh-plugin-subagent-director
31Last commit Aug 14, 2026
dsh-plugin-subagent-director DSH plugin
Subagent Director is a DeepSeek Harness plugin that lets you assign a specific LLM provider and model to subagents on a per-role or per-call basis. It provides role templates (e.g., code reviewer, translator) with descriptions, personas, and optional model bindings, plus a four-layer resolution chain for maximum flexibility. A settings UI allows visual management of defaults and roles.
How to install the dsh-plugin-subagent-director DSH plugin
dsh plugin --profile <name> add dsh-plugin-subagent-directorThis source command needs manual review. Copying does not run it.
dsh-plugin-subagent-director DSH plugin data source
dsh-plugin-subagent-director DSH plugin snapshot date: Aug 16, 2026
discovered
What the dsh-plugin-subagent-director DSH plugin can do
- Configure default LLM route and model for subagents, with per-call override via tool arguments.
- Define role templates carrying a description, persona, and optional model binding.
- Four-layer resolution: call arguments > role binding > plugin default > inherit from parent agent (zero intrusion when unconfigured).
- Inject a system prompt listing available roles so the main agent knows when to delegate.
- Settings UI in the DSH panel to manage default model and role cards (add/delete/modify).
- Support continuable background subagent sessions with follow-up messages.
Where the dsh-plugin-subagent-director DSH plugin fits
- Assign a specialized reasoning model (e.g., deepseek-reasoner) to a code review subagent.
- Create a translator role that always uses a cheap model for quick translations.
- Let the main agent dynamically choose between multiple subagent roles via a single tool call.
- Run a subagent with a different provider (e.g., pi-ai) while the main agent uses the default provider.
- Build multi-step workflows where each subagent call has its own model assignment.
Who the dsh-plugin-subagent-director DSH plugin is for
- DSH users who want granular control over subagent LLM providers and models.
- Developers building multi-agent systems with role-based delegation in DSH.
dsh-plugin-subagent-director DSH plugin limitations
- Requires DSH 0.1.0-rc.x or later (as indicated by the badge).
- Needs two plugin entries in cordis.patch.yml (main + bridge) for Web UI settings to work.
- The observability feature (showing actual provider/model under composer) is not yet available (still under development).
- Settings namespace is only exposed to Web UI via a dedicated bridge entry; headless mode may skip the bridge automatically.
dsh-plugin-subagent-director DSH plugin: from the repository README
Quoted from the SeverusZh/dsh-plugin-subagent-director README, the upstream source of the dsh-plugin-subagent-director DSH plugin. Copyright remains with the original authors.
> 为 DeepSeek Harness 的 subagent 指定 LLM 供应商与模型，并用「角色模板」规划主代理与子代理的分工。 <p align="center"> <img alt="npm version" src="https://img.shields.io/npm/v/dsh-plugin-subagent-director?label=npm"> <img alt="license" src="https://img.shields.io/npm/l/dsh-plugin-subagent-director"> <img alt="DeepSeek Harness" src="https://img.shields.io/badge/DeepSeek%20Harness-0.1.0--rc.x-blue"> </p> [English](#english) · [特性](#特性) · [快速开始](#快速开始) · [角色模板](#角色模板) · [术语](#术语) · [开发](#开发) · [路线图](#路线图) · [FAQ](#faq) --- ## 特性 - **供应商与模型选择** —— 为 subagent 配置默认 LLM 供应商（route）与模型；每次委派也可以由模型显式指定； - **角色模板** —— 定义「代码审查员」「翻译员」等角色：职责描述（给主代理看）+ persona（注入子代理）+ 可选模型绑定； - **四级回退链** —— 单次调用参数 > 角色绑定 > 插件默认 > 继承主代理（未配置时零侵入）； - **主代理指引** —— 系统提示自动注入角色清单，主代理知道何时委派给谁； - **设置界面** —— DSH 设置面板内可视化配置（默认模型 + 角色卡片增删改）； - **continuable 后台** —— 返回可续聊子代理 id，配合 send_message 持续委派； - **可观测性** —— 打开子代理会话时，composer 下方显示其实际运行的供应商/模型。⚠️ 该功能暂不可用，正在开发中； ## 快速开始 ### 安装 ```bash dsh plugin --profile <name> add dsh-plugin-subagent-director ``` 或本地开发时以 file: / link: 路径挂载（示例见下）。 ### 配置（cordis.patch.yml） 需要**两个插件条目**（本包拆分了桥接条目，用于把设置命名空间暴露给 Web UI）： ```yaml - insert: - id: subagent-director name: dsh-plugin-subagent-director
Read the full READMERepository license: MIT
dsh-plugin-subagent-director DSH plugin questions
Why do I need two plugin entries in cordis.patch.yml?
The DSH Web API only exposes settings namespaces that are whitelisted. This plugin registers its own HTTP route `/subagent-director` to bridge its namespace, which requires the `webServer` service via Cordis `inject`. To avoid pulling the web server dependency into the main plugin, the bridge is split into a separate entry (`subagent-director-bridge`). In headless mode without Web UI, the bridge entry is automatically deactivated, and the main plugin still works.
What happens if I don't configure any roles?
If no roles are configured, the plugin behaves exactly as if it were not installed: subagents inherit the parent agent's model, with zero intrusion. The four-layer resolution chain will fall back to the parent agent's settings.
Will new providers or API keys automatically appear in the settings UI?
Yes. The settings page subscribes to provider and settings change events. When you add a new provider or API key in the Models page, the dropdown list in the plugin's settings UI refreshes automatically without needing a restart.
Can I override the model for a single subagent call without changing the role?
Yes. When calling the `subagent_role` tool, you can pass optional `provider` and `model` arguments. These take the highest priority in the four-layer resolution chain (call args > role binding > plugin default > inherit from parent). For example: `subagent_role({ role: "code-reviewer", model: "deepseek-chat", prompt: "..." })`.
Is the observability feature (showing actual model under composer) ready?
Not yet. The README states that this feature is still under development and currently unavailable. The plugin will show the subagent's actual provider and model under the composer once the feature is implemented in a future version (v0.2).