dsh-port-inspector

Once a Coding Agent spins up several local dev servers, familiar questions pile up: which Vite instance is the browser actually hitting? Why is port 8080 still listening after the task is done? Which of the three node.exe entries in Task Manager belongs to which project? DSH Port Inspector closes this gap inside DeepSeek Harness Web by tracing every TCP listener back through the Agent tool call that started it, mapping each port to its application, project, Session, Turn, Call ID, and launch mode so you stop guessing at port ownership.

At its core, Port Inspector presents a consolidated view of listening ports across the project and the system, showing PID, application, and bind address, while distinguishing the current DSH session, other DSH sessions, and plain external processes. For DSH-managed Jobs and Terminals it performs identity-verified shutdown through the lifecycle owner; for external processes with complete identity evidence it allows a single same-user PID termination after a safety check. Additional capabilities include Docker Compose project association, a root-to-listener launch chain view, search/filter/sort by port, app, PID, project, and session, one-click copy of redacted details, and an automatic fresh scan after every action that reports whether the port was actually released.

It is built for developers who run DSH Web on Windows and regularly let their Agent start local dev servers, APIs, databases, or other tooling, especially those juggling multiple projects or DSH Sessions with same-named processes. If you need to resolve port conflicts without accidentally killing another project or service, Port Inspector separates attribution from action authority, recommends shutdown only when evidence is sufficient, and never auto-cleans background services or escalates to forced termination.