Install · Independent guide

DeepSeek Harness macOS Install: Node and Web UI

For the npm Web UI on macOS, check Node and npm in your terminal, run the pinned official launcher from your project directory, and open its printed loopback URL. Configure a model and verify a small task separately. Python SDK platform requirements belong to that separate installation path.

Reviewed Oct 4, 2026Developer previewIndependent guide
Evidence status: Official dsh-v0.2.1-alpha.1 documentation review; historical runtime verification remains 0.1.0-rc.7 on Linux x64. 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
npx @deepseek-ai/dsh@0.2.0-rc.2 web

1. Check the terminal runtime and project location

Open Terminal or your development terminal in the project directory. Run the checks below there. If you use a Node version manager, confirm the active version in this shell instead of assuming an editor terminal uses the same one.

Record whether the machine is Apple silicon or Intel when reporting native dependency failures. Do not infer support for the npm launcher from a Python SDK platform table: they are separate packages with separate dependency and runtime requirements.

Check command
node --version
npm --version

What to check: Both commands resolve in the shell you will use for the pinned launcher.

2. Start the local Web UI

Run the version check and the Web command below. Use the printed local URL and keep the terminal running. If macOS does not hand the address to your preferred browser, open the printed URL yourself; server startup and browser opening are separate observations.

If the server says the port is occupied, use web --port 3081 for a separate local check. Do not change API credentials to fix a listening-port error. For an SSH launch, use the address forwarded by your SSH client or editor.

Check command
npx --yes @deepseek-ai/dsh@0.2.0-rc.2 --version
npx --yes @deepseek-ai/dsh@0.2.0-rc.2 web

What to check: The launcher reports 0.2.0-rc.2, then the Web command prints its local service URL. A successful model request still needs a separate check.

3. Select the workspace and verify a model

Choose the directory you intend to inspect, save a provider in Settings → Models, and select its model in a new session. Ask for the repository’s test command and defining file without requesting changes. Check that answer against the file.

If the UI loads but that request fails, keep the exact adapter or provider error. Check the credential source or model ID named by the failure. A working Node version and a reachable local page do not establish model access.

Keep installation and runtime evidence separate

The launcher commands here pin npm latest 0.2.0-rc.2, checked on 2026-10-04. The reviewed upstream documentation is dsh-v0.2.1-alpha.1. The site’s retained local runtime record remains 0.1.0-rc.7 on Linux x64 with Node 22.22.1; it does not establish successful execution of the current package on this platform.

After any upgrade, record the new version and repeat the local-page and first-model-request checks. A Python SDK installation is a separate package path and does not install the Node Web launcher.

Frequently asked questions

Are Python SDK requirements also Web UI requirements?

No. Use the npm launcher documentation for the Node Web path and the SDK documentation for Python. A platform restriction in one package does not establish the same restriction in the other.

Do I need to change the host address for a local Mac?

Start with the documented loopback address and the URL printed by your invocation. Host or trust settings should follow the exact deployment guide for a deliberate remote setup.

What should I capture for a native dependency failure?

Record the exact dsh and Node versions, macOS version, machine architecture, installation method and first sanitized error. These details distinguish architecture and runtime problems from provider configuration failures.

First-party sources

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

Continue by layer