AI Agent Hub
Back to plugins
dsh-version-inspector preview

dsh-version-inspector

Client Updated 2026.08.24

Run the following command in DeepSeek Harness:

dsh plugin install NEVSTOP-LAB/dsh-version-inspector

Paste the following prompt into your AI chat to install this plugin:

Install the dsh-version-inspector plugin into DeepSeek Harness from https://github.com/NEVSTOP-LAB/dsh-version-inspector

About this plugin

When managing multiple plugins under DeepSeek Harness, diagnosing version conflicts or verifying environment consistency often requires manually digging through node_modules and cross-checking package.json files — slow and error-prone. dsh-version-inspector consolidates all of this into the DSH settings panel, giving you a single at-a-glance view.

It renders versions in a collapsible tree split into three groups: the DeepSeek Harness core with its top-level dependencies, other plugins registered through the Cordis Loader, and this plugin's own dependency subtree. Each entry displays the resolved real version, the declared semver range, its dependency category (dependency, peer, or optional), and the resolution path. Dependencies the host cannot resolve — such as client-only packages or uninstalled optional peers — are highlighted in a warning color while still showing their declared range, making potential conflicts easy to spot. The layout uses an auto-fill multi-column grid so long lists spread horizontally with minimal scrolling, and a search box filters by package name or version instantly, with results grouped and counted by section.

Styling is driven entirely by DSH theme tokens, adapting seamlessly to both day and dark modes and matching the look of existing settings pages. All data is collected read-only by the Host; the client makes a single same-origin fetch the first time the page opens, and all subsequent expand and collapse operations remain in memory with zero extra network calls. Ideal for DSH developers and ops engineers who frequently switch Harness versions, maintain multi-plugin stacks, or need to keep environment configurations aligned across a team.

Screenshots

Use Cases

  • Verify actual loaded plugin and harness versions after an update
  • Diagnose version conflicts or peer-dependency resolution issues in a multi-plugin stack
  • Confirm environment configuration consistency across team members

Best For

  • DSH developers maintaining multi-plugin stacks
  • Ops engineers who need consistent environment configurations
  • Plugin authors debugging dependency resolution issues