Install · Independent guide

DeepSeek Harness Node.js Requirements & Compatibility

The repository root declares Node ^22.19.0 or >=24.0.0 for development, while the published @deepseek-ai/dsh rc.7 manifest does not declare an engines field. We independently verified rc.7 on Linux x64 with Node 22.22.1 and npm 10.9.4, including the version command and a loopback Web UI HTTP 200 response. That tested point is evidence, not a universal minimum or a promise for every operating system.

Reviewed Aug 19, 2026Developer previewIndependent guide
Evidence status: Repo engines + published package metadata + rc.7 Linux x64 runtime verification. Re-check the linked first-party source after a new release candidate.
Track setup progress →

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.

Public command · no secrets
node --version
npx @deepseek-ai/dsh@0.2.0-rc.2 --version

What is verified now

The repository root declares Node ^22.19.0 or >=24.0.0 for development, while the published @deepseek-ai/dsh rc.7 manifest does not declare an engines field. We independently verified rc.7 on Linux x64 with Node 22.22.1 and npm 10.9.4: the version command returned 0.1.0-rc.7 and the Web profile returned HTTP 200 on an isolated loopback port.

Treat the repository range as a development requirement, the npm manifest as package metadata, and Node 22.22.1 as one tested runtime point. None of those facts alone certifies every Node version or operating system. The sources and runtime artifact were checked on 19 August 2026.

Safe workflow

Use the smallest reversible workflow first. Do not add community plugins or paste credentials while validating the base behavior.

  1. Check runtime and OS prerequisites.
  2. Run only the official command shown in the versioned code block.
  3. Verify the version and local URL before configuring a provider.

Verify before moving on

A successful result should be observable: a version string, reachable local URL, valid provider response, loaded configuration, or disappearance of the exact error. If the result differs, stop and capture sanitized evidence rather than stacking unrelated fixes.

  1. Record the exact dsh, Node or Python version.
  2. State the operating system and installation method.
  3. Link the first-party source and include only sanitized logs.

First-party sources

Open the pinned or retrieved source before acting on a changed release candidate.

Continue by layer

DeepSeek Harness Install: Node and Web UI
Open guide →DeepSeek Harness Troubleshooting Guide
Open guide →