Upgrade Guide

DeepSeek Harness is in developer preview and breaking changes may land at any time — the official docs say so explicitly. This guide is the safe path across preview releases (facts verified 2026-08-13).

There are no stable releases yet. Treat every upgrade as potentially breaking: back up your config, read the changelog, and keep a way back.

Know what you're on

Version history lives in the npm registry — GitHub Releases has no tags. Check your installed version:

zsh — dsh

$ dsh --version
$ npm ls -g @deepseek-ai/dsh # or npx @deepseek-ai/dsh --version

Current release line: 0.1.0-rc.6 (latest on npm as of 2026-08-13).

Release timeline so far

Version	Released	What changed	Upgrade risk
`0.0.1-rc.1`	2026-08-10	First public npm artifact; `npx @deepseek-ai/dsh web` became a working one-command install.	Preview
`0.1.0-rc.2`	2026-08-13	Version series moved to 0.1.0-rc; the ecosystem exploded (300+ repos with the `dsh-plugin` topic).	Series change
`0.1.0-rc.6`	2026-08-13	Public npm install without special access; this is the baseline new users should install.	Current

Safe upgrade procedure

1. Back up your config

Your profiles live under $DSH_HOME/profiles/ and machine preferences at $DSH_HOME/cordis.patch.yml. Copy the whole home directory (or at least your profile patches):

zsh — dsh

$ cp -r \"$DSH_HOME\" dsh-home-backup

2. Read the changelog for this version

Check the dsh.so Changelog — each entry has official changes plus dsh.so analysis on what it means for users and plugins.

3. Inspect your composed config before booting

After upgrading the package, verify the tree your machine will load — especially if you have custom patches or plugins:

zsh — dsh

$ dsh --profile web --dump-config
# watch stderr for unmatched patch targets
$

4. Upgrade the package

zsh — dsh

$ npm install -g @deepseek-ai/dsh@latest
$ dsh --version # confirm the new version

If you run from a source checkout instead: git pull, pnpm install, pnpm run build, then pnpm dsh web.

5. Verify plugins survived

After boot, confirm your plugins loaded (watch startup logs for errors), and check their compatibility records on dsh.so — the registry shows declared vs verified status per plugin, and the version compatibility matrix tracks which versions dsh.so has records for. Remember: no plugin is independently verified yet — declared compatibility is the author's claim.

If something breaks

Roll back the package — pin the previous version: npm install -g @deepseek-ai/dsh@0.1.0-rc.2.
Restore config — copy dsh-home-backup/ back over $DSH_HOME.
Isolate the change — run with --dump-config to see which rows changed; a patch that replaces whole config values is the usual culprit.
Ask — official Discussions, or see the Troubleshooting guide.

The bottom line

For new installs: use 0.1.0-rc.6. For existing setups: upgrade one release line at a time, keep the old package version one command away, and never skip reading the changelog — preview breaks are the rule, not the exception.

Join the community

GitHub Discussions Discord Submit a plugin

Questions or feedback? Official Discussions is the project’s canonical support channel; Discord has an active community. dsh.so itself improves via plugin submissions and your feedback.