Preface¶
In DSH, plugins are typically installed, updated, and removed via the dsh plugin command. When dealing with multiple profiles such as web, headless, and other local profiles, the command-line approach can become cumbersome: you need to switch profiles repeatedly, and it’s not easy to quickly view which dependencies are installed under a specific profile.
Introducing @springbrand/dsh-plugin-marketplace. It is a visual plugin marketplace designed for DeepSeek Harness profiles, built into DSH Web settings and provided with SpringBrand Desktop. It is not an official app store but a community directory; the plugins themselves remain third-party code.
What is this¶
One-line positioning: A graphical directory, installation, update, and removal interface for DSH profiles.
Maintained by: springbrand-lab.
License: MIT.
Applicable locations: Settings → Plugin Marketplace in DSH Web settings, and SpringBrand Desktop.
It primarily solves the problem of managing plugin operations across web, headless, and other local profiles—along with searching the directory by name, author, description, or npm package—within a single visual interface.
Core Features¶
- Browse and Search: Find plugins by
name,author,description, ornpm package. - Profile Management: Covers
web,headless, and other local profiles; SpringBrand Desktop restricts operations to its active profile. - Install, Update, Remove: All completed within the same marketplace interface.
- Installed View: Simultaneously covers catalog entries and profile dependencies not listed in the catalog.
- Marketplace Self-Updates: Supports self-updates within SpringBrand Desktop.
- Activation Timing: Differentiates between changes to the current profile and changes to other profiles.
Installation & Enabling¶
First, ensure the environment meets Node.js >=22.19.
If DSH is not yet installed, install pnpm and DSH first:
npm install --global pnpm @deepseek-ai/dsh
Verify DSH is available:
dsh --version
Install the marketplace plugin for the web profile:
dsh plugin --profile web add @springbrand/dsh-plugin-marketplace
Start DSH Web:
dsh web
If DSH is already installed, you can execute directly:
dsh plugin --profile web add @springbrand/dsh-plugin-marketplace
dsh web
If dsh is still not found after reopening the terminal, use the npx method:
npx @deepseek-ai/dsh plugin --profile web add @springbrand/dsh-plugin-marketplace
npx @deepseek-ai/dsh web
After completing the steps above, open DSH Web in your browser and navigate to Settings → Plugin Marketplace to browse and search the plugin directory.
Typical Usage¶
- Open
Settings → Plugin Marketplaceand search by name, author, description, or npm package name. - Perform install, update, or remove operations for the selected profile.
- View currently installed packages in the Installed view, including catalog entries and profile dependencies not listed in the catalog.
- In standard DSH, manage plugins across
web,headless, and other local profiles; SpringBrand Desktop operates only on its active profile.
Configuration & Targets¶
The following fields can be overridden in the profile configuration:
profile
catalogUrl
restartDelayMs
profile: The profile used by standard DSH processes; SpringBrand Desktop uses its active profile.catalogUrl: The address of the plugin directory.restartDelayMs: Restart delay for standard DSH processes, ranging from500to30000milliseconds.
profiles/node_modules is not provided as a target.
Security & Notes¶
- Installation is limited to entries in the catalog marked as
bundle,installable, ornpm. - The server re-resolves npm package names from the catalog rather than accepting arbitrary sources from the browser.
- Updates and removals only accept valid npm package names already installed in the currently selected profile.
- Mutation endpoints only accept same-origin JSON POST requests with a body limit of
8 KiB. - Standard DSH commands are started with argument arrays and not executed via a shell.
- Only one plugin operation runs at a time.
- Plugins are third-party code; inclusion in the directory does not imply a security endorsement. You should inspect the source code, dependencies, and licenses before installation.
This plugin executes related plugin operations in the context of the current DSH process’s environment, so you should verify the source is trustworthy and check the license before installation.
Uninstallation¶
You can remove it from the Installed view in the marketplace or execute:
dsh plugin --profile web remove @springbrand/dsh-plugin-marketplace
Conclusion¶
The value of @springbrand/dsh-plugin-marketplace lies in centralizing plugin browsing, installation, updating, removal, and viewing of installed dependencies for DSH profiles within Web settings. It is ideal for DSH users who need to manage multiple local profiles or prefer to view the plugin directory within the DSH Web interface.
Directory entry: Settings → Plugin Marketplace in DSH Web.
GitHub: springbrand-lab/dsh-plugin-market