1. Check the prerequisite

Use Node.js 22.13 or newer. DSHub’s August 20 test used Node.js 24.19 on macOS arm64 with a clean, isolated DSH_HOME.

node --version
npm --version

2. Choose rolling or pinned

The official README currently recommends the unpinned command below. It follows the npm latest tag, so it is the best default for a new user who wants the project’s current supported path.

For a reproducible investigation, pin the tested release candidate first. DSHub verified the rc.7 package’s CLI version and Web Profile through pnpm dlx because the same package’s npm dependency resolution did not finish within the local test window. That packaging observation is not a claim that the official npx command fails for every user.

# Official rolling command
npx @deepseek-ai/dsh web

# Reproducible version check used by DSHub
pnpm dlx @deepseek-ai/dsh@0.1.0-rc.7 --version

# Pinned Web Profile used by DSHub
pnpm dlx @deepseek-ai/dsh@0.1.0-rc.7 web

3. Verify the first run

  • The CLI reports 0.1.0-rc.7 when you use the pinned command.
  • The terminal prints a local Web Profile address; rc.7 defaults to port 3080.
  • The browser loads the internal-testing notice and then the workspace screen.
  • Use the current CLI help for flags. The tested rc.7 Web command exposes host, port, and trusted-host options; do not rely on an older undocumented flag.
pnpm dlx @deepseek-ai/dsh@0.1.0-rc.7 web --help

4. Establish a known-good baseline

  • Open a non-sensitive test workspace.
  • Configure one model provider without adding community Bundles.
  • Run one read-only prompt and keep its result.
  • Record Harness, Node.js, model, and Profile versions.
  • Stop the process normally with Control-C before changing versions.

5. Decide whether to update

At verification time, GitHub listed 0.1.0-rc.8 while npm latest still resolved to rc.7 and npm next resolved to rc.8. That difference is exactly why DSHub does not silently replace the tested baseline with the newest upstream tag.

Update only after reading the release notes, confirming the npm tag you intend to use, and preserving the working Profile. If startup changes, return to the pinned command and compare one variable at a time.

Configure a model safely →