DSH / GUIDE

DeepSeek Harness plugin concepts

Catalog labels answer how you use a record, not jargon for its own sake. These are the words people get stuck on first.

Plugin

A Cordis-loadable runtime module. It may contribute model tools, UI slots, configuration, or client capabilities. Built-in plugins ship in the Harness source snapshot; community plugins are usually published as installable bundles.

Bundle

A patch or manifest layer used to activate a profile or deliver capabilities. It is not a synonym for “any Git repository”. Built-in profile layers are Harness-owned bundles; external installable records are also bundles, but with their own repository and install command.

Profile layer

A built-in activation layer applied through a bundle patch. It usually cannot be installed with the CLI on its own; it is enabled with a profile such as web or headless.

Installable

Has pinned public source and a distribution contract, so `npx dshpub add …` works. The catalog only shows an install command when that contract is present, and CLI install counts only cover those completed reports.

Included in DSH

Already shipped in the pinned deepseek-ai/deepseek-harness source snapshot. There is nothing to install again—open the source and check which profiles include it.

Ecosystem find

A candidate from the public ecosystem index. It is for discovery only: not a claim of compatibility, installability, review, or safety. The source repository remains canonical.

CLI installs

Completed installs reported by the dshpub CLI. Direct Git clones or native DSH installs are invisible here, and the number is not unique users.

Runtime anatomy

Host-loadable, web client, UI surface, model tools, data & storage, and workflow. The checklist only lists capabilities verified as present; “not inspected” does not mean absent.

Next