Preface¶
DeepSeek Harness (dsh) is an open-source agent runtime developed by DeepSeek, with the core design concept of “everything is a plugin”: models, tools, sandboxes, session storage, interfaces, and even the agent loop itself can be assembled using plugins. The official repository is currently in developer preview, and compatibility may change at any time. Project address: https://github.com/deepseek-ai/deepseek-harness
Since the preview version launched, community plugins have grown rapidly. The dsh-plugin topic on GitHub, npm keywords, and various awesome lists have emerged simultaneously, with uneven quality: some packages only piggyback on the keywords, some repositories do not have the dsh manifest field, and errors will only occur after installation. Searching on npm, checking READMEs, and then manually typing dsh plugin add is not convenient for daily use.
What dsh-store does is straightforward: it embeds a quality-checked plugin directory into dsh’s Web UI, allowing browsing, searching, installation, uninstallation, deactivation, and updates to be completed in the same interface. It is maintained by huguangyu666, licensed under the MIT license, and the community directory categorizes it as “interface enhancement”. It should be clarified first: the community plugin directory (https://deepseek-harness-plugin.com/zh-CN/plugins/) referenced in this article is an independent site and has no official affiliation with DeepSeek / Horizon Robotics, and dsh-store is not an official app store.
What is this¶
dsh-store is a plugin store that runs inside the dsh Web interface. The current version on npm is 0.5.2 (released on 2026-08-16), with the package name dsh-store, requiring Node.js >=22.5. The dsh.client.platform declared in package.json is web, meaning it is designed for the Web UI, not a headless process without an interface.
As of 2026-08-18, both the GitHub repository https://github.com/huguangyu666/dsh-store and the directory detail page show 4 stars. The directory page was added on 2026-08-15, and the latest push was on 2026-08-16.
The problems it solves can be divided into two layers:
1. Findability: Merge the npm registry (keywords:dsh-plugin), curated awesome-dsh-plugin, GitHub topic:dsh-plugin stars, and the runtime validation status from AdamPlatin123’s automatic radar into a single directory.
2. Installability: Use the official dsh plugin add/remove commands for installation, writing to the dsh.profile.bundles layer, and fall back to pnpm add with patch merging if installation fails. The README emphasizes that plugins with npm entries in the directory should be truly installable, not just a list that only links to repositories.
Regarding the number of included plugins, the copy on several sources is not completely consistent, and should be viewed separately by source instead of mixing them into a single “official total”:
- The function description in the repository README and the “More Introduction” section of the directory page state that there are 750+ plugins after merging the four sources.
- package.json, the npm description, and the “About this plugin” section of the directory page still state 550+ plugins and 11 categories.
- On the curated awesome side, the README gives the number 324 plugins and 11 categories; on the radar side, it states 194+ entries.
These numbers will change with directory refreshes, and shall prevail based on the actual loading of the store page.
Core Features¶
The descriptions of capabilities in the repository README and the directory page are consistent. The current version mainly includes the following sections.
Aggregated Directory and Badges. Search uses npm’s keywords:dsh-plugin; categories and “Curated” badges come from awesome-dsh-plugin; stars, repository, and update time come from GitHub topic searches; entries verified by the radar will have a “Radar Verified” badge. Curated plugins not published on npm do not offer one-click installation, and a GitHub link is provided on the card.
Quality Filtering. The backend will request the npm /latest endpoint for each package to check if package.json contains the dsh field (the genuine plugin marker), and packages without this field will be filtered out. Verification results are cached for 7 days. The README once provided a set of test metrics: approximately 250 packages were found via keyword search, and 222 remained after filtering. The npm search itself will mix in packages that piggyback on keywords, and this step is designed to keep noise out of the directory.
Installation and Uninstallation. The “Install” button on the interface calls the official dsh plugin add command, automatically reconciling dsh.profile.bundles; the “Uninstall” button uses dsh plugin remove and cleans up patch residuals. If the official path fails, it falls back to pnpm add with patch merging. Identified installed plugins merge three sources: bundles, dependencies, and patches.
Installed Plugin Management and Updates. Starting from version 0.5.0, installed plugins support “Deactivate / Activate”, which writes to disabled in cordis.patch.yml and takes effect via HMR without restarting. There is a “Check for Updates” button at the top, which can list updatable items and update them with one click. For changes that require a restart, the page provides “Restart Now”.
Entry Points and Commands. The client registers a “Plugin Store” button in the footer of the sidebar, and a corresponding section in the settings page, which opens /plugin-store when clicked. It also registers two commands:
- /plugin-store: Outputs the store address, the number of included plugins, the installed plugin list, and popular summaries
- /plugin-install <package-name>: Installs directly by package name, for example /plugin-install dsh-plugin-notify
Details and Caching. Clicking on a card shows the description, category, README summary (local first, npm fallback), and repository link. The directory is cached for 24 hours at ~/.dsh/plugin-store/catalog.json, and the “Refresh Directory” button on the page will force an update.
Installation and Activation¶
The installation command given on the directory detail page can be run in the DeepSeek Harness terminal:
dsh plugin add github:huguangyu666/dsh-store
For reproducible installations, the directory page recommends pinning the commit hash (replace commit with the actual hash from the repository):
dsh plugin add github:huguangyu666/dsh-store#commit
The README also provides a syntax with a profile, where the default target profile is web:
dsh plugin --profile web add dsh-store
Restart the corresponding profile after installation. The default address of the official Web UI is http://127.0.0.1:3080, and the store page path is /plugin-store, that is:
http://<dsh address>:<port>/plugin-store
After restarting, the “Plugin Store” entry should appear in the sidebar, and a corresponding section will be added to the settings page.
There is also an npm i dsh-plugin-store command in the README. The actual package name on npm is dsh-store, so this command does not match package.json. Please use the dsh plugin add github:huguangyu666/dsh-store command from the directory page for installation, and do not copy that npm command verbatim.
Plugins run with the permissions of the current dsh process, and may execute code during installation. Please check the source code repository and license before installing.
Typical Usage¶
The steps below come from the repository README and the page/command registration in the source code, and can be tested in order.
1. Browse the Directory
Open /plugin-store. The page supports search, filtering by category, and sorting by stars, recency, and name. The card will display curated badges, descriptions, authors, versions, and stars. Curated entries not published on npm can only jump to GitHub, and do not expect to be able to install them by clicking “Install”.
2. Install a Plugin
Click “Install” on the card. The store will use the official dsh plugin add command. After successful installation, click “Restart Now” for the new plugin to take effect in the current process.
You can also install directly in the chat:
/plugin-install dsh-plugin-notify
The prompt text in the source code states that this command will modify cordis.patch.yml, and dsh needs to be restarted for the installation to take effect. Replace the package name with the real npm name from the directory.
3. Deactivate, Activate, Uninstall
Installed plugins will show “Deactivate / Activate”. This step only writes to disabled in the patch, and takes effect in real time via HMR without restarting. Uninstallation uses dsh plugin remove and cleans up patch residuals.
4. Check for Updates
Click “Check for Updates” at the top, list the updatable items, and then update them with one click. The method for updates to take effect shall prevail based on the page prompt, and use “Restart Now” if a restart is required.
5. Configure a Proxy for Domestic Access to GitHub
Stars and some repository information go through the GitHub API. If the pull fails, the directory will still be available (the source code will issue a warning and continue), but the stars may be empty. You can write the proxy and target profile in ~/.dsh/plugin-store/config.json:
{
"proxy": "http://127.0.0.1:7892",
"profile": "web"
}
Environment variables can override the same-named fields:
- DSH_PLUGIN_STORE_PROXY: Overrides proxy
- DSH_PLUGIN_STORE_PROFILE: Overrides profile
Replace the proxy address with your actual local port. The 7892 in the proxy example is just a sample given in the README and not a fixed port.
6. View Store Summary
/plugin-store
When used without parameters, it returns the store URL, the number of included plugins, the installed plugin list, and the top few summaries sorted by stars.
Applicable Scenarios and Notes¶
It is suitable for the following types of users: those who are already using dsh web and want to find plugins in the interface instead of searching GitHub topics manually; those who need to distinguish between “curated / radar verified / GitHub-only” entries; those who want to use the official dsh plugin add/remove commands instead of manually modifying patches.
Please note the following points before use.
Permissions and Security. Plugins run with the permissions of the current dsh process, and can read local files, use configured credentials, and access the network. Directory inclusion and “Curated” badges are not security audits. You should open the GitHub repository to check the source code and license before installing. dsh-store itself is licensed under MIT, with the copyright statement Copyright (c) 2026 huguangyu666.
Platform Restrictions. package.json states that the client only injects the Web platform. For headless or profiles that do not run the Web UI, the sidebar entry and /plugin-store page will not appear as documented.
The Directory is Not a Full Mirror. The source code uses size=250 for npm searches and per_page=100 for GitHub topic searches. Curated awesome and radar entries are added on top, and the entire network’s plugins are not pulled all at once. When the GitHub API fails, the directory will still be available with entries from npm / awesome, but the stars may be missing.
Do Not Treat It as an Official Store. The official DeepSeek Harness repository only provides the plugin mechanism and the dsh plugin add command. There are other similar projects in the community such as dsh-market, plugin-hub, and workshop. The dsh-store README uses a comparison table to emphasize that it takes npm as the authoritative source and uses the dsh field for backend verification, which is the author’s own positioning and not an official evaluation.
Version is Still Iterating Rapidly. The repository was created on 2026-08-14, and has fixed defects such as blank store pages and deactivation indentation up to version 0.5.2. The dsh itself is still in developer preview. If the page is blank or installation fails after installation, first check the repository CHANGELOG and Issues before deciding whether to pin a specific commit.
Summary¶
dsh-store aggregates npm, curated awesome lists, GitHub stars, and radar validation into the dsh Web UI, uses the official dsh plugin add/remove commands for installation and uninstallation, and adds deactivation, update, and README summary features. For users who are already running the Web UI and do not want to maintain their own plugin list, it can put “findability” and “installability” on the same page.
Directory page: https://deepseek-harness-plugin.com/zh-CN/plugins/dsh-store/
GitHub: https://github.com/huguangyu666/dsh-store
npm: https://www.npmjs.com/package/dsh-store