dsh-insight-tree

After introducing several third-party plugins into DeepSeek Harness (DSH), a recurring pain point emerges: the Profile declares a stack of dependencies, yet the Loader loading stage, the plugins actually engaged in the current session, and the root cause of a startup error all live in separate places—config files, node_modules, runtime context, and session logs—without a single pane of glass. dsh-insight-tree closes that gap by merging six observation dimensions (installation, assembly, loading, compatibility, session usage, and upstream versions) into one schema v3 explainable report, turning the workflow into find-impact-act.

Its core capabilities span three areas. While DSH is running, users can open a plugin tree in the navigation bar to inspect structure, dependencies, Loader state, and compatibility, and view per-session plugin activity on the conversation page. An independent diagnostics page launches without the full DSH Web UI; even when DSH is completely offline it can read the Profile and package metadata, then execute disable, reload, or uninstall operations with automatic backup and dry-run validation before any mutation. Finally, when DSH fails to start and the wrapper command attributes the error to a non-core plugin, the diagnostics page opens automatically—while core-host failures simply print a manual diagnostic hint without false-positive alerts.

This plugin is well suited for developers managing multiple DSH plugins who want a unified observability view, ops engineers who need fast root-cause attribution on startup failures, and any user who wants to confirm compatibility boundaries before updating or removing a plugin. It is not a plugin marketplace nor a security auditor; it answers the operational question of what is installed, how it is running, and what to do next.