DeepSeek Harness (DSH) has a flexible plugin-based architecture, but developers often encounter module conflicts or internal runtime errors when extending its functionality. Diagnosing these issues typically requires diving deep into the code. The dsh-conflict-checker plugin provides the ability to detect conflicts and manage plugin states directly from the settings page, aiming to simplify this maintenance process.

What It Is

This is a DSH client plugin maintained by TussalZeus18028. It mainly addresses two issues: first, it detects plugin conflicts and internal runtime problems in DeepSeek Harness; second, it provides plugin management features (enable, disable, uninstall) in the settings page.

Core Features

1. Conflict Detection
The plugin scans multiple potential conflict sources, including:
* Duplicated module loading
* Failed or hanging fibers
* Duplicated settings namespaces
* Duplicated tool names
* Startup graph issues
* Duplicated typert packages

2. Plugin Management
In the settings page, users can toggle plugins on or off. The uninstall action includes a two-step confirmation mechanism to prevent accidental removal. Each plugin can display detailed information.

3. One-Click Repair
For detected issues, the interface displays issue details and corresponding solutions, and provides a repair button where applicable.

4. UI Style
The plugin is rendered as a “Plugin Conflict Check” page in the settings, using official theme tokens to maintain visual consistency.

Installation and Enablement

Install it using the command line:

dsh plugin --profile web add dsh-conflict-checker

Alternatively, add the entry directly to the configuration file cordis.patch.yml:

- id: dsh-conflict-checker
  disabled: false

Typical Usage

After installation, open the Settings page and go to Plugin Conflict Check.

The page will display:
* Health Overview: plugin count, enabled/disabled status, and issue statistics.
* Issue List: shows detected issues and their solutions.
* Plugin List: includes search and filtering, with toggles to enable/disable plugins, as well as uninstall and detail-view actions.

How It Works

The plugin works by combining client-side rendering with host-side interfaces:

  1. Host Side: Registers JSON endpoints under the /plugins/dsh-conflict-checker/* path of the shared web server, responsible for scanning plugins, setting enabled states, and removing plugins.
  2. Client Side: Responsible for rendering the settings page and calling the JSON interfaces provided by the host side.

In terms of detection logic, the plugin enumerates the entries read by the Cordis Loader and further checks the Loader, settings namespaces, tool schemas, web startup graph, and typert registry.

Notes

This plugin runs with the permissions of the current DSH process. Please review the source code and license carefully before installing. The DSH philosophy is “everything is a plugin”; the community catalog has no official affiliation with DeepSeek or High-Flyer.

Summary

dsh-conflict-checker lowers the barrier to diagnosing DSH plugin issues by providing a visual interface for conflict detection and plugin management. Developers can quickly locate and attempt to fix runtime issues when they occur.