how to upgrade dsh

[wxl5000]

if i want to upgrade dsh, should i pull latest code? should i refresh local env? just like :"pnpm install", "pnpm build"?

[Takagi-Masao]

I just delete old files and clone new ones, then build everything again according to the readme.

[MIHassan3]

you can use this new released tool. DSH-Launcher
it will prevent the use of line commands at all and will help to control the installed version even you can pick the alpha versions.

it's just a tool to launch the official harness from DeepSeek not a new harness.

it's currently only working on windows

[ChangedenCZD]

npm i -g @deepseek-ai/dsh@latest

[wxl5000]

Has DSH been published to the npm registry?

[MIHassan3]

this one only installs the rc releases. if you want to try some alpha and also there's an option to go back without losing the data and workspaces you can give this tool a try

DSH-Launcher

also if you think performance needs enhance you can share it or you can do it yourself

[ChangedenCZD]

Has DSH been published to the npm registry?

https://www.npmjs.com/package/@deepseek-ai/dsh

[zhousm666]

You can try dshvm, a multi-version manager that supports multiple versions coexisting side by side. When upgrading, it uses an independent session directory for the new version, so your existing sessions remain untouched. If any issues arise, your original session data and the normal operation of your dsh system will not be affected.

Upgrade scenario:

1 · Safely try the latest version without affecting your current environment (isolated copy upgrade)

npm install -g @dsh-so/dshvm
dshvm setup # adopts your existing global dsh and installs the shims

dshvm isolate 0.1.3-alpha.1 --copy # copies your current ~/.dsh, then makes it independent
dshvm use 0.1.3-alpha.1 # activates this independent copy

dshvm --version # you'll see it's now switched to the new version
dsh web # starts the new version

• Recovery steps if issues occur:
  dshvm use 0.1.2-rc.1 # switch back to the original version
  dshvm --version # you'll see it's now back to the old version
  dsh web # starts the original version
  Your sessions, plugins, and settings work exactly as before — the new version tinkers with its own data, so an upgrade will never pollute the environment you're actively using.

[zhousm666]

You can try dshvm, a multi-version manager that supports multiple versions coexisting side by side. When upgrading, it uses an independent session directory for the new version, so your existing sessions remain untouched. If any issues arise, your original session data and the normal operation of your dsh system will not be affected.

Upgrade scenario:

1 · Safely try the latest version without affecting your current environment (isolated copy upgrade)

npm install -g @dsh-so/dshvm
dshvm setup        # adopts your existing global dsh and installs the shims

dshvm isolate 0.1.3-alpha.1 --copy   # copies your current ~/.dsh, then makes it independent
dshvm use 0.1.3-alpha.1              # activates this independent copy

dshvm --version                      # you'll see it's now switched to the new version
dsh web                              # starts the new version

- Recovery steps if issues occur:
dshvm use 0.1.2-rc.1                 # switch back to the original version
dshvm --version                      # you'll see it's now back to the old version
dsh web                              # starts the original version

Your sessions, plugins, and settings work exactly as before — the new version tinkers with its own data, so an upgrade will never pollute the environment you're actively using.

===============================================================

dshvm 0.1.0 — An nvm-style multi-version manager for the DeepSeek Harness CLI (dsh)

What It Does

dshvm is an unofficial, zero-runtime-dependency multi-version manager for the DeepSeek Harness CLI (dsh) — the community name for @deepseek-ai/dsh. Think of it as "nvm for dsh": install versions from anywhere, switch the global dsh with a single command, and give each version its own completely isolated data home whenever you need it.

