DSH is a plugin-based architecture, and its runtime environment involves multiple dimensions such as configuration, loading state, session activity, and version compatibility. When plugin behavior is abnormal or startup fails, troubleshooting often requires consulting multiple scattered information sources. dsh-insight-tree aims to consolidate these sources into an explainable report and provide a visual management interface, helping developers complete the loop of “discover the issue → assess the impact → take action.”

What It Is

This is a runtime observability and plugin diagnostics panel for DeepSeek Harness (DSH). It is maintained by user xingzhen199186 and uses the MIT License. The plugin merges Profile configuration, actual installed packages, Loader runtime state, session activity, and upstream version information to generate an explainable report, and provides support through a plugin tree, current round activity, and a standalone diagnostics page.

Core Features

Comprehensive Report Generation
The plugin merges Profile configuration, actual installed packages, Loader runtime state, session activity, and upstream version information to generate an explainable report. The report is based on the InsightTreeReport model (current schema is v3), and all interfaces consume this report to avoid logic inconsistency.

Plugin Management
It can manage installed non-core plugins in the current Profile: disable, re-enable (reload), update, or uninstall. Before making changes, it performs a static configuration dry-run; if it fails, the original file is preserved.

Standalone Diagnostics
It provides a standalone command-line diagnostics tool. Even if DSH itself is not running, you can start the standalone diagnostics page, read the Profile, check plugin status, and perform available disable, re-enable, and uninstall operations.

Startup Attribution
When DSH fails to start, it attempts to automatically attribute the issue to a non-core plugin. This is implemented through the wrapper command dsh-insight-tree-web; the standalone diagnostics page opens automatically only when the error is explicitly attributed to a non-core plugin in the report.

Compatibility Checks
It provides version and dependency compatibility checks to determine whether a plugin is compatible with the DSH core and related packages.

Installation and Activation

Install into DSH from npm:

dsh plugin --profile web add dsh-insight-tree

After installation, restart DSH Web to make the host, client bundle, and cordis.patch.yml assembly take effect:

schtasks /run /tn DSHWebRestart

Typical Usage

After successful installation, it can be used as follows:

  • Plugin Tree Panel: After starting DSH, open the panel via “Settings → Plugins → Plugin Tree” to view the plugin’s structure, capabilities, dependencies, compatibility, and Loader status.
  • Current Round Activity: Open “Current Round Activity” on the right side of the chat page to view the plugin activity actually present in the current conversation.
  • Command-line Standalone Diagnostics: Run the following command in the command line:
dsh-insight-tree-diagnose --profile web --port 3092

Then visit http://127.0.0.1:3092/.

  • Wrapper Command: Use the wrapper command to start diagnostics:
dsh-insight-tree-web --profile web

Applicable Scenarios and Notes

Applicable Scenarios
- You need to confirm which plugins are actually assembled in the Profile.
- You need to verify whether the Loader has loaded the plugins correctly and what stage it is currently in.
- You need to check compatibility between the current plugin and the DSH core plus related packages.
- You need to view which plugin capabilities were actually used in the current session.
- You need to independently inspect and handle plugin configuration when DSH is not running.

Notes
- It is not a plugin marketplace and not a third-party plugin security auditor.
- The HTTP service listens on loopback only and supports token authentication.
- A static configuration dry-run is performed before changes; if it fails, the original file is preserved.
- Uninstallation of a plugin that other plugins depend on is rejected.
- The actual availability of Loader, session projection, and session query depends on whether the DSH host provides the corresponding services.
- When a tool event has no explicit owner, only a stable mapping or an “unconfirmed” label can be used; precise attribution cannot be guaranteed.
- Standalone diagnostics has no Loader runtime evidence, so it will not fabricate a “currently running” state.
- When required context is missing, it displays “temporarily unable to confirm”; it does not misreport unknown as “incompatible.”

The plugin has been published to GitHub: https://github.com/xingzhen199186/dsh-insight-tree