Command generator
Choose your install path
node --version
npm --version
npx @deepseek-ai/dsh webExpected default address: http://127.0.0.1:3080
Check the environment before the package
Run Node and npm checks in the exact shell that will launch DSH. The current npm package does not publish a Node engines floor, so this page does not invent one. Keep the repository and DSH process in the same native, WSL, container, or remote environment.
Verify five boundaries
- Runtime: Node and npm resolve in the intended environment.
- Process: DSH stays running and prints a URL.
- Browser: the printed address opens; the documented default is 127.0.0.1:3080.
- Configuration: a model credential can be saved and a workspace selected.
- Task: a small read-only repository summary completes before broader permissions.
Windows baseline: the environment and results we actually measured
This matrix answers a narrower, more useful question than “does it install?”: whether the pinned base Web UI starts, how the same isolated profile behaves across rc.6 and rc.7, and what memory was observed after HTTP readiness.
Retained lab record
Native Windows base startup and lifecycle
- Operating system
- Windows 11 Home China · 10.0.26200 · x64
- Runtime
- Node v24.11.1 · npm 11.5.2 · PowerShell 7.6.4
- Hardware
- Intel i7-12700H · 15.7 GiB RAM
- Isolation
- Dedicated DSH_HOME, workspace, profile, and localhost ports
What the upgrade, rollback, and removal test proves
Running rc.7 against the same base profile previously opened by rc.6 loaded the real UI with zero console errors. Pinning rc.6 again did the same. This verifies base-profile version switching, not every plugin’s data migration.
npx --yes @deepseek-ai/dsh@0.1.0-rc.7 web
# rollback test: pin the previous version
npx --yes @deepseek-ai/dsh@0.1.0-rc.6 web- Upgrade: rc.6 → rc.7 base profile loaded normally.
- Rollback: rc.7 → rc.6 base profile loaded normally.
- Reversible removal: moving the exact isolated DSH_HOME made the active profile absent and closed the test ports.
- Cache boundary: the shared npx/npm cache was intentionally retained; removing a profile and clearing downloaded packages are different decisions.
Use a safe first task
The official Web UI guide recommends a repository summary task after model and workspace selection. It exercises file reading without asking the agent to modify the repository.
Summarize this repository and identify its main packages.See a community setup flow—with its evidence limit visible
The video adds visual context for the shell, Web UI, and model-provider screens. It is embedded because it informed this page, but it does not replace the official command or the direct Windows baseline above.
YouTube · community observed
A visual NPX and local-provider walkthrough
Community demonstration of the Node check, NPX start, local Web UI, and a later Ollama provider flow.
Boundary: The exact command comes from official documentation, and HarnessBase verified base startup separately. The Ollama provider flow remains community evidence, not a tested compatibility claim.
Open the cited segment on YouTube ↗Do not reinstall before locating the failure
| Visible symptom | First boundary to inspect |
|---|---|
| Package command fails immediately | Node/npm resolution, registry access, package name, and current CLI output. |
| Process exits | First error line, port conflict, configuration parse, and recent update. |
| Browser cannot connect | Printed host/port and native/WSL/container boundary. |
| Composer is blocked | Model selection and workspace selection. |
| Model request fails | Credential, provider, exact model ID, and endpoint response. |
Provenance ledger
Evidence sources used on this page
- Official Official DeepSeek Harness repository ↗
Canonical identity, quick start, Developer Preview status, source workflow, and plugin architecture.
- Repository npm package @deepseek-ai/dsh ↗
Published version metadata. Registry state does not by itself prove a successful run.
- Official Official Web UI guide ↗
Model, workspace, and first-task flow.
- Direct test HarnessBase Windows lifecycle test
Retained commands, environment, HTTP readiness, process-tree memory, browser checks, version switching, profile removal, and reinstall results.
- Community Ray Codes NPX and Ollama walkthrough ↗
Visual setup context. The exact command and compatibility conclusions are sourced separately from official documentation and direct tests.