AI Agent Hub
Back to plugins
🖥️

dsh-mod-manager

Client Updated 2026.08.15

Run the following command in DeepSeek Harness:

dsh plugin install HamSamMike/dsh-mod-manager

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install HamSamMike/dsh-mod-manager in your terminal to install the plugin (source repository: https://github.com/HamSamMike/dsh-mod-manager); after installation, restart dsh web once and the Mod Manager panel will appear under Settings.

About this plugin

Once you have several third-party plugins living inside a DeepSeek Harness Web profile, switching one off usually means cracking open cordis.patch.yml, typing a disabled: true line, and praying the YAML still parses. dsh-mod-manager turns that into a single click: open Settings, go to Mod Manager, see every registered plugin with its live status, and flip it on or off. The change propagates through the patch watcher as a hot-update, so you rarely need to restart dsh web.

Its discovery is deliberately narrow: it reads only the dsh.profile.bundles explicitly declared in the target profile package.json, never scans arbitrary node_modules, and never touches plugin source code. While auto-discovery handles the common cases, config.mods gives you an escape hatch for friendly display names or Loader row IDs that the matcher cannot resolve. Every write stays within the target profile cordis.patch.yml, wrapped in clearly marked boundary blocks so any unrelated user-patch entries you already have are preserved untouched.

It does not install or uninstall plugin packages for you. Each target bundle must already be added to the same profile, and a one-time dsh web restart is needed after a new install so the Loader picks it up. After that, day-to-day toggling, reordering, and combination testing all happen right in the settings panel. It is built for developers who run three or more plugins in Harness Web and are done hand-editing YAML every time they want to change which features are active.

Use Cases

  • Toggling multiple third-party plugins on and off inside a single Web profile
  • Avoiding repeated manual cordis.patch.yml edits for each enable or disable cycle
  • Verifying which installed bundles are actively loaded by the Loader after a restart

Best For

  • Developers running three or more third-party plugins in a DeepSeek Harness Web profile
  • Engineers who frequently switch plugin combinations during feature testing
  • Teams that want fewer YAML hand-edit errors and lower day-to-day config maintenance overhead