Errors · Independent guide

Fix node-pty “pty.node” Missing in DeepSeek Harness

We reproduced a missing prebuilds/linux-x64/pty.node error only after deliberately installing with --ignore-scripts. A normal npm install of the same rc.6 package worked; reinstall normally before treating the error as a DeepSeek Harness product defect. This page separates verified behavior from community reports and marks the release-candidate context so you can act without mistaking an observation for a permanent guarantee.

Unverified report · noindexDeveloper previewIndependent guide
Unverified report: Repro: ignore-scripts install; normal install verified. This page remains accessible for review but is excluded from search indexing until its claim and recovery path have exact support.

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
npm install @deepseek-ai/dsh@0.1.0-rc.6
npx @deepseek-ai/dsh@0.1.0-rc.6 --version

What is verified now

We reproduced a missing prebuilds/linux-x64/pty.node error only after deliberately installing with --ignore-scripts. A normal npm install of the same rc.6 package worked; reinstall normally before treating the error as a DeepSeek Harness product defect.

Evidence basis: Repro: ignore-scripts install; normal install verified. The status was checked on 14 August 2026; re-check the linked source after any dsh release.

Safe workflow

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

  1. Copy the exact error and record OS, Node and dsh versions.
  2. Apply the narrow checks on this page in order.
  3. Verify with a minimal profile and escalate with sanitized logs if it persists.

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