Install & uninstall plugins in the DSH plugin market

Install & Get StartedPublished 2026-08-28Author: DSH Plugin Hub
DeepSeek HarnessDSH pluginplugin marketinstall pluginuninstall plugin
In the DSH Plugin Hub market, installing a plugin means finding it in the Plugin Center, clicking Install, confirming the dialog and waiting for progress; uninstalling means switching to the Installed list, clicking Uninstall and confirming. Step-by-step for both, compared with the dsh plugin add / remove commands, plus where to verify and whether data is kept.

The DSH plugin market (DSH Plugin Hub Plugin Center) turns install and uninstall into button clicks: installing = find the plugin in the market, click Install, confirm the dialog and wait for progress; uninstalling = switch to the Installed list, click Uninstall and confirm. This guide walks both operations from entry to completion, compares them with the dsh plugin add / remove commands, and covers where to verify the result and whether uninstalling keeps your data.

Overview: install and uninstall in one table

In the plugin market, neither install nor uninstall needs a command; everything is visual, and both operations share one entry — Settings → Plugin Center. At a glance (source):

StageMarket pathEquivalent command underneathResult
Installmarket → find the plugin → Install → confirm → progressdsh plugin --profile web add <package>card flips to Installed, badge +1
UninstallInstalled → find the plugin → Uninstall → confirm → progressdsh plugin --profile web remove <package>row disappears, config and data kept

Step 1: how to install a plugin from the market

Installing takes five steps: find, click Install, review, confirm, wait. Prerequisite: DSH Plugin Hub is installed. Steps:

  1. Open the DeepSeek Harness Web UI → Settings → Plugin Center (the entry exists once DSH Plugin Hub is installed);
  2. Type the plugin name or keyword in the search box, or narrow the range with the category filter, until you find the target plugin;
  3. Click the Install button on the plugin card;
  4. Review the plugin name, source repo and the command that will run in the confirm-install dialog, then confirm;
  5. Wait for the install progress to finish (shown live in the dialog), then refresh the page — the card button changes to Installed.

You can cancel an install at any time; the installed-count badge in the top navigation increments by one when it finishes. Fallback: if the progress is stuck, cancel and retry, or switch the npm mirror and click Install again.

dsh-plugin-hub · confirm install
DSH Plugin Hub confirm install dialog

Step 2: how to uninstall a plugin from the market

Uninstalling offers several entry points, all with visible progress. Steps:

  1. Open Settings → Plugin Center;
  2. Pick an entry: switch to Installed in the top navigation and find the plugin in the list; or locate the plugin card directly in the market;
  3. Click the Uninstall button, review the plugin and its source in the confirm-uninstall dialog, then confirm;
  4. Wait for the uninstall progress to finish — the plugin is removed from the list/card immediately.

Uninstalling only removes the plugin itself; configs and sessions under $DSH_HOME stay untouched, so you can reinstall any time (source); fully cleaning leftover cache directories is a separate manual step. Fallback: on a failed uninstall, read the dialog — reinstall the npm build on package conflicts and retry, or restart dsh web first.

dsh-plugin-hub · confirm uninstall
DSH Plugin Hub confirm uninstall dialog

Compared with the command line: two equivalent ways

Clicking buttons in the market and typing commands in the terminal drive the same add / remove underneath — the results are identical. Two ways:

Fully visual: search, click buttons, watch progress, and dialogs keep a trace when something goes wrong. Best for everyday installs and uninstalls, especially for beginners; follow Steps 1 and 2 above — no commands needed.

Way 2: the command line (for scripts and batch work)

Fits scripting, batch processing, or when you would rather skip the UI. Prerequisite: you know the package name. Steps:

bash
# Install (equivalent to clicking Install in the market)
dsh plugin --profile web add <package>

# Uninstall (equivalent to clicking Uninstall in the market)
dsh plugin --profile web remove <package>

# List installed plugins (confirm the result of either operation)
dsh plugin --profile web list

Fallback: a mistyped name returns 404 — verify with npm view <package>; on command not found, prefix with npx @deepseek-ai/dsh (source).

Troubleshooting common issues

When an install or uninstall fails, read the failure dialog first, then fix accordingly. Common issues:

IssueLikely causeFix
No Plugin Center entryHub not installed or not activereinstall with dsh plugin --profile web add dsh-plugin, restart dsh web, refresh
Install progress is stuckslow network, unstable npm mirrorcancel and retry, or switch the npm mirror and install again
Not active after installpage not refreshed, wrong profilerefresh the page or restart dsh web; verify --profile web
Plugin still there after uninstallpage not refreshed, progress unfinishedrefresh the page; confirm the progress ended
Uninstall failspackage conflict, leftover files in useread the dialog, reinstall the npm build and retry, restart first
Disk space not freed after uninstallonly the dependency was removedReveal in Finder, then clean leftover directories manually
Want a plugin back after uninstallingdata kept, dependency removedjust reinstall — configs and sessions under $DSH_HOME are untouched

If you cannot pinpoint it, open Settings → System logs for the full error and follow the matching guide.

Quick recap

In short: install = click Install in the market, confirm and wait; uninstall = click Uninstall in the Installed list, confirm and wait — no commands involved. Four reminders:

  1. Review the confirmation dialog before installing: verify the source repo and the command that will run;
  2. Refresh and verify after installing: refresh the page or restart dsh web; the plugin must show up in the Installed list;
  3. Uninstalling keeps your data: only the dependency is removed — configs, credentials and sessions under $DSH_HOME stay, so reinstalling restores it;
  4. The CLI is equivalent: add installs, remove uninstalls, list confirms — handier for scripts and batch work.

Sources: dshplugin/dsh-plugin-hub, dsh CLI README

FAQ

How do I install a plugin from the DSH plugin market?

Install DSH Plugin Hub first (dsh plugin --profile web add dsh-plugin), open Settings → Plugin Center, find the target plugin with search or categories, click Install on the card, review the source and command in the confirmation dialog, then confirm. The install runs in the background with live progress; refresh the page when it finishes.

How do I uninstall a plugin from the DSH plugin market?

Open Settings → Plugin Center, switch to Installed in the top navigation, find the plugin in the list, click Uninstall and confirm. The plugin disappears once the live progress completes. You can also click Uninstall directly on the market card.

Do I need to type commands to install plugins from the market?

No. Market installs are fully visual: click Install, review the confirmation dialog, and watch the progress. The dialog shows the dsh plugin --profile web add command that will run so you can verify the source, but you never type it; the CLI route requires running dsh plugin --profile web add <package> yourself.

Does uninstalling from the market delete configuration or data?

No. The market uninstall only removes the plugin dependency from the profile; configs, credentials and sessions under $DSH_HOME are untouched. Manually cleaning plugin cache directories is a separate, optional step. The command line behaves the same with dsh plugin --profile web remove <package>.

What should I do when an install or uninstall fails?

Read the reason in the failure dialog first: reinstall the npm build if the package is incomplete, switch the npm mirror and retry on network issues, or use an official channel for untrusted sources. Every attempt lands in the notification center and system logs for full-context troubleshooting.

Sources