• One-command switch — dshvm use <version> re-points the global dsh; no re-download, works offline, supports prefix matching.
• Source-built pre-releases — versions not on npm (e.g., 0.1.3-alpha.1) are built automatically from the DSH GitHub repo, so dshvm install 0.1.3-alpha.1 just works.
• Per-version data isolation — dshvm isolate <version> [--copy] gives a version its own $DSH_HOME (sessions, plugins, settings, credentials); --copy seeds it from your current setup, dshvm unisolate drops back to the shared home.
• Multiple install sources — npm registry, GitHub (auto / release asset / forced source), or a local checkout/tarball; you can even register an existing dsh as-is with dshvm register.
• Cross-platform, fully local, no background service — thin shims (dsh.cmd / dsh.ps1 / dsh) for Windows/macOS/Linux; state lives in plain files under ~/.dsh-versions, zero runtime dependencies, just Node >= 18. Nothing is downloaded twice, and nothing runs unless you invoke dsh.

Install

npm install -g @dsh-so/dshvm
dshvm setup        # adopts your existing global dsh + installs the shims

First five commands:

dshvm install 0.1.2-rc.1      # from npm
dshvm install 0.1.3-alpha.1   # not on npm → auto GitHub source build
dshvm use 0.1.3-alpha.1       # switch (prefix match works)
dshvm list                    # * = active
dsh --version                 # runs the active version

Common Scenarios

1 · Safely try the new release without touching your setup (isolated copy upgrade)

dshvm isolate 0.1.3-alpha.1 --copy   # copies your current ~/.dsh, then goes independent
dshvm use 0.1.3-alpha.1              # activate the isolated copy

Your sessions, plugins and settings keep working exactly as before — the new version experiments on its own data, so an upgrade can never pollute what you are using.

Recovery steps if something goes wrong:

dshvm use 0.1.2-rc.1                    # switch back to the original version
dshvm --version                         # confirms you're back on the old version
dsh web                                 # start the original version

2 · Everyday multi-version management

dshvm install 0.1.2-rc.1     # install normally
dshvm use 0.1.2-rc.1         # switch; shares the default ~/.dsh like every other version

3 · Fully isolated test environment

dshvm isolate 0.1.3-alpha.1  # brand-new, empty $DSH_HOME — nothing copied, nothing affected
dshvm use 0.1.3-alpha.1

Test plugins / profiles / sessions in a clean room; nothing leaks back to the shared home.

4 · Roll back, un-isolate or clean up

dshvm use 0.1.2-rc.1            # back to the shared home and an older version
dshvm unisolate 0.1.3-alpha.1   # drop that version's isolated copy
dshvm remove 0.1.2-rc.1         # delete a slot (incl. its isolated data) when you're done

Good to know — use never disturbs running sessions (new dsh calls pick up the active version). Isolation survives new terminals and reboots (stored on disk; injected into the dsh process by the shim, not a shell variable — echo $DSH_HOME staying empty is normal). Plugins always live in $DSH_HOME (~/.dsh), never inside a version slot.

Extras

• 14 management commands — setup / use / list / install / register / unregister / remove / isolate / unisolate / exec / repair / doctor / current / which.
• Tested on 3 OSes × 3 Node lines — offline npm test suite (temp homes, sandbox-friendly) plus a real-install integration run; CI on Ubuntu/macOS/Windows × Node 18/20/22.
• Drop-in history compatibility — registry compatible with the legacy PowerShell dshvm; when dsh web finds port 3080 busy, the shim auto-adapts to the next free port.
• Windows-friendly source installs — GitHub source trees skip symlinks tar cannot create and get a one-commit git snapshot, so builds that read HEAD work from a tarball.
• Bilingual README — English + Simplified Chinese with a language switcher.

P.S. dshvm is an independent community project — not affiliated with DeepSeek. It is MIT-licensed, published to npm, and just reached its first official release (0.1.0) after moving under the dsh-so org. Issues, feature requests and PRs are very welcome — the "upgrade anxiety" it removes is real, and so is the need for feedback.

Author: zhoushimin (dshvm contributors) · License: MIT · Repo: https://github.com/dsh-so/dshvm · npm: @dsh-so/dshvm

---

Disclosure. For transparency: I maintain the dsh.so site — the DeepSeek Harness plugin registry & discovery hub for community dsh plugins — and I authored dsh-plugin-advisor — a dsh plugin that searches that registry and compares candidates by verification level (L1–L5) and security scan before you install.