Build Your First DeepSeek Harness Plugin
The official first-plugin path starts with a package that exposes a Cordis plugin and, when it should activate as a bundle, declares the patch metadata consumed by dsh. Build and test it in an isolated profile before sharing installation commands. 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.
What is verified now
The official first-plugin path starts with a package that exposes a Cordis plugin and, when it should activate as a bundle, declares the patch metadata consumed by dsh. Build and test it in an isolated profile before sharing installation commands.
Evidence basis: Official first-plugin docs. 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.