Before installation: resolve identity and source

Open the repository or package page linked by the author. Confirm the package name, owner, install command, license, recent activity, and whether the plugin requests build scripts or external credentials. Do not infer identity from a GitHub Topic result alone.

  • Canonical repository and author match.
  • Package name matches the README command.
  • Latest commit and release are plausible for the current DSH preview.
  • Build scripts, environment variables, network, and filesystem needs are visible.
  • Remove or rollback route is known.

Use the current CLI help as the command authority

Plugin command syntax can change during Developer Preview. Inspect the installed CLI before pasting a command from a directory page.

Plugin command surface · shell
npx @deepseek-ai/dsh plugin --help

Verify in three layers

First confirm the package operation completes. Second confirm DSH discovers the plugin after any required restart. Third run one narrow feature task and record the actual result. If any layer fails, keep the result distinct rather than calling the plugin simply compatible or incompatible.

  • Install status: package operation.
  • Load status: plugin discovered by DSH.
  • Feature status: one named task succeeds or fails.
  • Permission observation: what the test actually touched.
  • Compatibility: tied to DSH, plugin, Node, OS, and date.

Current direct-test matrix

On DSH 0.1.0-rc.7, Windows 11 x64, and Node v24.11.1, HarnessBase directly tested three version-pinned packages. dsh-deepseek-vision@0.1.5 and @sugarforever/dsh-lark@0.2.2 installed and loaded normally across two starts. dsh-oomol@0.1.4 installed but failed at UI load twice because the keyed settings slot was missing options.key.

  • Vision 0.1.5: load verified; actual vision request remains Unknown.
  • Lark 0.2.2: load verified; message delivery and external permissions remain Unknown.
  • OOMOL 0.1.4: exact repeatable load failure; hosted MCP behavior remains Unknown.
  • No API key, external account, model call, or real secret was used.

Updates are compatibility events

Record the working pair before updating. After an update, rerun the same smoke test and keep the old failure or success result. A new release can fix installation while breaking behavior, or vice versa.

What still blocks indexing

The first three-package matrix and one version-pinned repair now exist. Broader source shapes, allowBuilds behavior, external feature calls, non-Windows environments, and more update/remove paths still need retained results before this becomes a general plugin-install reference.

Sources and evidence boundary

Primary sources establish product facts. HarnessBase labels direct testing separately and does not convert community observations into verified results.

Target query cluster: install DeepSeek Harness plugin · dsh plugin add · dsh plugin update · dsh plugin remove