ChatGPTClaudeGrok / X / CursorGemini

Three dsh install myths: desktop, npx, and global

Install & Get StartedPublished 2026-11-02Author: DeepSeek Plugin Market
dsh installmisconceptionsnpxglobal installversions
No command after installing, or still an old version? Three concepts are being mixed together. Each myth gets the reality and one command that settles it.

"Installed but no command" and "installed but still old" are the same mistake wearing two masks: desktop, npx, and global installs are three different things. Take them apart, and each gets one verification command.

dsh install myth one: desktop means CLI

What you see: the installer finished and the app opens, so the terminal should work too.

What happens: desktop and command line are separate distributions. The desktop app bundles a runtime and a window; it does not write dsh into PATH. "Command not found" is correct behavior, not a failed install.

Verification:

  1. Run which dsh; no output means there is no CLI entry;
  2. Launch the desktop app and confirm it starts;
  3. Both results are consistent — you are missing a CLI, not a working app.

What to add: install a CLI separately through npx or global npm. The desktop app solves "I want a window"; the CLI solves "I want to script it".

dsh install myth two: npx means installed

What you see: npx @deepseek-ai/dsh web worked and the page opened, so the machine is set up.

What happens: npx resolves and executes, then stops. Nothing is registered globally. It may hit the cache or fetch again, and the version can differ between runs. You proved "this run worked", not "this machine has an install".

Verification:

  1. Open another terminal and run dsh --version; a missing command proves there is no global entry;
  2. Run npx @deepseek-ai/dsh --version; output proves the npx path works;
  3. One failing and one succeeding is the classic npx-only state.

What to add: for a stable command, scripted use, or a pinned version, switch to a global install and record the version. For occasional use, npx is enough.

dsh install myth three: global means latest

What you see: a guide said to install latest, you did, and later behavior no longer matches the documentation.

What happens: latest decides what a new install resolves. It does not update files already on disk, and nothing checks the registry at startup. Your version is whatever the last install or upgrade left behind.

Verification:

  1. dsh --version for what actually runs;
  2. npm view @deepseek-ai/dsh version for what the registry currently tags;
  3. Different numbers mean you are behind and need an explicit upgrade.

What to add: upgrade is an action, not a side effect. Record the previous version so you can return to it.

dsh install myths and three state commands

"What you assume" next to "what happens" is the fastest way to remember it.

You assumeRealityOne command
Desktop gives me a commandTwo distributions, no shared PATHwhich dsh
npx means installedEphemeral, registers nothingdsh --version in a new shell
latest means newest hereOnly affects new installsCompare the two versions

All three share one missing step: an independent check after installing, and three commands provide it. Without that check, the misunderstanding survives indefinitely.

Do not guess; run these three in order:

  1. which -a dsh lists every executable that matches; more than one means duplicates;
  2. dsh --version shows which one actually runs and at what version;
  3. npm ls -g --depth=0 @deepseek-ai/dsh shows what the global directory holds.

Reading the results:

ResultConclusion
which prints nothingNo CLI entry; only npx or desktop exists
Multiple paths, different versionsDuplicates; clean PATH or uninstall one
Global exists, version behindAn explicit upgrade is needed
Nothing at allNo CLI install has happened

Look before acting. Most "reinstall loops" are PATH pointing at a second copy.

dsh install: two traps and when to reinstall

Two details also trip people, and both affect "where things are" rather than "whether it installed".

  1. Package name: the canonical name is @deepseek-ai/dsh, so the command is npx @deepseek-ai/dsh web. The often-quoted npx deepseek-ai/dsh web mirrors a GitHub path; when resolution fails, use the scoped name.
  2. Data location: sessions and settings are not in the install directory. They live in DSH_HOME, default ~/.dsh. Reinstalling or changing methods does not migrate them, and uninstalling a package does not erase them.

Rule these out before concluding anything about the install. They explain "everything is installed but nothing is where I expect", and only then is a reinstall even a candidate.

Reinstalling fixes damaged files, not confused concepts. Only when:

  1. which -a dsh points at a path that exists but fails to execute;
  2. The global package directory is visibly incomplete;
  3. An upgrade was interrupted, leaving a version number inconsistent with behavior.

If the three commands show "not installed", "installed elsewhere", or "behind", the fix is choosing a path and cleaning PATH, not reinstalling.

dsh install next steps

Separate the concepts, then pick one install. For all methods, read four ways to install DeepSeek Harness. For the smallest setup, read minimal dsh install. For npx versus global, read npx versus a global install. For upgrades that do not take effect, read dsh updates not applying.

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

ChatGPTClaudeGrok / X / CursorGemini

FAQ

I installed the DeepSeek Harness desktop app but the terminal has no dsh command. Did the install fail?

No: the dsh desktop app and the command line are separate distributions. The desktop app bundles a runtime but does not register a command on PATH, so the terminal cannot see it. Add a CLI install if you need terminal access.

Does running something through npx mean dsh is installed?

No: running dsh through npx resolves and executes it, then exits without registering a global command. It proves the command works right now, not that the machine has an install you can call later.

npm said it installed latest. Why is `dsh --version` still old?

The npm latest tag describes what a new dsh install resolves, not what exists on your machine. An older global install keeps running until you explicitly install again, because nothing checks for updates at startup.

How do I list every dsh on the machine at once?

Run which -a dsh for all matching executables, dsh --version for the one that runs, and npm ls -g --depth=0 @deepseek-ai/dsh for the global copy. Comparing the three exposes duplicates.

Related Terms

desktop app
The desktop app is a graphical build shipped as an installer; it bundles a runtime but does not add a command to the system PATH.— DeepSeek Harness Releases
npx
npx is the ephemeral runner shipped with npm: it resolves a package and executes it without registering a global command.— npm docs
PATH
PATH is the list of directories a shell searches for executables; a command outside those directories behaves as if it does not exist.— dsh CLI README
latest tag
The latest tag is the default dist-tag in an npm registry; it affects what a new install resolves, not what is already installed.— npm docs

Sources