Configuring dsh-plugin-hub
The panel is added to the web profile at Settings → Plugins → Plugin Management. Search sources and installation registries are managed in the panel. Built-in search sources are GitHub and Gitee; custom sources use a URL template containing {q} and {page}. Custom sources may define request headers, including Authorization: Bearer .... Registry sources can be ordered, edited, restored to defaults, or removed unless protected because an installed plugin depends on them.
DeepSeek Harness stores the user-level enablement changes in $DSH_HOME/profiles/<profile>/cordis.patch.yml. The supported deployment target is the web profile. The repository also provides an optional framework patch script, scripts/apply-framework-patch.cjs, for tolerance of a top-level empty YAML array in cordis.patch.yml; a DeepSeek Harness upgrade can overwrite that patch.
dsh-plugin-hub behaviour
The installed-plugin view can search by name or ID, show status, and open package README summaries, versions and repository links. It initially shows third-party plugins, with an option to show all entries. Infrastructure entries such as timer, hmr and webserver are marked protected. GitHub search uses the browser first and falls back to the server; Gitee uses exact repository lookup with owner/repo or a full URL. “Official” filtering checks for a dsh.bundle manifest in a root package or eligible subpackage.
Commands and deployment files
The repository includes deploy.ps1 for Windows and deploy.sh for Linux and macOS. These scripts copy the package into $DSH_HOME/profiles/<profile>/node_modules/ and add an enablement entry to cordis.patch.yml. The official dsh plugin installation path uses the repository's dsh.bundle declaration.
Requirements and known limits
DeepSeek Harness must be 0.1.0-rc.6 or another supported 0.1.0 release with dsh-client-modules and dsh-host-plugin-inventory. Host-code changes require restarting DeepSeek Harness; ordinary toggles use HMR and normally take about one to three seconds. The panel displays a warning after breaking releases such as 0.2 or 1.0. The optional AI fallback is disabled entirely by its panel switch, or requires authorisation after normal installation routes fail.
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