Preface¶

The DSH ecosystem extends capabilities in the form of plugin bundles. A profile may already have multiple plugin packages installed. When installing, updating, uninstalling, or checking for new versions, operations can become scattered if you have to switch back and forth between the command line, the repository page, and the marketplace search.

dsh-plugin-manager is an independently distributable DSH bundle. It provides a categorized plugin manager in Settings → Plugins for managing installed plugin packages in Desktop and native Web profiles.

Basic Information¶

• Repository: TAOxxx7/dsh-plugin-manager
• Maintainer: TAOxxx7
• License: MIT
• Position: DSH Settings plugin manager bundle for Desktop and native Web profiles

Below are the key fields in package.json related to installation and runtime:

{
  "name": "dsh-plugin-manager-community",
  "version": "0.1.3",
  "engines": {
    "node": ">=20"
  },
  "license": "MIT"
}

The npm package name used in the install command is dsh-plugin-manager-community. If the publisher renames the package, the package name in the install command needs to be updated accordingly.

Core Features¶

dsh-plugin-manager provides the following capabilities:

• Provides a categorized plugin manager in Settings → Plugins.
• Provides categorization for installed profile packages.
• Supports GitHub dsh-plugin marketplace search.
• Duplicate installation detection.
• Prefers npm installation when the marketplace repository publishes a DSH bundle.
• Falls back to GitHub for unpublished repositories.
• Supports uninstall, single-package update, update check, and startup check.
• Performs GitHub Release checks for source-installed plugins, supports semver tags, and uses commit-head fallback for unpinned sources.
• Explicit pnpm build approval/retry with diagnostic capture.
• Restart prompts after installation completes in Desktop and native Web.
• Maintains the same active-profile behavior in DSH Desktop and npx @deepseek-ai/dsh web.

Installation and Enablement¶

First, confirm that the current DSH runtime environment meets the Node engine requirement: >=20.

To install the latest community plugin package for the Desktop profile:

dsh plugin --profile desktop add dsh-plugin-manager-community@latest

To install the plugin package for the native Web profile and start the Web:

npx -y @deepseek-ai/dsh plugin --profile web add dsh-plugin-manager-community@latest
npx -y @deepseek-ai/dsh web

After installing an updated package version, you need to restart the current DSH process to load the new bundle layer. After a successful marketplace installation, the Settings tab will ask whether to restart.

Typical Usage¶

Viewing Installed Packages¶

After installation completes, go to Settings → Plugins. This will display installed profile packages along with their categories.

Searching and Installing Marketplace Plugins¶

Search for candidate plugin repositories through the GitHub dsh-plugin marketplace.

• If the marketplace repository has published a DSH bundle, npm installation is preferred.
• If the repository has not been published, GitHub fallback is used.
• Duplicate installation detection is performed before installation.

Updates and Uninstallation¶

The plugin manager supports:

• Uninstallation.
• Single-package updates.
• Update checks.
• Startup checks.

For source-installed plugins, GitHub Release checks are performed:

• Supports semver tags.
• Uses commit-head fallback for unpinned sources.

pnpm Build Approval and Retry¶

When the plugin workflow requires pnpm build to be executed, dsh-plugin-manager requires explicit approval/retry and captures diagnostic information.

Native Web Restart Behavior¶

A restart in native Web replaces the running Node process. Depending on when the browser request is made, the HTTP request that triggers the restart may show Failed to fetch. The current client recognizes this Web-only disconnect as an expected restart and displays a reconnecting state.

Windows Native Web pnpm Resolution Order¶

On Windows native Web, the pnpm resolution order is:

1. DSH_PNPM_BIN
2. active profile/shared DSH pnpm package
3. PNPM_HOME / npm global directories
4. PATH
5. Node.js Corepack

If none of the above locations are available, you need to install Node.js/Corepack, or set DSH_PNPM_BIN to the full pnpm.cmd path, then restart the Web process.

Applicable Scenarios and Notes¶

Suitable for people who manage profile plugin packages in DSH Desktop or native Web. This plugin consolidates categorization, marketplace search, installation, updates, uninstallation, and restart prompts into Settings → Plugins.

Notes before use:

• It runs with the current dsh process permissions. Check the source code, license, and package name before installation.
• dsh.client.platform is web, describing the browser interface, not a GitHub-only installation mode.
• lib/ is a release artifact copied from a validated Harness build.
• src/ is for review and future maintenance.
• Licensed under MIT.
• Requires Node >=20.

Conclusion¶

The value of dsh-plugin-manager is consolidating the viewing, searching, installation, updating, uninstallation, and restart prompts of DSH plugins into the Settings panel, reducing redundant operations between Desktop and native Web.

GitHub: https://github.com/TAOxxx7/dsh-plugin-manager

Index page: The index page URL does not appear in verified materials; this article does not complete it.