dsh-restart-confirm

In DeepSeek Harness, the Web UI and the harness backend live in the same process. Restarting used to mean closing the terminal, killing the PID, and re-typing the exact launch command with every flag intact. dsh-restart-confirm collapses that into a small icon in the sidebar and two deliberate clicks: the first dialog asks "restart?", the second is a final warning. Cancel either one and nothing happens. Only the second confirm fires.
When confirmed, the plugin follows a graceful-kill-then-relaunch path. It sends SIGTERM first and escalates to SIGKILL only if the process lingers. The relaunch command is not hardcoded; it is reconstructed from the running process itself (execPath plus argv, same working directory), so whatever launcher you used originally—CLI, PWA, supervisor script—reproduces exactly. The client does not wait a fixed 15-20 seconds: it polls the health endpoint for a changed bootId and reloads the moment the new process is ready, making the whole cycle feel nearly instantaneous.
The button itself is carefully pinned via DOM placement next to the sidebar fold toggle, adapts its icon size between the expanded row and the 56-px rail, and a MutationObserver keeps it locked through re-renders. Colors read directly from DSH CSS custom properties, so light and dark themes follow automatically. On the security side, the restart endpoint accepts only loopback POST requests, and the plugin never transmits data externally.
It is built for local DSH Web UI developers—especially those who launch the harness through a PWA, remote desktop, or supervisor script and would rather not memorize the full command line. Once installed, restarting DSH is as effortless as a page refresh, with a built-in safety net on every step so an accidental click never interrupts a live session.