Port / PID / app / project
See listeners
Search Windows TCP listeners by port, application, PID, project, and Session.
A Windows port-inspector plugin for DeepSeek Harness DSH Web
Every local port
has a story.
In the DeepSeek Harness DSH Web UI, see who is listening, which Session started it, and whether the port was actually released after handling.
Windows / DSH Web / TCP listeners
Why it exists
A port conflict is only the symptom. The missing context is the real problem.
Task Manager can show a PID. DSH can manage Jobs and Terminals. What is missing is a chain you can verify between the two.
- Which project owns this port?
- Which Session and Tool Call started it?
- Was the port really released after stopping it?
Port Inspector brings the Windows listener snapshot and DSH launch evidence into one view.
Capabilities
From discovery to cleanup, the evidence stays in view.
It is not a general task manager. It is a DeepSeek Harness runtime inspection and local port-origin tool for Coding Agent workflows.
Session / Turn / Tool Call
Trace origins
Match the Windows parent chain to a DSH root process. Only complete evidence earns “Started by DSH”.
Managed / External / Read-only
Handle safely
Managed Jobs and Terminals use DSH lifecycle APIs. External handling is limited to one identity-verified PID.
Fresh scan / portReleased
Confirm release
Run a fresh scan after every action and report whether the target port was actually released.
How it works
It connects two worlds without hiding the evidence.
From the Windows listener to the DSH Tool Call, each step remains understandable and reviewable.
-
Listener snapshot
Read current TCP listeners and record the address, port, PID, application, and creation time.
-
Root identity
Observe the root process created by DSH and keep PID plus creation time to guard against PID reuse.
-
Origin check
Walk the parent chain and connect the listener back to its DSH Session, Turn, Step, and Tool Call.
-
Human confirmation
Review the project, origin, and handling mode before stopping a managed resource or ending one external PID.
-
Fresh scan
Scan again after handling to confirm the target port is released while other services remain intact.
Product evidence
Not a guess. A chain you can review.
The real interface shows the port, project, starter, and handling mode. Each state answers a different question.
Origin and handling are separate
“Started by DSH” describes origin evidence. “Can stop” describes the available lifecycle handling path.
Current project first
The UI prioritizes the current project and identified development toolchains while keeping other listeners searchable.
Degrade locally
Incomplete origin evidence or permissions keep the record visible, but the handling capability stays read-only.
Safety boundary
The allowed path and the unsafe shortcut are both explicit.
Safe handling is a boundary defined by evidence, permissions, and user confirmation, not a hidden shortcut.
Read-only by default
The port list is for diagnosis. Models can read bounded, redacted information, but cannot terminate through the Tool.
Identity recheck
Before termination, verify PID, creation time, and executable. If the target changes, refuse the action.
Local impact
Handle one explicitly selected target at a time. Never kill an external process tree or elevate automatically.
Capability fallback
System, protected, other-user, or insufficiently identified targets remain view-only.
It is not a general task manager, and it does not label every still-useful background service as a leak.
Support scope
Made for local Windows development with DeepSeek Harness Coding Agents.
The first release focuses on one frequent, real-world path: multiple local services running in DSH Web on Windows.
Windows local
The first release targets Windows local execution and TCP listeners.
DSH Web
Install as a standard Bundle and open Port Inspector from the Web sidebar.
Development toolchains
Useful for local Vite, Node.js, Go, Python, and Docker Compose services.
Get started
Turn the next port conflict into a question you can answer.
Install this DSH Web plugin, restart the target DeepSeek Harness Web Profile, then open Port Inspector from the sidebar.
Restart the target Profile after installing or updating the Bundle. Origin records begin with the new DSH runtime cycle.
Install with npm PowerShell
dsh plugin --profile web add dsh-port-inspector@latest RequirementsWindows / Node.js >= 22.19.0 / DSH Web Profile
FAQ
A clear boundary before you install.
What kind of DeepSeek Harness plugin is it?
Port Inspector is a Windows local development port-inspection plugin for DSH Web. It connects TCP listeners, processes, projects, Sessions, and Tool Calls in one reviewable origin chain.
Does it automatically close every background service?
No. Port Inspector is read-only by default. Handling starts only after an explicit selection and identity recheck.
Does it support macOS or Linux?
The Windows MVP does not target macOS, Linux, UDP, remote hosts, cross-restart history, bulk termination, or automatic governance.
What happens when origin evidence is incomplete?
The listener can still be shown. Its starter becomes unconfirmed, and insufficient permissions or identity keep handling view-only.
Does it start another local server?
No. It works as the Host and Browser halves of a standard DSH Bundle without starting a second companion Web service.