How plugin-manager behaves
plugin-manager adds a Store tab under the DeepSeek Harness Web UI settings area. DeepSeek Harness loads the plugin in the web profile. The tab displays entries from the dsh-suite catalogue and supports browsing, search, filtering and sorting. Catalogue entries include descriptions and compatibility badges.
The catalogue is maintained outside the plugin: dsh-suite refreshes its data hourly and runs daily compatibility checks by installing collected packages into temporary profiles. plugin-manager displays those catalogue results; the README does not describe a separate local catalogue database or a configurable refresh process.
Installing through plugin-manager
Selecting an entry starts one-click installation through DeepSeek Harness. The README identifies the plugin package as @dsh-suite/plugin-manager and places the store in the Web UI rather than describing a separate command exposed by the store itself. After adding plugin-manager to the web profile, restart the Web UI and open Settings → Plugins → Store.
The installation action can add other DeepSeek Harness plugins to the profile. Because the supplied metadata flags a terminal surface and a credentials requirement, review the permissions and credentials available to DeepSeek Harness before using one-click installation.
Requirements and limits
The documented integration is the DeepSeek Harness Web UI and its web profile. The README provides no version requirement, configuration key, environment variable, supported-platform list or additional command for plugin-manager. It also does not document an offline catalogue, alternative profile targets, or an installation approval setting.
Compatibility badges are catalogue results, not a guarantee that every plugin will work in the current environment. The catalogue’s own checks run in temporary profiles, while the selected installation occurs in the DeepSeek Harness profile using the Web UI.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub