MIT-licensed draft/experimental spec defining how dsh community plugins achieve dsh-TUI / multi-version compatibility via an adapter mapping table and dsh-std conformance tests.
DSH integration
Ecosystem-related
Author-claimed
Safety audit
Unaudited
Last verified
2026-09-04
License
MIT
01What can it help you accomplish?
Publish a dsh plugin that stays compatible across dsh-TUI and dsh versions without per-release maintenance
A spec-compliant plugin manifest validated against the Community v0.15 baseline and TUI Admission v0.15 profile via the conformance suite
dsh-TUI plugin authors and community plugin maintainers who want admission into the TUI plugin marketplace and recommended list
Verify a plugin manifest against the admission rules before publishing
An admission validation report (`npm run validate:manifest`) that reuses the same admission algorithm as the conformance suite
Plugin developers and CI pipelines that need automated manifest admission checks
02How to install into DeepSeek Harness
Prerequisites
- Environment: Node.js 18 or higher, with `corepack` enabled
Installation steps
Not specified by the author
Verify the integration
- Run `npm run validate:manifest -- --manifest ./path/to/dsh-plugin.json` to admission-check a manifest
- Run `pnpm test` (inside the dsh-TUI workspace) or `npm run test:standalone` (standalone checkout) to run the conformance suite
03DSH integration and capability boundaries
Defines the DSH community ecosystem interoperability specification (adapter mapping, dsh-std protocol profile, conformance suite) that community plugins follow to stay compatible across dsh-TUI and dsh versions.
Plugin admission & development spec
Community v0.15 baseline + TUI Admission v0.15 profile→Single integration doc with interface/compatibility agreements, dev guide, and admission checklist
Adapter mapping table
dsh-TUI team's adapter for host/runtime version ↔ public contract→Adapter mapping that auto-adapts all dsh legacy and future versions
Dependency-chain provenance & experimental hot-reload
optional compliance features→dependency-chain tracing and optional experimental plugin hot-update
04Who is it for? When not to use it?
Good for
- dsh-TUI plugin authors and community plugin maintainers who want admission into the TUI plugin marketplace and recommended list
- Plugin developers and CI pipelines that need automated manifest admission checks
Not for
- The current spec and tests are Draft / Experimental; until Candidate/Stable conditions are met, users may only claim "experimental adaptation", and no spec may imply permanent ABI/API stability or official certification before Stable.
05Compatibility, maintenance and safety notes
- The current spec and tests are Draft / Experimental; until Candidate/Stable conditions are met, users may only claim "experimental adaptation", and no spec may imply permanent ABI/API stability or official certification before Stable.
- Reference implementations, TUI itself, or any single host may only provide evidence and cannot become the standard or self-certify merely because an implementation exists.
- Interfaces outside the adapter's coverage range cannot guarantee maintenance-free updates across future dsh releases; coverage grows over time and you can file an issue to propose adding an upstream dsh API to the coverage.
MIT license; no published release yet; last push 2026-08-31
06Frequently asked questions
What is dsh-ecosystem-spec?
It is the DSH Community Ecosystem Interoperability Specification — an experiment library holding the adapter mapping maintained by the dsh-TUI team plus the plugin standard built on the dsh-std protocol, so plugins can stay compatible across dsh versions.
How do I make my plugin compatible across dsh versions?
If your dsh communicates with the dsh body through the dsh-TUI team's adapter, it auto-adapts all legacy and future dsh versions without per-version maintenance concerns. Read and follow this spec to gain that maintenance-free convenience.
How do I validate a plugin manifest?
Run `npm run validate:manifest -- --manifest ./path/to/dsh-plugin.json` (optionally with `--host <host-descriptor.json>` and `--grant <permission>`). It reuses the same admission algorithm as the conformance suite and prepares dsh-std on demand.
How stable is the spec?
The current spec and tests are Draft / Experimental. Until Candidate/Stable conditions are met, you may only claim "experimental adaptation"; nothing may imply permanent ABI/API stability or official certification before Stable.
07Related DSH workflows
deepseek-reasonix
by esengine
DeepSeek-native AI coding agent for your terminal. Engineered around prefix-cache stability — leave it running.
mnemon
by mnemon-dev
LLM-supervised persistent memory for AI agents — graph-based recall, cross-session knowledge, single binary. Works with DeepSeek Harness, Claude Code, OpenClaw, and any agent runtime.
sivtr
by ariestar
A unified agent memory workspace for human and agent
phi
by pulseaiclub
a coding Agent, rpc plugin, sub-agents, hashline edits, and mcp
08Data and sources
> **DSH Community Ecosystem Interoperability Specification**
`dsh-ecosystem-spec` 存放了[dsh-TUI](https://github.com/ccch1mneyyy/dsh-TUI)团队维护的adapter的映射表，同时是使用[dsh-std](https://github.…
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-09-04. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.