dsh-env-inspector: A Machine Environment Self-Check Dashboard for DeepSeek Harness

What Does It Do?

webkubor/dsh-env-inspector is a DSH plugin for DeepSeek Harness that turns "what is actually installed on this machine" into a visual dashboard. It solves the pain of ports held by leftover processes, toolchain versions that require repeated terminal checks, and uncertainty about whether model credentials are configured, letting you see system status, CLI readiness, and listening ports at a glance inside the harness. Maintained by webkubor under the MIT license and written in JavaScript, it ships with zero runtime dependencies and never connects to the network, since all probing happens locally.

Core Features

• Live port overview with one-click release: detects every listening port and its owning process, terminates it safely when you click the ×, then re-runs the self-check automatically and decrements the KPI counters.
• Port safety guardrails: the DSH core port and host process are permanently locked, system-critical PIDs are blocked, the target PID is re-verified as actually listening before any kill, and termination escalates from SIGTERM to SIGKILL in two stages.
• Wildcard-listening warnings and dynamic port folding: ports bound to 0.0.0.0 get a yellow warning dot, while high dynamic ports (49152+) collapse into a drawer you can expand and release one by one.
• Command-line toolchain sniffing: two-column cards report the install and version status of 12 common tools including node, npm, pnpm, yarn, git, docker, mise, brew, codex, and claude.
• Credentials and plugin overview: configured model capabilities are highlighted in emerald green while unset variables appear as low-contrast grey tags, no secret is ever printed in plaintext, and the panel also lists loaded DSH extension plugins with their effective versions plus local IPv4/IPv6 interface addresses.

How to Use This Plugin?

After enabling it in DSH, open the "🖥️ 电脑环境" tab in the top navigation bar to load the dashboard: a four-metric Hero KPI row gives the overall picture, and the two-column grid cards below cover system status, toolchain, credentials, and ports. To clear a port conflict, find the port in the port card and click × to release it; the page refreshes itself and updates the counters. For high dynamic ports, expand the drawer first and then release them individually. All endpoints enforce same-origin checks and every probe runs on the local machine without reporting data to any external service.

How to Troubleshoot This Plugin?

If releasing a port fails, first check whether it belongs to the locked DSH core port or host process, which show a lock badge and cannot be terminated. If the PID verification fails, the process is no longer listening on that port, so refresh the self-check as described in the official instructions and retry. When a tool or credential shows as not ready, verify the corresponding command is available on the system PATH and that the relevant environment variables are set in the current session.