In DeepSeek Harness (DSH) development scenarios, a common pain point is how to let one agent simultaneously manage multiple parallel subtasks. Traditional approaches often handle only single-threaded execution, or require manual intervention. dsh-plugin-task-coordinator aims to solve this problem. It allows one “supervisor” session to dispatch, monitor, and collect results from other subtask sessions through a set of tools.

Plugin Overview

The plugin is maintained by developer Kayungko, belongs to the “Workflow” category, and is licensed under the MIT License. It provides a set of task_* tools that mimic Codex’s cross-task coordination mechanism, supporting cross-session messaging, task creation, and status tracking.

Core Features

The plugin provides the following core capabilities:

  • Task Management: task_list lists visible tasks; task_progress reads detailed progress for a single task (including status, messages, to-dos, etc.).
  • Task Scheduling: task_spawn creates and starts a new task; task_spawn_batch supports batch parallel dispatch; task_send sends visible follow-up prompts to tasks.
  • Result Collection: task_wait collects results from spawned tasks.
  • Interactive Confirmation: Supports interactive confirmation (task_confirm), with approval cards, reusable task-level approvals, and multi-select partial dispatch (task_confirm_select).
  • Environment and Model Control: Supports workspace migration (task_workspace), subtask model selection (task_models), recursive depth governance, and workspace inheritance.
  • Auxiliary Features: Includes the /tasks command, session ID copy button, result report return, and localized user interface strings.

Installation and Enabling

Before installation, ensure the following prerequisites are met:

  • DSH Desktop is installed and running (the plugin does not start the host application).
  • Node.js version is ^22.19.0 || >=24.
  • PowerShell is installed on the system.

Run the following command to install:

git clone https://github.com/Kayungko/dsh-plugin-task-coordinator.git
cd dsh-plugin-task-coordinator
pwsh install.ps1 -Source .

The installation script performs the following actions: it copies the plugin files into node_modules/ under the configuration directory (without modifying pnpm-lock.yaml), registers the dependency and packaging contents in the configuration manifest, and updates .package-map.json. All operations are first backed up to the backups/<timestamp>/ directory before execution.

After installation, restart DSH Desktop. At this point, any top-level session can use the related tools and the /tasks command.

Usage

The plugin relies on explicit instructions. To ensure the model calls the tools correctly, it is recommended to directly reference tool names in prompts and use imperative mood.

Example 1: Parallel Task Splitting

You can directly request that a task be split into multiple parts for parallel execution:

Split this into three tasks and run them in parallel: A researches the approach, B builds the prototype, C runs the tests. Summarize for me when they finish.

Example 2: Supervisor Session Takeover

In /goal mode, the supervisor session should clarify its responsibilities:

As the supervisor session, take over the remaining development: ① splittable work MUST be dispatched to parallel sub-task sessions via task_spawn_batch (attach a team name) — do not do everything yourself; ② collect results with task_wait and integrate them; ③ sub-task sessions may further parallelize with their own subagents; ④ push to remote main at every milestone.

Notes and Applicable Scenarios

  • Runtime Environment: The plugin runs with the permissions of the current DSH process, so check the source code and license before installing.
  • Git Worktrees: To maintain isolation, Git worktrees are intentionally designed as “ungrouped.”
  • Re-runnability: Re-running the installation script is safe; file copying is idempotent, and manifest registration automatically deduplicates.
  • Prompt Engineering: Vague instructions (such as “you can use the /task plugin”) usually do not work. The model will only coordinate when it can map your language to tools. Ensure instructions name the tools explicitly and use imperative mood.
  • /goal Mode Limitation: In /goal mode, coordination instructions must be included in the goal object so that each subsequent turn remains anchored to that text.

Summary

dsh-plugin-task-coordinator gives DSH the ability to transition from single-session to multi-session orchestration. Through standard task_* tools and approval workflows, developers can achieve complex cross-task collaboration without leaving the DSH interface.