Interactive failure router · verified 2026-08-15
Find the first broken boundary.
Do not reinstall everything. Select the earliest observable failure and collect one discriminating piece of evidence.
01 / Symptom
What failed first?
01 No Web URL appears Process exits or never becomes ready 02 Remote Web UI is empty Workspace and provider lists do not load 03 Workspace cannot open Folder picker, invalid path, or wrong scope 04 The model turn fails Authentication, endpoint, TLS, or streaming 05 A tool does not execute Arguments, approval, policy, or provider 06 The shell is denied Policy denial versus unavailable isolation 07 History or continuation is wrong Persistence, replay, queue, or route inheritance
Process Start here
Confirm the host stays alive
The first boundary is process startup—not the browser, workspace, or model provider.
Collect first The launch command, Node and DSH versions, and the complete terminal tail.
Success signal The process remains alive and prints a reachable Web URL.
First command
npx @deepseek-ai/dsh web
Copy command
02 / Next move
Keep the launch terminal visible.
Do not diagnose the browser until the URL is printed.
Preserve the first error and its cause chain.
03 / Guardrail
One variable per run.
Use a disposable workspace. Never paste credentials, full settings, private paths, or an unredacted session log into an issue. A final assistant sentence is not evidence; prefer terminal output, durable events, artifacts, diffs, and exit status.