The fastest DeepSeek Harness download/trial is not an .exe. Upstream’s homepage path is: install Node, then run npx @deepseek-ai/dsh web. That fetches @deepseek-ai/dsh (developer-preview builds on npm) and serves the Web UI—docs often default to http://127.0.0.1:3080.
This site documents Clash Verge Rev. npx is “npm download + start” inside a shell. Restricted networks often fail here even when the browser looks fine. Concepts: what Harness is. Proxy acceptance: Harness + Clash Verge. Full checkout: git clone install.
Before the one-liner: three checks
-
Node: 22.19+ or 24+ per upstream docs. Run
node -v. - Fresh shell: If you need a proxy, start Clash, then open a new terminal for npx.
-
Expected URL: After listen logs appear, open
127.0.0.1:3080(or whatever the process prints).
You do not need plugins or a full clone first. Preview commands move—follow deepseek-ai/deepseek-harness.
Run: npx @deepseek-ai/dsh web
npx @deepseek-ai/dsh webThe first run downloads the CLI and deps. When the UI is up, configure a DeepSeek (or other adapted) API key. Smoke with list-dir / read-file—not “refactor the monorepo.”
| Symptom | Likely layer | Next |
|---|---|---|
| npx hang / ETIMEDOUT | npm egress | Tun or HTTPS_PROXY, retry |
| Instant engine errors | Node version | Upgrade into the documented range |
| UI up, tasks fail | Key / tools / model | Do not reinstall Clash first |
| UI up, overseas tool timeouts | Agent child egress | Proxy article + connections page |
When Clash Verge must come first
npx uses the shell network stack. System-proxy “on” does not fix Node that ignores it. Long-running agents: Tun in Clash Verge (Windows often needs Service Mode). Temporary trials:
-
HTTP_PROXY=http://127.0.0.1:MIXED_PORT -
HTTPS_PROXY=http://127.0.0.1:MIXED_PORT
Use the port shown in the app (often 7897). Overview: Tun & AI. Shell notes: CLI proxy. Client builds: download center—that installs the proxy client, not Harness itself.
How this splits from source installs
npx is for “see the UI today.” Source is git clone → pnpm install → pnpm run build → pnpm dsh web for plugins and mainline work. Both can hit the same egress class of failures; npx is mostly npm, clone also needs GitHub. Details live in the source article.
Acceptance and stop rules
Pass: npx reaches listen, browser opens the UI, key saves, read-only smoke works. If fetches keep failing, change only the network layer once. If the UI works but tools still need overseas egress, move to the proxy guide—do not loop on reinstalling dsh.