The first version-pinned plugin matrix
“Three packages tested” means all three were installed and classified. It does not mean all three passed, and it does not promote untested external features to verified.
Retained lab record
Plugin install, client load, restart, and cleanup
- Operating system
- Windows 11 · 10.0.26200 · x64
- Runtime
- Node v24.11.1 · DSH 0.1.0-rc.7
- Isolation
- Separate DSH_HOME and web profile for every package
- External access
- No API key, model call, Lark app, OOMOL key, or real secret
From a community error to a tested repair
The report below was valuable because it contained an exact error signature. Its missing environment prevented a verdict, so HarnessBase recreated the smallest versioned matrix instead of copying the suggested conclusion.
Reddit · official embed
Where the error was first reported
Posted by u/Potential_Back_4398 in r/DeepSeek
Open the source on Reddit ↗Source boundary: the post supplied an exact error string, but no DSH version, plugin version, OS, Node version, command, cause, or repair. It was used as a reproduction lead—not as the compatibility verdict.
npx @deepseek-ai/dsh@0.1.0-rc.7 plugin --profile web add dsh-deepseek-vision@0.1.5 If—and only if—the command returns ERR_PNPM_ADDING_TO_ROOT, the tested Windows fallback adds -w before the package name. That flag is not presented as a universal requirement.
Plugin evidence finder
Stars describe repository attention, not DSH compatibility. Records below are intentionally conservative; no third-party entry is labeled install-verified until HarnessBase retains a real run.
Official
DeepSeek Harness core
The official product repository and architecture source. Included as the identity baseline, not counted as a third-party plugin.
Permission question: Permission behavior depends on the active sandbox, approval policy, plugins, tools, and task.
Vision
DeepSeek Vision
A vision gateway plugin whose rc.7 loader compatibility was tested across two published versions.
Permission question: A functional vision test still needs a scoped API credential, one non-sensitive image, and explicit network observations.
Messaging
DSH Lark
A Lark/Feishu channel plugin with a published app ID, credential reference, and long-connection configuration path.
Permission question: Real use needs a Lark/Feishu app ID, DSH_LARK_APP_SECRET, and outbound long-connection access. Message permissions and delivery are untested.
MCP integration
DSH OOMOL
An OOMOL MCP connector that installs and injects configuration but fails the rc.7 client loader on the tested version.
Permission question: Published config references OOMOL_MCP_API_KEY, OOMOL_TEAM_NAME, and an external connector endpoint. No credential or hosted MCP call was used.
Interface
DSH Web UI collection
Repository describing a DSH Web UI plugin and skin collection with task board, git graph, remote UI, token stats, and other extensions.
Permission question: Remote UI, repository state, and token-stat surfaces require source and network review before use.
Preset
DSH Anchored Standard
A two-phase DSH preset described as a minimal bootstrap followed by a fuller standard tool set.
Permission question: Presets can change tools and permission assumptions; inspect every enabled component.
Desktop
DeepSeek Harness Desktop
A third-party desktop solution presented as part of the DSH plugin ecosystem.
Permission question: Desktop packaging expands update, filesystem, process, network, and credential trust surfaces.
Design
Open Design
A local-first design application that claims support for DSH and many other coding agents.
Permission question: May touch local files and invoke multiple agent CLIs; classification and integration path need inspection.
Prompt management
Voyager
A browser enhancement and prompt manager that lists the DSH Web UI among many supported surfaces.
Permission question: Browser extensions can access page content; review requested browser permissions and data handling.
Context
OpenViking
An agent context database tagged in the same topic, with no plugin identity established by the API result alone.
Permission question: Context stores may ingest repository content and persist data; integration and retention need review.
Topic pollution
Reactive Resume
An open-source resume builder that appears in the dsh-plugin topic results without DSH plugin evidence in its repository summary.
Permission question: Not evaluated because it is excluded from the native plugin dataset.
Clear one filter or search a broader repository term.
How a candidate becomes verified
- Resolve canonical repository, author, package, license, and installation source.
- Review build scripts, credentials, network, filesystem, process, and shell surfaces.
- Install in a named DSH, runtime, OS, and date.
- Confirm DSH discovers the plugin.
- Run one named feature smoke test and retain success or failure output.
- Publish rollback, limitations, Unknown fields, and a correction route.
Watch the plugin contract source we used for research
This video contributed concrete implementation vocabulary and a Host/Client MCP example. It remains a community source until its exact code is matched to current official types and compiled.
YouTube · community observed
Plugin structure and lifecycle walkthrough
Publisher-caption tutorial covering Context, name, inject, Config, Schema, apply, ctx.effect, Host/Client entries, and an MCP bridge example.
Boundary: This is community implementation evidence. Exact APIs must be checked against current official types and compiled before a code pattern is labeled verified.
Open the cited segment on YouTube ↗Why the Topic count is not an available-plugin count
The GitHub dsh-plugin topic currently returns the official repository, likely native plugins, broad integrations, browser tools, Skills, tutorials, and unrelated projects. Reactive Resume is a visible example in the current API result: its summary describes a resume builder, not a DSH plugin. HarnessBase keeps that rejected record to show the filter rather than silently inflating the total.
Provenance ledger
Evidence sources used on this page
- Official Official DeepSeek Harness repository ↗
Canonical identity, quick start, Developer Preview status, source workflow, and plugin architecture.
- Repository GitHub dsh-plugin topic ↗
Discovery input only; topic membership is not compatibility evidence.
- Direct test HarnessBase three-plugin load matrix
Pinned package install, configuration dump, UI load, restart, and cleanup on isolated Windows profiles.
- Direct test HarnessBase vision plugin reproduction
Reproduced 0.1.4 loader failure and verified the 0.1.5 repair on two DSH process starts.
- Community r/DeepSeek plugin-loader report ↗
Discovery lead with an exact error signature. Reporter environment and repair were not supplied; HarnessBase reproduced the versioned failure independently.
- Repository dsh-deepseek-vision package and repository ↗
Published 0.1.4/0.1.5 artifacts and changelog used to explain the tested rc.7 compatibility change.
- Repository @sugarforever/dsh-lark repository ↗
Credential, network, configuration, and package identity evidence for 0.2.2.
- Repository dsh-oomol repository ↗
Published 0.1.4 client artifact was compared with the stable loader diagnostic.
- Community 01Coder plugin-development tutorial ↗
Publisher-caption implementation walkthrough; used as a research lead, not a compiled compatibility result.