Introduction¶
DeepSeek Harness (DSH) uses a plugin-based architecture, with Cordis as its core dependency. In agent development, when a sub-Agent’s step activation has settled, it wakes the parent. However, if the parent is currently busy, the runtime usually places the subagent-settled response written by the parent into the next safe Agent step.
This causes the parent to process sub-Agent callbacks before ordinary context. The dsh-subagent-response-promoter plugin is designed to stably promote these responses ahead of the ordinary context in that step, ensuring that the parent prioritizes sub-Agent callbacks without polling or interrupting ongoing model or tool calls.
What It Is¶
dsh-subagent-response-promoter is a Host-side Cordis plugin. It is maintained by JachinShen. Its core role is to safely promote sub-Agent responses at Agent step boundaries in DeepSeek Harness, and to handle the migration of coordinator relays.
Core Features¶
- Promote sub-Agent responses: Within an Agent step, place sub-Agent responses before ordinary context, ensuring that the parent responds to sub-Agents first.
- Coordinator relay migration: The built-in
send_messagetool submits coordinator relays. This plugin moves the relay fromnext-turnto the sub-Agent’snext-stepinbox, while preserving the original wake-up signal. - Non-interrupting: Relocating the relay does not cancel active model requests or tool calls. It only becomes visible when the Agent reaches a safe step boundary.
Installation and Activation¶
Add the dependency and bundle the plugin in the DSH configuration file.
{
"dependencies": {
"dsh-subagent-response-promoter": "github:JachinShen/dsh-subagent-response-promoter#v0.2.0"
},
"dsh": {
"profile": {
"bundles": [
"@deepseek-ai/dsh-base",
"dsh-subagent-response-promoter"
]
}
}
}
After adding the configuration above, reinstall the profile and restart the DSH process. The plugin’s cordis.patch.yml will automatically insert the Host plugin.
Typical Usage¶
The plugin reorders Agent steps.
Assume a proposed Agent step contains:
ordinary A, child response A, ordinary B, child response B
After processing by the plugin, the model receives:
child response A, child response B, ordinary A, ordinary B
For coordinator relays inserted into next-turn, the plugin persists them and reinserts them into next-step. This migration does not cancel active requests or tool calls; it takes effect after the Agent reaches a safe step boundary.
Applicable Scenarios and Notes¶
This plugin is suitable for scenarios where sub-Agent responses need to be prioritized in complex Agent workflows, without interrupting ongoing model inference or tool calls.
Note:
* This is a Host-side Cordis plugin.
* The plugin includes a built-in send_message tool to submit coordinator relays.
* It is recommended to review the source code and license (MIT) before installation.
Conclusion¶
This plugin resolves the processing delay issue caused when sub-Agents wake a busy parent by adjusting response order and relay routing. For more implementation details and source code, refer to the GitHub repository.