dsh-service-board: A Session Service Panel for DeepSeek Harness

What Does It Do?

DSH Service Board is a DSH plugin for DeepSeek Harness that shows, in the Web GUI sidebar, which conversation (agent session) started which service. It solves the problem of unclear service ownership and invisible process state when several sessions run in parallel, gathering ports, HTTP codes, PIDs, start time and uptime into one docked panel. It is a patched fork of the upstream dsh-process-board, maintained by fanjinduo111 under the MIT license, with a focus on Windows.

Core Features

• Session-grouped service list: one row per service with a tri-state health dot, HTTP code, port badge (including bind address), PID, start time and uptime.
• Live log band: selecting a service expands a tail below the list, with ERROR in red and WARN in yellow, a 4-second refresh, scroll pinning and a full-panel view.
• In-place restart with command replay: confirm inside the panel (the dialog shows the exact command line), then stop the process tree, relaunch it detached with the original command line and inject the log marker.
• Polite stop: after in-panel confirmation it sends SIGTERM/taskkill, waits a 10-second grace period, then force-kills the tree; SCM-managed Windows services are labeled "Windows service" instead of offering a stop button.
• Docked panel and filtering: the panel occupies the right side while app content slides aside, its width is draggable (300–1000px) and remembered, and it supports scope, port allow-list and hide-keyword filters.
• Upstream fixes: logs no longer turn into "log unavailable: no-log" after a restart, the scanner no longer merges same-named launchers with same-named services, and the panel no longer steals composer focus with native dialogs.

How to Use This Plugin?

Once enabled in DSH, a "process panel" entry appears in the sidebar; opening it gives you the docked panel on the right, where services are listed per session. For the panel to see your services, start them with the environment markers: the log-file marker lets the panel read that process's log, and the session marker decides which conversation it belongs to. On Windows you can set the environment variables in PowerShell and launch the process hidden, or register a service directly with its name, command line and working directory so the panel's start button can replay it. Day to day, click "log" to expand the live tail, click "restart" to confirm in-panel and replay the original command line (it waits one 1–3 second scan before refreshing), and click "stop" for a polite termination; Esc steps back through log fullscreen, panel fullscreen and collapse.

How to Troubleshoot This Plugin?

• After a restart, the log shows "log unavailable: no-log": this was an upstream defect; the fork now makes the restart request wait until a scan sees the new process, so a brief "running…" state is expected.
• A service disappears from the list and its port is attributed elsewhere: the scanner used to merge same-named launchers with same-named services as master/worker; it now requires matching non-empty command lines and never merges descendants carrying the log marker.
• The composer stops accepting typing after a stop or restart: the panel used window-level modal dialogs that stole focus; it now shows messages inside the panel and returns focus to the element that was active before opening.
• Logs are nearly invisible in the light theme: older builds referenced theme tokens that do not exist, and now use real theme variable combinations.
• Installing it alongside the upstream project inserts two sidebar entries; keep only one of them.