Preface¶

When maintaining profile plugins on the DSH web end, manually editing configuration files to enable, disable, or delete combined rows can easily lead to overlooking statuses and makes it inconvenient to confirm which row is currently active. dsh-plugin-manager provides a Web UI entry point that consolidates search, status display, enable/disable/delete operations in one place. After operations, it writes to cordis.patch.yml and takes effect immediately via HMR hot reload.

What This Is¶

monk233/dsh-plugin-manager is maintained by monk233 and is MIT licensed. It is used for DeepSeek Harness Web UI, targeting the web client platform, with the current version being 0.1.0.

Below is the verified information related to installation and dependencies:

version: 0.1.0
license: MIT
peerDependencies: "@deepseek-ai/cordis": "^4.0.1"
dsh.bundle.patch: ./cordis.patch.yml
dsh.client.platform: web

Core Features¶

Plugin Management Entry in Settings¶

The entry point is: Settings → Plugin Management.

On this page, you can do the following:

• Search for plugins;
• View status badges;
• Execute enable, disable, or delete via the ⋮ menu;
• Disable and delete actions require secondary confirmation;
• The page automatically refreshes after operations.

Configuration Writing and Hot Reload¶

Operation results are written to cordis.patch.yml.

Verified capabilities include:

• HMR hot reload takes effect immediately;
• Core components are protected;
• Built-in plugins can only be disabled.

Installation and Activation¶

Option One: git clone + dsh¶

First clone the repository, then prepare the commands, and finally install to the web profile:

# 1) Clone the repository
git clone https://github.com/monk233/dsh-plugin-manager.git
cd dsh-plugin-manager

# 2) Prepare commands (if not installed, take effect in a new terminal)
npm install -g @deepseek-ai/dsh pnpm

# 3) Install to the web profile
dsh plugin --profile web add .

After installation, be sure to restart the DSH service.

Option Two: Let the AI Install¶

Using DSH creation mode, open a session and send the following text to the AI:

Install this plugin https://github.com/monk233/dsh-plugin-manager.git

After installation, you also need to restart the DSH service, then go to “Settings → Plugin Management” to check the plugin status.

Typical Usage¶

Here is a set of steps you can follow directly:

1. Go to “Settings → Plugin Management” and use the search to locate the target plugin.

2. Confirm whether it is currently enabled or disabled via the status badge.

3. Click the ⋮ menu and select enable, disable, or delete.

4. If you choose disable or delete, complete the secondary confirmation first.

5. After the operation, the page automatically refreshes; modifications will be written to cordis.patch.yml, and HMR hot reload takes effect immediately.

6. If you want to disable dsh-plugin-manager, you can only modify the configuration file manually and restart to re-enable it, or have the AI modify it within dsh.

7. If you want to delete dsh-plugin-manager, you can have the AI delete it within dsh.

Applicable Scenarios and Notes¶

Suitable for scenarios where you need to manage DSH profile plugins in the Web UI and want to reduce manual configuration file editing.

Notes before use:

• The plugin runs with the current dsh process permissions; check the source code and MIT license before installation;
• Core components are protected; built-in plugins can only be disabled;
• Be sure to restart the DSH service after installation;
• After disabling or deleting dsh-plugin-manager, recovery is limited to configuration file editing or AI modification, and you cannot rely on the plugin’s own interface for continued operations.

Conclusion¶

The value of dsh-plugin-manager lies in bringing the enable, disable, delete, and status viewing of DSH web profile plugins into the Web UI, and reducing manual configuration steps through cordis.patch.yml and HMR hot reload.

GitHub repository:

https://github.com/monk233/dsh-plugin-manager