Overview

DeepSeek Harness (DSH) adopts a “everything is a plugin” design philosophy. Because plugin sources are scattered across the npm registry and GitHub repositories, finding and selecting suitable plugins is highly search-dependent. The dsh-plugin-market plugin adds a Market page inside DSH, simplifying plugin discovery and decision-making through automatic discovery, presentation, and model review.

Plugin Introduction

This is a built-in plugin for DeepSeek Harness, maintained by duxingxiake3.

Core value:
1. Automatic discovery: Automatically discovers DSH plugins from the npm registry and GitHub.
2. Visual presentation: Displays plugin capability descriptions and author-provided screenshots.
3. Security review: Reviews plugins with a model before any plugin is installed.

Core Features

  • Market page: Adds a dedicated plugin market entry point in the DSH client.
  • Information aggregation: Displays plugin name, developer, license, homepage, and summary information.
  • Pre-installation review: Assesses plugin content risk using a model before the user approves installation.
  • Post-installation management: After a plugin is installed, the built-in Plugins page is responsible for enabling, configuring, and uninstalling it. The Market page only provides link navigation.

Installation and Enablement

The plugin supports installation via the DSH UI, command line, or manual configuration.

1. Install via the DSH UI

  1. Open Plugins → Add plugin.
  2. Enter the package name dsh-plugin-market and approve installation.

Enter the following content directly in the Add plugin interface:

dsh-plugin-market

Or point to the repository (applicable when the npm package has not been published):

github:duxingxiake3/dsh-plugin-market

3. Manual Installation

Add the dependency and plugin entry point to the user-configured package.json:

{
  "dsh": { "profile": { "bundles": ["…", "dsh-plugin-market"] } },
  "dependencies": { "dsh-plugin-market": "link:/path/to/dsh-plugin-market" }
}

After configuration, you need to restart DSH.

Access Methods

After installation, you can open the plugin market using any of the following methods:
* The Plugin Market icon in the sidebar (located next to the built-in Plugins button).
* The Settings → Built-in plugins → Market tab.

Plugin Author Guide

Plugin authors don’t need to take additional action to be automatically discovered in the market, but they must follow a specific directory structure for proper presentation.

Directory Structure

Create a dsh-market folder at the root of the plugin repository and place the presentation content inside it:

your-plugin/
├─ package.json          # "icon" 字段指向此文件夹内的 logo
├─ README.md
└─ dsh-market/
   ├─ market.json        # 描述、开发者、截图列表
   ├─ logo.svg           # 插件图标
   └─ screenshots/       # 截图目录
      ├─ dashboard.png
      └─ settings.png

Field Description

  • market.json: Contains displayName (display name), summary, description, homepage, license, and the screenshots array.
  • logo.svg: Used as the icon in the Market list.
  • package.json: The icon field is used by the Plugins page and should point to ./dsh-market/logo.svg.

Path Rules (Important)

  • Paths in package.json are relative to the package.json file and are used for local file resolution.
  • Paths in market.json (such as logo or screenshots[].url) are relative to the repository root and are used for reading from GitHub.
  • Package-relative paths (such as ./dsh-market/logo.svg) cannot be used as repository paths in market.json, as this will cause a 404 error and fall back to the default icon.

Notes

  • Restart requirement: DSH must be restarted after manual installation.
  • Automatic reload: When DSH is running, browser components reload automatically; no manual refresh is needed.
  • Screenshot domain restriction: Screenshot URLs in market.json are only allowed to point to permitted hosts (such as raw.githubusercontent.com). Other domains are rejected to protect user privacy.
  • Permission execution: The plugin runs with the permissions of the current DSH process. It is recommended to inspect the source code and license before installation.

References