dsh-plugin-hub: Plugin Manager & Marketplace Panel for DeepSeek Harness

noob-stupid/dsh-plugin-hub

UI & ExperienceVerified
Listed on 2026-08-20
Page last updated 2026-08-20

Adds a plugin manager panel to DeepSeek Harness for toggling plugins and browsing GitHub marketplace.

Enable or disable plugins with one click in the DeepSeek Harness web interface, and browse, search, and install dsh-plugin projects directly on GitHub.

install
dsh plugin --profile web add github:noob-stupid/dsh-plugin-hub
Category
UI & Experience
Platform
DSH-Plugin
Author
noob-stupid
Distribution
Plugin

dsh-plugin-hub Key Features

One-click toggle pluginsView plugin detailsGitHub plugin marketplaceInfrastructure protectionCompatibility warnings

dsh-plugin-hub Repository

noob-stupid
Publisher
noob-stupid
Repository
noob-stupid/dsh-plugin-hub
62
Stars
3
Forks
0
Watchers
1
Open issues
LanguageJavaScript
LicenseMIT License
Website
Repo last push2026-08-20 14:23:14
Repo created2026-08-14 16:39:43
Topics
deepseek-harnessdshdsh-plugindsh-pluginsgithubhelp-wantedplugin-managerplugin-market
Default branchmain

dsh-plugin-hub Repo Summary

dsh-plugin-hub is a plugin manager & marketplace DSH plugin for DeepSeek Harness (DSH), adding a plugin management panel to the DSH web interface. It enables one-click enable/disable of installed plugins and provides a GitHub-based plugin marketplace for browsing, searching, and installing dsh-plugin projects. This plugin solves the pain of manually editing config files and discovering new plugins, with core capabilities including toggling and viewing details of installed plugins, direct GitHub marketplace browsing, and instant HMR-based activation. Maintained by Noob-stupid under the MIT license, last updated in 2026-08, it currently supports DSH 0.1.0 series.

What core features does dsh-plugin-hub support as a DSH plugin?

  • Installed plugin management: Lists all plugin entries (name, load status, enabled status), supports one-click disable/enable. Disabling writes disabled: true to the user patch layer, enabling removes the entry, and HMR takes effect within 1 second.
  • Infrastructure protection: Marks 70+ lines of plugins on the host transport, hot-reload, storage, and settings chain as "protected", preventing toggling to avoid breaking hot-reload.
  • Detail panel: Each plugin can be expanded to view description, version, repository/homepage links, and README summary.
  • GitHub plugin marketplace: Defaults to searching dsh-plugin, shows npm package name, DSH plugin hints, and README summary; supports "Add & Enable" one-click install (falls back to github:owner/repo if npm fails).

How to install dsh-plugin-hub?

The recommended way is the official command, as the plugin declares the dsh.bundle official manifest, installing and enabling it in one command:

bash
dsh plugin --profile web add github:noob-stupid/dsh-plugin-hub

After installation, restart the dsh service, refresh the page, and navigate to Settings → Plugins → Plugin Manager. If network is restricted, use the deployment scripts (PowerShell for Windows, bash for Linux/macOS), which copy the plugin package into $DSH_HOME/profiles/<profile>/node_modules/ and append the enable entry to cordis.patch.yml.

Which DeepSeek Harness versions and platforms are compatible with dsh-plugin-hub?

Currently supports DSH 0.1.0 series (0.1.0-rc.6 and same-series versions), requiring the web profile to include dsh-client-modules and dsh-host-plugin-inventory. The panel reads the running @deepseek-ai/dsh-web-app version; if the official release introduces breaking changes (e.g., 0.2 / 1.0), the panel shows a compatibility warning with the repository address. The deployment script does not check versions; the panel warning is authoritative.

How does dsh-plugin-hub work internally?

DSH's web profile combines a bundle patch layer and a user patch layer (cordis.patch.yml), with patches using per-key override semantics. Plugin toggling simply appends/removes two YAML lines (e.g., - id: X + disabled: true) to the user patch layer; the config file watcher (HMR) recombines within 1 second after save, no restart needed (except for host code changes). The host side uses loopback HTTP routes (state / toggle / search / repo / install) to directly read/write the patch layer.

What security mechanisms does dsh-plugin-hub have?

All routes are restricted to loopback addresses; GitHub metadata is used only for discovering public plugins, npm installs go through full TLS verification of the registry; the marketplace search connects directly to GitHub from the browser, not through the server, avoiding man-in-the-middle risks.

View more DSH plugins at dsh-plugin.org

DSH-Plugin FAQ