MIT-licensed protocol-definition meta-layer for DSH: the `@dsh-std/core` meta-protocol plus per-domain protocols and a single `adapter-dsh` shock absorber make plugin interop standard — write once, run in TUIs, Web, SSH, or headless daemons.
DSH integration
Ecosystem-related
Author-claimed
Safety audit
Unaudited
Last verified
2026-08-27
License
MIT
01What can it help you accomplish?
Let DSH plugins, background runtimes and user interfaces interoperate through one standard protocol layer
Universal interoperability protocols plus a `@dsh-std/core` meta-protocol; the same plugin code runs unchanged in TUI terminals, Web browsers, Remote SSH services and headless daemon containers
DSH plugin authors and host/runtime implementers who want stable contracts decoupled from upstream churn
Predict plugin compatibility before installing, without executing plugin code
Static `dsh-plugin.json` manifests let marketplaces, hosts and CI tools compute compatibility in milliseconds
Developers and platform teams who want to avoid installing a plugin only to find it crashes at runtime
02How to install into DeepSeek Harness
Prerequisites
- Node.js ^22.19 || >=24 and pnpm — the README lists these under Development
Installation steps
- 01
pnpm install
- 02
pnpm check
Verify the integration
Not specified by the author
03DSH integration and capability boundaries
Via the `@dsh-std/adapter-dsh` adapter layer — the adapter acts as a single-point shock absorber isolating DSH's upstream runtime from the universal protocol layer
Meta-protocol core (`@dsh-std/core`)
protocol declarations (`apiVersion` + `kind`) and `requires` / `supports` manifest entries→structured compatibility reports from pure-function negotiations
Single-point DSH adapter (`@dsh-std/adapter-dsh`)
upstream DSH runtime changes and third-party interop churn→breaking changes absorbed inside one adapter layer, shielding the ecosystem
Facet-based on-demand activation
a plugin package bundling frontend UI and backend logic→hosts activate only the facets they need (e.g. a headless server never loads frontend UI code)
when a plugin is disabled or uninstalled, all listeners, timers and resources are automatically garbage-collected by the scopeLightweight headless unit testing
plugins or hosts against the pure protocol core→test results in tens of milliseconds in lightweight Node.js/CI, without a full DSH instance or browser
04Who is it for? When not to use it?
Good for
- DSH plugin authors and host/runtime implementers who want stable contracts decoupled from upstream churn
- Developers and platform teams who want to avoid installing a plugin only to find it crashes at runtime
05Compatibility, maintenance and safety notes
- The code and proposals are early drafts; public contract modifications must be tracked in each package's CHANGELOG.md.
- Conforming implementations are not required to depend on the reference npm packages, nor to run inside DeepSeek Harness.
MIT · early drafts (code and proposals are early drafts)
06Frequently asked questions
What is DSH Standard?
It is a set of universal interoperability protocols whose goal is to let DSH plugins, background runtimes, and various user interfaces (TUI terminals, Web UIs, desktop apps, headless daemons) decouple cleanly and work together smoothly.
How does it connect to DeepSeek Harness?
Adapter code for DSH lives in `@dsh-std/adapter-dsh`. The adapter acts as a single-point shock absorber that isolates the upstream runtime from the universal protocol layer, so DSH can refactor aggressively without breaking the ecosystem.
Do conforming plugins have to depend on the npm packages?
No. Conforming implementations are not required to depend on these npm packages, nor do they need to run inside DeepSeek Harness.
What is `dsh-plugin.json` for?
With static manifests (`dsh-plugin.json`), marketplaces, hosts, and CI tools calculate compatibility in milliseconds without running a single line of plugin code — no more installing a plugin only to find it crashes at runtime.
How mature is the project?
The code and proposals are early drafts. Each package records changes in its own CHANGELOG.md, and public contract modifications must update the corresponding changelog.
07Related DSH workflows
zhuzhiliao
by imsai-sh
Web simulation of a traditional spinning cicada toy that chirps as it spins — zero-dependency single file with real audio samples, mobile-first.
picgo-core
by picgo
:zap:The ultimate image uploading engine. Both CLI & API supports.
helloagents
by hellowind777
Autonomous AI companion that doesn't just analyze problems — it keeps working until the implementation is built and verified.
dsh-infinite-gen-2
by minglink
DeepSeek jailbreak plugin ("Infinite Gen 2") that keeps prompts stable and bypasses model refusals for DeepSeek Harness.
08Data and sources
It isolates the upstream runtime from the universal protocol layer.
Adapter code for DSH lives in [`@dsh-std/adapter-dsh`](packages/adapter-dsh/README.md).
Conforming implementations are not required to depend on these npm packages, nor do they need to run inside DeepSeek Har…
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-08-27. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.