How to Install a DeepSeek Harness Plugin
The official manager forwards plugin arguments to pnpm inside the selected profile and reconciles installed bundle declarations. A package only joins the profile layer stack when its manifest declares the expected dsh bundle metadata. This page separates verified behavior from community reports and marks the release-candidate context so you can act without mistaking an observation for a permanent guarantee.
Start with this command
This is the narrow command relevant to this page. Read the checks below before changing flags, credentials or profile patches.
dsh plugin --profile my-profile add <reviewed-package-or-git-spec>What is verified now
The official manager forwards plugin arguments to pnpm inside the selected profile and reconciles installed bundle declarations. A package only joins the profile layer stack when its manifest declares the expected dsh bundle metadata.
Evidence basis: Official plugin-management reference. The status was checked on 14 August 2026; re-check the linked source after any dsh release.
Safe workflow
Use the smallest reversible workflow first. Do not add community plugins or paste credentials while validating the base behavior.
- Inspect package identity, source, manifest and lifecycle scripts.
- Install into an isolated profile and inspect the composed config.
- Enable the smallest capability set and verify startup before adding another plugin.
Verify before moving on
A successful result should be observable: a version string, reachable local URL, valid provider response, loaded configuration, or disappearance of the exact error. If the result differs, stop and capture sanitized evidence rather than stacking unrelated fixes.
- Record the exact dsh, Node or Python version.
- State the operating system and installation method.
- Link the first-party source and include only sanitized logs.
First-party sources
Open the original source before acting on a changed version or unresolved community report.