buhuikongpan/dsh-pluginmanager
30Last commit Aug 15, 2026
dsh-pluginmanager DSH plugin
dsh-pluginmanager transforms the flat 100+ plugin list in DSH Web settings into a three-layer architecture view: native extensions, user extensions, and running instances. It offers search, enable/disable, uninstall, and register operations, plus a built-in description system for 90+ core plugins.
How to install the dsh-pluginmanager DSH plugin
dsh plugin add github:buhuikongpan/dsh-pluginmanagerCopying does not run this command. Review the repository and version before installing the dsh-pluginmanager DSH plugin.
dsh-pluginmanager DSH plugin data source
dsh-pluginmanager DSH plugin snapshot date: Aug 16, 2026
discovered
What the dsh-pluginmanager DSH plugin can do
- Three-layer architecture view (native, user, running) with counts
- Enable/disable/uninstall user extensions with hot-reload
- Search filter by name, display name, description, or source
- Edit descriptions for any plugin (persisted to local file)
- Register manually installed plugins into dependency management
Where the dsh-pluginmanager DSH plugin fits
- Quickly locate and manage plugins when you have 100+ installed
- Safely uninstall or disable user extensions without breaking the system
- Understand the plugin architecture of your DSH instance
- Add custom descriptions to remember what each plugin does
- Migrate from patch-based installation to bundle-based management
Who the dsh-pluginmanager DSH plugin is for
- DSH power users who install many plugins
- Plugin developers and maintainers who need to understand the plugin system
dsh-pluginmanager DSH plugin limitations
- Native extensions are read-only and cannot be uninstalled through this plugin
- Hot-reload may disconnect active sessions (e.g., running terminals); changes persist after restart
dsh-pluginmanager DSH plugin: from the repository README
Quoted from the buhuikongpan/dsh-pluginmanager README, the upstream source of the dsh-pluginmanager DSH plugin. Copyright remains with the original authors.
> 你的 DSH 装了 100 多个插件？恭喜，你现在拥有了一座没有楼层指示牌的摩天大楼。 > 这个插件就是那张楼层指示牌——顺便把"哪层能拆、哪层是承重墙"给你标得明明白白。 **dsh-pluginmanager** 是 DeepSeek Harness Web 的设置页插件管理器。它把全部插件从一张 100+ 行的大平铺（谢谢你，原生 `all` 标签页）整理成**三层架构视图**，让"看懂 DSH 的插件体系"这件事从"考古"变成"观光"。 --- ## 🏗️ 它到底解决了什么 DSH 的插件体系很强大，但原生的插件清单长这样： ``` @deepseek-ai/dsh-llm @deepseek-ai/dsh-tool-bash @deepseek-ai/dsh-client-ui-theme @deepseek-ai/dsh-agent-loop @deepseek-ai/dsh-tool-fs @deepseek-ai/dsh-client-ui-sidebar @deepseek-ai/dsh-session @deepseek-ai/dsh-tool-web ... （还有 90 多个，它们全在一个列表里，平等地糊你一脸） ``` 谁负责 Agent 大脑？谁负责界面？谁是模型能调的工具？你装的扩展又混在哪？——**都看不出来**。 这个插件把混沌整理成了架构： ``` ┌─────────────────────────────────────────────┐ │ dsh-pluginmanager 总览 │ │ │ │ ┌───────────────────────────────────────┐ │ │ │ 原生扩展 [N] › │ │ ← 点进去：系统层 / WebUI 层 / 工具层 │ │ 系统层 · WebUI 层 · 工具层 │ │ │ ├───────────────────────────────────────┤ │ │ │ 用户扩展 [M] › │ │ ← 点进去：补丁行 / 扩展包 / 依赖 │ │ 补丁行插件 · 扩展包 · 依赖 │ │ │ ├───────────────────────────────────────┤ │ │ │ 运行中（临时） [K] › │ │ ← 当前会话的动态 Cordis 插件 │ │ 当前会话的动态
Read the full READMEThe repository declares no license. Check with the authors before using it.
dsh-pluginmanager DSH plugin questions
Why isn't my installed plugin showing up in the User Extensions section?
The plugin manager only shows plugins that have active loader entries in `cordis.patch.yml`. If you only ran `npm i` but didn't add an activation line, it won't appear. Use the 'Register' button in the User Extensions section to add it to dependencies and ensure the activation line exists.
What does the 'Unregistered Dependency' tag mean?
It means the plugin was manually placed into `node_modules` without being declared in `package.json`. Click 'Register' to formally add it to dependency management, so the marketplace and other tools can recognize it.
Can I edit the descriptions of native plugins?
Yes, you can edit the description of any plugin by clicking the edit icon. The custom description is saved to `~/.dsh/profiles/web/plugin-manager/descriptions.json` and persists across restarts.
I get 'duplicate loader entry id: pluginmanager' on startup. What should I do?
This means the plugin is activated twice — once via bundle and once via a manual patch line. Open `~/.dsh/profiles/web/package.json` to check `dsh.profile.bundles`, then open `cordis.patch.yml` and delete the line `- id: pluginmanager` (including its `insert:` block). Keep only the bundle activation.
Does hot-reload affect other plugins or break my session?
Hot-reload restarts the target plugin within the same process. If that plugin has active sessions (e.g., a running terminal), those sessions will be disconnected. The operation is persisted, so changes take effect after a full restart as well.