DeepSeek Harness (DSH) uses a plugin architecture. Developing local plugins installed via file: or link: usually requires handling the file system and package.json in a terminal. dsh-plugin-dev provides a management panel in the web interface to simplify this workflow.

This is a DeepSeek Harness web plugin maintained by baihejiangnan. It scans package.json files in development directories, identifies plugins installed via file: or link:, and provides a UI for managing them.

Core Features

Local Plugin List
Scans each profile’s package.json files and lists packages installed from development root directories via file: / link: as candidates. Only projects that users explicitly add enter development management.

Explicit Add/Remove
Users can explicitly click to add a project to development management in the panel’s “Projects Pending Addition”. Projects can also be removed at any time. Registration uses resolved real paths and does not modify the managed plugins.

Open File Explorer
Uses the official Harness workspace service to open the plugin source directory in the system file explorer.

Discuss GitHub Upload
Creates a safety-confirmation session in the plugin workspace. The plugin itself does not execute git or gh commands. The panel pre-fills the repository name, visibility, description, and risk constraints, then waits for the user to confirm in the session.

Discuss Updates
Plugins with an associated remote start an update-check session. The model must first perform a read-only check, present the changes and risks, then stop and wait for explicit user confirmation before taking any action.

Continue Development
Starts a workspace session in the plugin directory and sends a “continue development” prompt to begin the conversation.

Similarity (Reserved)
Planned follow-up feature: similarity detection for similar plugins on GitHub.

Install and Enable

Run the following command in the terminal to install the plugin:

dsh plugin --profile web add "github:baihejiangnan/dsh-plugin-dev"

After installation, you must restart DSH and hard refresh the web page.

Typical Usage

Add a Local Plugin

dsh plugin --profile web add link:<本目录绝对路径>

Remove a Plugin

dsh plugin --profile web remove @baihejiangnan/dsh-plugin-dev

Security and Dependencies

Dependencies
Creating development conversations relies on the host’s workspaces / sessions services (included in the web bundle). The plugin does not directly run Git or GitHub CLI. If a user explicitly authorizes the model to upload after reviewing risks in the session, actual execution still depends on local Git and an installed, logged-in GitHub CLI (gh auth login).

High-Risk Operation Limits
Uploading and updating are high-risk operations. The panel only creates conversations with safety constraints; it does not automatically commit, push, or create repositories. The safety-confirmation prompt requires the model to first perform a read-only check, present the intended steps, then stop and wait for explicit user confirmation in the session.

Configuration and Directories

Default Configuration
The default development workspace is ~/Documents/herness. The registry is stored in DSH_HOME/plugin-dev/projects.json (default: ~/.dsh/plugin-dev/projects.json).

Multiple Workspace Configuration
To configure multiple development workspaces, set the environment variable DSH_PLUGIN_DEV_ROOTS. On Windows, separate multiple absolute paths with semicolons.

Directory Structure
The core plugin files are in lib/index.js (host-side routing) and lib/client.js (client settings panel), and the mount declaration is in cordis.patch.yml.

License

MIT