在 DeepSeek Harness（DSH）中，插件是核心。以往安装插件需要终端命令，配置则需要编辑配置文件。omdsh-plughub 为这些操作提供了一个集中的界面。

功能概览

omdsh-plughub 是一个插件中心插件，为 DSH 提供了一个集中的管理界面。它位于“设置” > “插件”标签页下，负责从可配置的上游管理插件的安装、更新、启用/禁用以及配置。

核心功能

界面与目录

在“设置” > “插件”下新增“插件中心”标签页。该插件会合并本地、注册表和 GitHub 源的目录信息。

安装与更新

  • 可用列表：显示可安装的插件。对于新版本，按钮高亮显示为“安装”。
  • 已安装列表：显示已安装的插件。
  • 更新逻辑：对于已安装的插件，如果上游有新版本，按钮显示为“更新”；否则按钮为灰色（直到有新版本可获取）。更新操作同样通过调用 dsh plugin 命令完成。

启用与禁用

在已安装列表中，插件可以独立启用或禁用。
* 不触碰 node_modules：禁用操作仅从层堆栈中移除依赖，不会删除或修改 node_modules 中的文件。
* 无法禁用的项目：模板包、插件中心本身以及模式系统保持开启，无法被禁用或卸载。

配置表单

每个已安装的插件都会根据其注册的架构（schema）自动生成配置表单。开发者无需为每个插件单独编写 UI，只需遵循 DSH 的规范即可。

进度与通知

操作进度通过事件流（event stream）显示。当配置发生变更时，界面顶部会显示重启横幅。

使用方式

UI 操作

开发者可以在浏览器中的“设置” > “插件” > “插件中心”标签页中：
1. 浏览可用插件目录。
2. 点击“安装”添加新插件。
3. 在“已安装”列表中展开插件，通过自动生成的表单进行配置。
4. 使用“更新”或“移除”按钮管理已安装插件。

命令行工具

插件提供了独立的命令行工具 omdsh-plughub，用于解析目录并在终端中运行安装程序。

注意事项

  • 更新按钮状态：在“已安装”列表中，如果当前版本已是最新，更新按钮为灰色，直到上游有新版本发布。
  • 配置变更：任何对配置的修改都会导致重启横幅出现。
  • 层堆栈管理：插件层在启动时组合，目前仅监视用户补丁层。因此，新安装的插件通常需要重启才能生效。
  • 依赖管理：禁用插件只是从层堆栈中移除依赖，并不影响 node_modules 中的文件。

总结

omdsh-plughub 通过 UI 统一了插件的安装、配置与管理流程，减少了手动编辑配置文件和终端命令的操作成本，是 DSH 生态中管理插件的重要工具。

  • GitHub: https://github.com/omdsh-plugins/omdsh-plughub
  • 目录: https://www.skillhub.cn/plugins/omdsh-plugins/omdsh-plughub

In DeepSeek Harness (DSH), plugins are core. Previously, installing plugins required terminal commands, and configuration required editing configuration files. omdsh-plughub provides a centralized interface for these operations.

Feature Overview

omdsh-plughub is a plugin hub plugin that provides DSH with a centralized management interface. It is located under the “Settings” > “Plugins” tab and is responsible for managing plugin installation, updates, enabling/disabling, and configuration from configurable upstream sources.

Core Features

Interface and Catalog

Adds a “Plugin Hub” tab under “Settings” > “Plugins”. This plugin merges catalog information from local, registry, and GitHub sources.

Installation and Updates

  • Available List: Displays installable plugins. For new versions, the button is highlighted as “Install”.
  • Installed List: Displays installed plugins.
  • Update Logic: For installed plugins, if a newer version is available upstream, the button displays as “Update”; otherwise, the button is gray (until a new version becomes available). The update operation is also performed by invoking the dsh plugin command.

Enabling and Disabling

In the installed list, plugins can be independently enabled or disabled.
* Does Not Touch node_modules: Disabling a plugin only removes its dependencies from the layer stack; it does not delete or modify files in node_modules.
* Items That Cannot Be Disabled: Template packages, the plugin hub itself, and the pattern system remain enabled and cannot be disabled or uninstalled.

Configuration Forms

Each installed plugin automatically generates a configuration form based on its registered schema. Developers do not need to write individual UIs for each plugin; they only need to follow DSH conventions.

Progress and Notifications

Operation progress is displayed through an event stream. When a configuration change occurs, a restart banner appears at the top of the interface.

Usage

UI Operations

Developers can use the “Settings” > “Plugins” > “Plugin Hub” tab in the browser to:
1. Browse the available plugin catalog.
2. Click “Install” to add a new plugin.
3. Expand a plugin in the “Installed” list and configure it using the auto-generated form.
4. Use the “Update” or “Remove” buttons to manage installed plugins.

Command-Line Tool

The plugin provides a standalone command-line tool, omdsh-plughub, for resolving the catalog and running installers in the terminal.

Notes

  • Update Button State: In the “Installed” list, if the current version is already the latest, the Update button is gray until a new upstream version is released.
  • Configuration Changes: Any modification to the configuration will cause the restart banner to appear.
  • Layer Stack Management: Plugin layers are composed at startup, and currently only user patch layers are watched. Therefore, newly installed plugins usually require a restart to take effect.
  • Dependency Management: Disabling a plugin only removes its dependencies from the layer stack and does not affect files in node_modules.

Summary

omdsh-plughub unifies the plugin installation, configuration, and management workflow through the UI, reducing the operational overhead of manually editing configuration files and running terminal commands. It is an important tool for managing plugins in the DSH ecosystem.

  • GitHub: https://github.com/omdsh-plugins/omdsh-plughub
  • Catalog: https://www.skillhub.cn/plugins/omdsh-plugins/omdsh-plughub