Minimal dsh install: pick only the entry you use
A minimal install is not "the fewest packages"; it is "only the entry point you actually use". Answer where you work first, and half the troubleshooting disappears.
dsh install: one question first
If you ask yourself only one thing, ask: do I send messages in a browser, run commands in a terminal, or want a desktop window?
| Your answer | Smallest entry | Needs Node | Needs an installer |
|---|---|---|---|
| Browser chat | npx @deepseek-ai/dsh web | Yes | No |
| Terminal and scripts | Global npm | Yes | No |
| A window and tray | Desktop app | No, bundled | Yes |
All three share one data directory. Switching entries does not migrate data automatically, but nothing is lost because settings, sessions, and credentials live in DSH_HOME.
dsh install profile A: browser only
For messages and occasional review, npx is the complete setup.
- Confirm
node -vprints a version; - Run
npx @deepseek-ai/dsh web; - Open the address from the startup output, normally
127.0.0.1:3080; - Enter model credentials once in settings;
- Stop the process when you are done.
What this path does not install is explicit: no global command, no desktop app, no plugins yet. The first run initializes the web profile for you.
The cost is version drift. npx may resolve a different release each time; fine for trials, wrong once you depend on specific behavior.
dsh install profiles B and C: terminal and desktop
If you write scripts, configure aliases, or need a fixed version, a global install is the smaller solution.
- Confirm the npm global bin directory is on PATH;
- Run
npm install -g @deepseek-ai/dsh; - Verify with
dsh --version; - Record the version in your environment notes;
- Upgrade explicitly instead of reinstalling.
This path does not need the desktop app and does not need a per-project copy. One global command covers dsh web, headless runs, and SDK profiles.
Profiles initialize on first use. You do not create the headless or sdk profile in advance.
Adjacent to that need but different in goal is "I want a window", which is a separate distribution entirely.
Choose the desktop app only when you need windows, tray, and system integration. It is not a replacement for the CLI.
- Download the installer for your platform from Releases;
- Install, launch, and complete initialization;
- Configure the model inside the app;
- Update through the app, never by overwriting the install directory;
- Uninstall through the OS, then decide whether to keep data.
The desktop app does not register a dsh command. Finding no command in the terminal afterwards is expected. Terminal use still needs profile A or B.
Official desktop packages do not cover every platform. Where none exists, use the CLI plus a browser rather than a third-party build.
dsh install matrix and what to skip
Write "install" and "do not install" side by side to avoid over-installing.
| Profile | Install | Explicitly skip |
|---|---|---|
| Browser chat | Node plus npx | Global command, desktop app, plugins |
| Terminal automation | Node plus global npm | Desktop app, per-project copies |
| Desktop window | Platform installer | Global command, unless you also script |
| Desktop plus terminal | Installer plus global npm | A third, always-on npx copy |
The last row is the one case that needs two installs, each with a clear job. Every other combination makes which dsh hard to explain.
Read the matrix backwards and it becomes a list of things that are usually redundant. Beyond the matrix, extra installs buy troubleshooting cost, not capability.
- Installing a pile of plugins before verifying the base;
- Keeping an npx cache, a global package, and a desktop app on one machine with no idea which version runs;
- Repeating the install command "for safety", leaving duplicates in the global directory;
- Installing pnpm and build tooling copied from a guide when you only chat in a browser.
The test is simple: if removing it still lets your main entry run, it should not be there.
dsh install acceptance and upgrade timing
Three checks, not a full catalog.
- Your main entry starts without an error in the output;
- A message returns an answer, proving credentials and the model path;
- A restart still works, proving it was not a one-off.
Stop there. Add plugins when you need plugins, add a global command when you script. Incremental additions stay controllable.
The minimum is not permanent, so any of these signals means it is no longer enough: the version changes on every start, scripts need a fixed command, you need a window, or you need to reproduce the setup on several machines. Change the method rather than adding another: after moving to a global install, clear the npx cache so the next run cannot fall back to an old copy.
dsh install next steps
Decide the profile, then install. For all four methods side by side, read four ways to install DeepSeek Harness. For environment checks, read the install preflight. For post-install checks, read the acceptance test. For npx versus global, read npx versus a global install.
Sources: DeepSeek Harness docs, dsh CLI README, DeepSeek Harness Releases
FAQ
Node.js plus one command: npx @deepseek-ai/dsh web. No global install and no desktop app are needed. The first run initializes the web profile automatically and stores data under DSH_HOME.
A global dsh install is worth adding only if you need a stable command name, a pinned version, or reuse across scripts. npx may resolve a different version per run, so installing both is not faster; it just makes which dsh ambiguous.
The dsh desktop app and the CLI are separate distributions. The desktop app bundles its own runtime but does not register a command on PATH. Terminal use still requires npx or a global npm install.
Installing dsh plugins requires pnpm as an extra prerequisite. Plugin operations are forwarded to it inside the profile directory, so a target without pnpm cannot complete them; if you only send messages, you can skip that step entirely.
Related Terms
- usage profile
- A usage profile is a one-line description of where and how you work, such as browser chat or scripted terminal use, used to derive the smallest sufficient install.— DeepSeek Harness docs
- global install
- A global install is an installation that places the package in npm's global directory and registers the `dsh` command; it suits long-term use but requires you to manage upgrades.— dsh CLI README
- profile
- A profile is a named assembly environment with its own dependencies; web, headless, and sdk profiles initialize from bundled templates on first use.— dsh CLI README
- DSH_HOME
- DSH_HOME is the data root for DeepSeek Harness, defaulting to ~/.dsh, independent of how the program was installed.— DeepSeek Harness docs
Sources
- DeepSeek Harness docs· deepseek-harness
- dsh CLI README· deepseek-ai
- DeepSeek Harness Releases· deepseek-ai