DeepSeek Harness Linux Install: Node and Web UI
Check Node and npm in your Linux shell, run a pinned official launcher from the intended project directory, and use the printed local Web UI URL. For SSH, forward that loopback service with your client. The site’s retained Linux HTTP test belongs to rc.7; verify current releases independently.
Sharing includes the public link only, without local progress or private configuration.
Start with this command
This is the narrow command relevant to this page. Read the checks below before changing flags, credentials or profile patches.
npx @deepseek-ai/dsh@0.2.0-rc.2 web1. Check the Linux runtime and launch directory
Run node --version and npm --version as the same user who will launch dsh. Distribution packages and version managers can resolve different Node releases, so keep the printed versions with your test record. Start in the repository you want to inspect.
If npm cannot fetch the package, capture the registry or network error first. If package resolution succeeds but the launcher fails, capture the first startup diagnostic. Avoid changing the model configuration before the process can start.
node --version
npm --versionWhat to check: The same Linux shell resolves both runtimes and prints their versions.
2. Launch locally or through SSH
Run the pinned version check and Web command below. A local desktop launch can open the browser; an SSH launch prints the host URL. Leave the server running and forward its loopback port through your SSH client or editor, then open the local forwarded address.
For a port conflict, select a different local port with web --port 3081 and forward that port if using SSH. The browser address must correspond to the process you just launched. A remote service bound to loopback will not become reachable merely by typing the remote machine’s public IP.
npx --yes @deepseek-ai/dsh@0.2.0-rc.2 --version
npx --yes @deepseek-ai/dsh@0.2.0-rc.2 webWhat to check: The launcher identifies 0.2.0-rc.2. The Web process prints its URL; a remote browser uses the forwarded address chosen by the SSH client.
3. Verify the selected workspace and first request
Choose the repository in the Web UI and confirm its location before sending a task. Save a model provider, start a fresh session and ask for the test command and defining file without making changes. Verify the file yourself.
A reachable HTML page checks the HTTP service. A useful answer from the selected model checks a different layer. Keep credential, model and protocol errors separate from Linux installation errors so each repair has an observable result.
Keep installation and runtime evidence separate
The launcher commands here pin npm latest 0.2.0-rc.2, checked on 2026-10-04. The reviewed upstream documentation is dsh-v0.2.1-alpha.1. The site’s retained local runtime record remains 0.1.0-rc.7 on Linux x64 with Node 22.22.1; it does not establish successful execution of the current package on this platform.
After any upgrade, record the new version and repeat the local-page and first-model-request checks. A Python SDK installation is a separate package path and does not install the Node Web launcher.
Frequently asked questions
Does the Linux runtime record prove the newest package works?
The retained test establishes an HTTP 200 response for 0.1.0-rc.7 in its recorded Linux environment. It does not establish the same result for a newer package, other distribution or model request.
Why does an SSH launch not open my local browser?
The reviewed launcher leaves the browser handoff to the SSH client or editor and prints the host URL. Set up loopback forwarding and use the client’s local address.
Should I run the launcher as root to fix a startup error?
First read the actual startup diagnostic and check the normal user’s runtime, project path and permissions. Changing the user also changes home, credentials and profile state, so it can hide the cause rather than demonstrate a repair.
First-party sources
Open the pinned or retrieved source before acting on a changed release candidate.
- Official DeepSeek Harness run guideOfficial documentation · retrieved 2026-10-04↗
- Official CLI behavior referenceOfficial documentation · retrieved 2026-10-04↗
- Official Web UI guideOfficial documentation · retrieved 2026-10-04↗
- Official model configuration guideOfficial documentation · retrieved 2026-10-04↗