How to install DeepSeek Harness: 4 methods compared

DeepSeek Harness has four install paths: npx, global npm, desktop, and source. All run, but prerequisites, maintenance, and audience differ; choosing wrong makes updates and uninstalls awkward.

Four paths compared

Start with the table, then read each path.

You do not need all four, and data location is decoupled from install method. Pick one primary path; multiple installs cause version and data confusion. Sessions, plugins, and configuration live under DSH_HOME, so switching paths does not migrate data, but it does not lose it either.

npx: try it out

npx is the lowest-barrier entry.

1. Confirm Node.js: node -v.
2. Run npx @deepseek-ai/dsh web.
3. Open the local address printed in the terminal.
4. Complete model and profile initialization on first entry.
5. Close when done; no global command remains.

npx fetches the latest each time and still writes data. It avoids update management but starts slower and changes versions; switch to global npm when you need stability. Sessions and configuration still land under DSH_HOME, so "temporary run leaves no trace" is false.

Global npm: long-term use

For daily terminal use, a global install is simplest.

1. Confirm the npm global directory and PATH.
2. Run npm install -g @deepseek-ai/dsh.
3. Confirm the command with dsh --version.
4. Start with dsh web and open the browser.
5. Update with npm; do not reinstall.

PATH is the most common issue, and version management matters. If the command is missing, check whether the global bin is on PATH; npx running while dsh does not means a path problem. Record the version before upgrading so you can roll back.

Desktop: graphical interface

Desktop suits windows, tray, and system integration.

1. Open Releases and choose the installer for your platform.
2. Install, start, and complete initialization.
3. Configure model and plugin market in settings.
4. Update through in-app prompts; do not overwrite the install directory.
5. Uninstall through the system, then clean data.

Sharing data between desktop and CLI needs care, and Linux has no official desktop build. Two versions writing one DSH_HOME risk locks and version conflicts; do not run both at once. On Linux, use CLI plus browser instead of third-party packages.

Source: development and customization

Use source when changing code, inspecting implementation, or submitting patches.

1. Clone the repository and check out the target branch.
2. Install dependencies and build per the repository instructions.
3. Start the build output and confirm the commit matches.
4. Rebuild after changes and clear cache when needed.
5. Update with git pull and rebuild.

The cost is the build, and source and global installs should not mix commands. Dependencies, Node versions, and build scripts can fail; if you only need features, avoid this path. Two dsh binaries may point to different locations; use which dsh to confirm.

Choosing by scenario

Choose by duration, customization, and GUI needs.

Pick one primary path, then supplement as needed; do not install all four to "try them." Mixing versions and data costs more than the choice saves.

Verification after install

All paths share three verification signals.

1. Command: dsh --version prints a version.
2. Service: dsh web starts and prints an access address.
3. Function: the browser opens the UI and completes a minimal conversation.

Record the install method and version. All three must pass; passing only the command may hide a service failure, and passing only the service may hide an unconfigured model.

Updates and uninstalls

Each path maintains itself differently.

1. npx: no update needed; clear cache if necessary.
2. Global npm: update and uninstall with npm; watch PATH residue.
3. Desktop: in-app update, system uninstall, then clean data.
4. Source: git pull and rebuild; clear artifacts when switching branches.

Uninstalling is not deleting data, so snapshot before updates. Sessions, plugins, and configuration live under DSH_HOME and need separate cleanup. Keep a version list and a data copy for rollback.

Next steps

Choose a path, then verify three layers. For detailed comparison, read DeepSeek Harness install methods compared. For downloads, read Where to download DeepSeek Harness. For Linux, read Running DeepSeek Harness desktop on Linux.

Sources: DeepSeek Harness docs, dsh CLI README, DeepSeek Harness Releases