Stop dsh processes before uninstalling DeepSeek Harness

Stop background processes before uninstalling dsh, because DeepSeek Harness leaves several long-running or semi-persistent processes: the profile process started by the CLI dsh web, the session process from dsh --profile headless that exits when its task finishes, and the desktop Host process. They hold the runtime, the profile and file handles, so step-by-step cleanup is blocked outside the door.

This guide covers three steps: which processes to stop, why a port stays busy, and how to locate and finish off leftover processes and ports. The uninstall commands and per-platform paths are in Ways to uninstall dsh.

Which processes to stop before uninstalling dsh

Stop three kinds of processes before uninstalling: the long-running web profile process from dsh web, the session process from dsh --profile headless (which exits when its task finishes), and the desktop Host process (source).

Find all three with commands first:

1. List dsh and Node processes — On macOS / Linux run pgrep -fl dsh or ps aux | grep -i deepseek; on Windows run tasklist | findstr /i "dsh node". Expected: all related processes and their PIDs are listed.
2. Tell long-running from one-off — Check whether the command line is dsh web (long-running, listens on a port) or dsh --profile headless "..." (exits when done). Expected: you can separate what holds resources long term from what you can leave alone.
3. Check the desktop Host process — A Host runs while the desktop is open. Expected: it disappears after you quit the desktop, releasing the single-instance lock on profiles/desktop.
4. End the long-running processes one by one — On macOS / Linux use kill <pid>; on Windows use taskkill /F /PID <pid>, preferring a normal exit when possible. Expected: related entries vanish from the process list and the runtime and handles are released.

Step 2 saves effort: a headless session process exits by itself when the task finishes and usually needs no manual action; the ones that need work are the long-running dsh web and the desktop Host. Do not treat a one-off as long-running, and do not assume a long-running one costs nothing.

Why a port stays busy after uninstall: the desktop opens none, dsh web does

The official docs state the desktop app opens no web port; only the profile process started by the CLI dsh web listens on one. So a port still in use after uninstalling DeepSeek Harness is almost always a dsh web process that did not exit, not an incomplete uninstall (source).

Confirm the port owner with commands:

1. List listening ports — On macOS / Linux run lsof -i -P | grep LISTEN; on Windows run netstat -ano | findstr LISTENING. Expected: ports with their PIDs are listed.
2. Map the PID back to a process — On macOS / Linux use ps -p <pid> -o pid,command; on Windows find the PID in Task Manager details. Expected: you confirm whether the PID is a Node / dsh process.
3. Confirm it is dsh web — Check whether the command line contains dsh web or --profile web. Expected: a match means it is a CLI-started long-running process, unrelated to the desktop.
4. End it and recheck the port — After ending the process, rerun step 1. Expected: the port leaves the listening list, confirming the occupation is over.

Step 3 explains a common misread directly: "I uninstalled the desktop, so why is the port still there?" Because that port was never opened by the desktop. The desktop opens no web port; a coexisting dsh web process is the listener. Knowing the owner prevents repeated uninstalls.

Locating and finishing off processes and ports after uninstall

The finishing order is "find processes by name, map ports to a PID, match the two, then exit gracefully", force killing only an unresponsive process so a process writing packages is not interrupted (source).

Run in order with a verifiable expectation each step:

1. Check leftover processes again — On macOS / Linux run pgrep -fl dsh; on Windows run tasklist | findstr /i node. Expected: you confirm whether any dsh / Node process remains.
2. Check ports again — Run lsof -i -P | grep LISTEN / netstat -ano | findstr LISTENING. Expected: you confirm whether the port is released.
3. Check the desktop restart reminder — Open the DSH Plugin Hub notification center. Expected: a "restart pending" note means the process must exit to finish; quit the desktop and recheck.
4. Prefer a graceful exit — Exit from the UI or send a normal termination signal when possible. Expected: the process finishes and releases its profile and locks with no half-finished state; force kill only an unresponsive one.

Step 4 matters: force killing a process writing packages means a failed plugin change keeps partial modifications without rollback, per the official docs, so do not force kill what a normal exit can finish. Once processes exit and ports free up, uninstall and cleanup stop fighting each other.

Notes on stopping processes before uninstalling dsh

1. Headless usually needs nothing: it exits when the task ends; only handle it if it hangs without exiting.
2. The desktop opens no port: a busy port is a dsh web process, not a desktop uninstall issue.
3. Identify the owner first: map the port to a PID, map it back to a process, and confirm it is dsh / Node before acting.
4. Prefer a graceful exit: force kill can interrupt a package transaction and leave non-rollbackable partial state.
5. Processes first, then uninstall: once the runtime and handles are released, uninstall and directory cleanup go smoothly.

To see which tasks are still running and whether a restart is pending before or after uninstall, the DSH Plugin Hub notification center lists progress and reminders together, more clearly than scrolling processes in a terminal.

Sources: DeepSeek Harness CLI README (official repository), DeepSeek Harness desktop README (official repository), DeepSeek Harness source repository