Introduction¶

The philosophy of DSH is “everything is a plugin.” By the time you finish installing, your profile is often a mix of official plugins, npm packages, repositories cloned from GitHub, and local directories. Whenever package content changes, the process must be restarted. Consequently, questions like “what is currently installed,” “which plugins can be upgraded to a new version,” and “how to move this machine to another one” require typing commands one by one in the terminal, making it easy to miss items or accidentally delete them. The dsh-plugin-keeper introduced below is designed to address this daily operational burden. It only manages what you have already installed; it does not provide a plugin marketplace, nor does it support hot restarts.

What is it¶

dsh-plugin-keeper is a plugin operations dashboard for DeepSeek Harness (DSH 0.2.x), maintained by HelloQingTao. It is categorized as admin-security in the community plugin directory (the directory page currently shows 0 stars). It aggregates the plugins of the current profile into a single panel, grouped by source. It provides batch updates, start/stop, uninstallation, export/import, direct GitHub installation, and search capabilities.

One-sentence positioning: It is not a plugin discovery or installation source, but a manifest and batch operations console for installed plugins.

Core Features¶

All capabilities provided by the panel can be verified in the README:

• View all plugins of the current profile in one place, grouped by source: Official / npm / GitHub / Local.
• Check which plugins have new versions (the badge corresponds to the latest version on npm/GitHub) and update them in batch.
• Batch enable, disable, and uninstall plugins.
• Export selected plugins along with their configuration into a zip file and import it on another machine.
• Install plugins directly from GitHub.
• Search by package name, description, or version, highlighting the matched parts.

Note the boundaries: It only manages installed plugins and does not act as a plugin marketplace; operations that change package content, such as updates and uninstallations, require a restart of the host process to take effect, whereas enabling and disabling take effect immediately.

Installation and Enablement¶

The installation command comes from the original README:

dsh plugin add dsh-plugin-keeper

After installation, restart DSH, as package content changes require a process restart to take effect. The runtime requirements are Node >=20 and DSH version within the range >=0.2.0-rc.2 <0.3.0.

Typical Usage¶

The panel is accessible via the sidebar “Plugins” -> “Plugin Ops / Plugin Ops” tab, or by opening a named entry in the Settings page. The operation workflow is: select the rows to be processed -> select an action -> a popup lists the package names to be processed -> confirm to execute.

The README provides four onboarding checks, which can serve as a minimum verification process:

1. Open the sidebar “Plugins” -> “Plugin Ops” and check if plugins are grouped by source and if the total count matches dsh plugin ls.
2. Click “Check Updates” and verify that the latest version on the badge matches the npm/GitHub web pages.
3. Check a non-official plugin, execute “Batch Disable,” and the row status should immediately change to “Disabled”; re-enabling it should restore it immediately.
4. Enter a package name fragment in the search box; the list should converge and highlight the matched parts; press Esc or click × to restore the full list.

The convention for export and import is: export downloads a zip via the browser; copy it to the target machine and import; import displays what will happen first, and executes only after confirmation.

Use Cases and Notes¶

Suitable for three scenarios: exporting installed plugins and importing them on a new machine when replacing hardware; centrally cleaning up excessive plugins by unchecking them and batch disabling or uninstalling them; and daily maintenance to see which are outdated, followed by batch updates.

A few reminders:

• Plugins run with the permissions of the current DSH process. Check the source code and license before installing. The license for this repository is MIT.
• Updates and uninstallations do not take effect immediately; the process needs to be restarted after execution.
• This plugin comes from the community. The community directory is an independent site with no official affiliation to DeepSeek or Huafan; do not treat it as an official app store.
• Exported packages contain plugin configurations. Be careful about credentials and environment-related items when sharing or migrating.

Conclusion¶

The value of dsh-plugin-keeper lies in moving the question of “what is installed and whether to modify it” from the command line to a selectable checklist. It lists the affected package names before batch operations, reducing the risk of accidental operations. It does not solve plugin discovery, nor does it change DSH’s requirement that package content changes must trigger a restart; its positioning is clear.

Directory Page: https://www.skillhub.cn/plugins/HelloQingTao/dsh-plugin-keeper

GitHub: https://github.com/HelloQingTao/dsh-plugin-keeper