Foreword

DSH originally used one agent carrying about 60 tools and loaded them all for every request. This creates high context overhead and tool redundancy. dsh-paoding (Paoding) is DSH’s preset generator; it transforms DSH into a “one conductor + four helpers” architecture. The main agent only handles orchestration and internal search, while the remaining work is delegated by role to sub-agents that carry only their specialized tools. Everything is done through configuration, with zero changes to DSH source code.

Core Features

  1. A small team with clear division of labor: The main agent acts as the conductor—breaking down tasks, delegating work, and verifying results. Four dedicated helpers own web research, UI design, coding, and deep repository-wide search; they are available on demand and finish, then exit.
  2. Routine tasks are not delegated: Easy, frequent jobs such as finding code, checking references, and reading files are handled directly by the main agent instead of going through delegation.
  3. Dedicated helpers can be recruited: The four built-in roles are only a starting point—configure tools and skills for a new role, and then a single instruction can route work to it. Roles can be created from either the config file or the GUI.
  4. Helpers can be assigned dedicated models: Use a stronger model for coding, a faster/lighter model for research, and so on. If no model is configured, a helper follows the main agent’s current session model.
  5. Helpers can fork and inherit the conversation: Set a role’s startup method to conversation inheritance, and the helper starts with the conversation turns already completed by the main agent, avoiding restating context when delegating.
  6. Helpers can be fixed in place (continuable): Set a role’s session mode to continuable. If a result is bad or unsatisfying, the main agent uses send_message to continue repairing it in the same sub-session instead of re-delegating from scratch.
  7. Save cost and context: Helper tools are loaded only when they are called, so cost is incurred per use; the main agent’s per-request tool overhead drops by about two-thirds, and only summaries enter its context.
  8. Roles can be adjusted immediately: Removing unused built-in roles, renaming roles, and setting a display name for the main agent are all one-line config changes; after clicking “Save and Apply” in the panel, the preset is regenerated immediately.
  9. Installed integrations are detected: MCP servers, local plugins, and installed skills are detected throughout installation and configuration; by default only the DSH base tools are installed, and detected host tools can be toggled as needed in “Paoding Configuration”.
  10. Each workspace can have its own team: Different projects can configure different main/sub-agents—select a workspace in “Paoding Configuration” and configure it separately; each workspace generates its own preset.
  11. GUI configuration: Open the “Paoding Configuration” entry at the bottom of the left sidebar, configure everything by clicking, and “Save and Apply” regenerates the preset immediately.
  12. Update reminders with one-click upgrade: The panel checks the latest version from the npm registry, shows an in-place update notice with a link to the release page when a newer version is found; click “Upgrade” to switch to the new version in place.
  13. Easy to enter and exit: It does not modify a single line of DSH source code; new sessions can use it immediately after installation, and uninstalling removes the directory.
  14. Compatible with both host generations: Supports DSH 0.1.5 – 0.2.0-rc.2.

Installation and Enablement

Prerequisites: Node.js ≥ 18, pnpm, and an installed DSH host (0.1.5 – 0.2.0-rc.2).

Install using the official plugin channel:

dsh plugin --profile web add dsh-paoding

After installation, restart DSH to use it. By default, only DSH’s built-in base tools are installed; detected MCP/host tools are not automatically written. After installation, open “Paoding Configuration” in the left sidebar, select tools and roles as needed, and “Save and Apply” takes effect immediately.

Typical Usage

Just assign tasks to the main agent; it routes them according to responsibilities:
* Find code / check references / read files → handled by the main agent itself, without delegation.
* Web research / fact-finding → web research helper (search_external).
* UI proposals / design drafts → design helper (design).
* Write code / modify code → implementation helper (implement).
* Deep exploration of a very large repository → deep repository-wide search helper (search_internal_deep).
* Specialized work → create a custom role first, then invoke it on demand.

Configuration and Maintenance

All preferences are written in ~/.dsh/dsh-paoding.config.yml: adding, removing, and modifying roles, skill assignment, dedicated models, session mode, startup method, and more. After making changes, click “Save and Apply” in the panel to apply them immediately.

Uninstallation requires cleaning up the .agent-presets directory:

rm -rf "${DSH_HOME:-$HOME/.dsh}/.agent-presets/orchestrator"
rm -rf "${DSH_HOME:-$HOME/.dsh}/.agent-presets"/orchestrator-*

Ecosystem Context

DSH’s philosophy is “everything is a plugin”; the community catalog is an independent site and has no official affiliation with DeepSeek / Huanfang.