Fix DeepSeek Harness install errors: pnpm missing, node not in PATH

DeepSeek Harness install errors like 'pnpm' is not recognized and node: command not found mean the environment is not ready: both Node.js and pnpm are required, and both install directories must be on PATH. The order is fixed — node first, pnpm second — because pnpm is installed through npm and npm depends on node. Fix it in three steps: install Node, enable Corepack, verify with node -v && pnpm -v.

DeepSeek Harness install errors: what they look like and which comes first

node: command not found always shows up before 'pnpm' is not recognized — pnpm is installed through npm, and npm depends on node, so the whole chain breaks when node is unavailable. The exact messages (source):

1. node: command not found — running any node command (node --version) prints this, meaning node is not installed or not on PATH;
2. 'pnpm' is not recognized as an internal or external command (Windows) / pnpm: command not found (macOS/Linux) — pnpm --version fails, meaning pnpm is not installed or not on PATH;
3. How to tell: run node --version, then npm --version, then pnpm --version — start fixing from whichever step errors out. Node is the foundation; always fix node first.

Why DeepSeek Harness installs fail: Node and pnpm missing or off PATH

There are two root causes: Node and pnpm are either missing or not on PATH, and the fix order is often reversed — install node first, then pnpm; both are indispensable. In detail:

1. The dsh launcher needs node on PATH: dsh is a Node.js program and cannot start without it; the dshbase troubleshooting page calls this out explicitly (source).
2. dsh plugin needs pnpm: the plugin install command calls pnpm, and the install aborts when pnpm is missing (source).
3. Install order: pnpm is installed through npm (npm install -g pnpm) or Corepack, and npm ships with node — so the order is node → npm → pnpm.
4. PATH write-through: if a tool is installed but the command is not found, its install directory is almost always missing from PATH; the node installer ticks "Add to PATH" by default, while the npm global directory is often forgotten.

Fix DeepSeek Harness environment errors: install Node, enable Corepack, verify

Follow the fixed order: install Node and confirm it is on PATH, then enable Corepack or install pnpm globally, then verify both with a single node -v && pnpm -v. Step by step:

1. Install Node (LTS): download the LTS installer from nodejs.org and tick "Add to PATH" in the wizard (the macOS pkg installer configures PATH automatically). Open a new terminal and run:

   bash

   node --version
   

   Expected output: v20.x or newer. If it still says command not found, skip to step 4 to add PATH manually.

2. Confirm npm works: npm ships with node:

   bash

   npm --version
   

   Expected output: an npm version number (e.g. 10.x.x). If it errors, PATH is misconfigured — go to step 4.

3. Enable Corepack to get pnpm (recommended) — Corepack is bundled with Node, one command turns it on:

   bash

   corepack enable
   

   With no error output, verify directly:

   bash

   pnpm --version
   

   Expected output: a pnpm version number (e.g. 9.x.x). Prefer the classic route instead? Then:

   bash

   npm install -g pnpm
   

4. Add PATH manually (when node/pnpm are installed but commands are not found) — first locate the npm global directory:

   bash

   npm prefix -g
   

   • Windows: add the output directory (e.g. C:\Users\You\AppData\Roaming\npm) to "System environment variables → Path", save, and open a new terminal;
   • macOS / Linux: run echo 'export PATH="$(npm prefix -g)/bin:$PATH"' >> ~/.zshrc (zsh) or append to ~/.bashrc, then run source ~/.zshrc or open a new terminal.

5. Final verification — run both at once; both should print version numbers:

   bash

   node -v && pnpm -v
   

   Two version lines means the environment is ready; then run dsh --version — a version number means DeepSeek Harness is usable.

How to verify a DeepSeek Harness environment: version trio and a full startup test

A single node -v && pnpm -v && dsh --version tells you whether the environment is ready — three version lines mean node, pnpm and dsh all work, and a dsh web startup test closes the loop. In order:

1. Version trio:

   bash

   node -v && pnpm -v && dsh --version
   

   Three version lines mean node / pnpm / dsh are all usable; whichever line reports command not found, fix that link in the corresponding step above.

2. Confirm the commands come from the right place (in case you have two installs and PATH resolves to an old one): macOS / Linux:

   bash

   which node && which pnpm && which dsh
   

   Windows:

   powershell

   where node & where pnpm & where dsh
   

   The printed paths should point to the directories you just installed into; if they point at an old version, reorder PATH.

3. Start the Web UI for a full-chain test:

   bash

   dsh web
   

   When the terminal prints dsh web: http://127.0.0.1:3080, a browser page that loads means the whole chain from node to dsh works.

4. Verify the pnpm channel with a real plugin install (optional): only when dsh can call pnpm to install plugins is the environment truly closed-loop:

   bash

   dsh plugin --profile web add <package>
   

   A clean install and dsh plugin --profile web list showing the package means pnpm is being invoked correctly.

5. Pin the pnpm version with Corepack (optional): when a project requires a specific pnpm version:

   bash

   corepack prepare pnpm@<version> --activate
   

   pnpm --version now prints the pinned version.

Notes: DeepSeek Harness — fix node before pnpm

1. The error order dictates the fix order: fix node: command not found first, 'pnpm' is not recognized second — do not skip steps.
2. Opening a new terminal is required for PATH changes to take effect.
3. On Windows, close the environment variables window with OK and use a freshly opened terminal.
4. Once the environment is ready, the easiest way to add plugins is Settings → Plugin Market — the DSH Plugin Hub store browses and installs plugins graphically, without touching the command environment.
5. See install error troubleshooting for other DeepSeek Harness install issues.

Sources: dshbase troubleshooting, Node.js official site, pnpm official docs