ChatGPTClaudeGrok / X / CursorGemini

Rolling back a dsh install: version, method, data

Install & Get StartedPublished 2026-11-02Author: DeepSeek Plugin Market
dsh installrollbackdowngradeversion pinningdata recovery
Rollback is not reinstall. Decide whether you are reverting the version, the install method, or the data; do the cheapest first, and touch DSH_HOME only last.

Before rolling back, answer one question: are you reverting the version, the install method, or the data? The three have different blast radii, and the wrong order turns a recoverable problem into an unrecoverable one.

Identify the dsh rollback target

Similar symptoms, different fixes.

SymptomRevertScope
Behavior changed, plugins incompatibleVersionExecutable only
New install method is awkward or conflictsInstall methodCommand and PATH
Sessions lost, settings corruptedDataDSH_HOME
Nothing starts at allVersion first, then dataNarrow step by step

Start with the smallest blast radius. A version rollback fixes most cases and does not touch data.

dsh rollback targets one and two: version and install method

A version rollback is the safest because it changes neither data nor entry point.

  1. Record the current version: dsh --version;
  2. Confirm the target exists: npm view @deepseek-ai/dsh versions;
  3. Install the older version: npm install -g @deepseek-ai/dsh@<old>;
  4. Confirm with dsh --version;
  5. Start once and check the page and sessions.

No uninstall step is needed. Installing a specific version overwrites the current one; uninstalling first only risks ending with nothing if the second command fails.

npx is simpler: put the version inside the command, npx @deepseek-ai/dsh@<old> web. Without a version, it keeps resolving latest.

Plugins must come along. A plugin declares an engines.dsh range, and a downgraded runtime can fall outside it, which shows up as a refusal at install or startup.

When a version revert is not enough, change the entry point. Reverting the method restores the entry you know, without touching data.

  1. Global back to npx: npm uninstall -g @deepseek-ai/dsh, then run npx @deepseek-ai/dsh@<version> web;
  2. npx to global: install a pinned global version and replace npx calls in scripts.

After uninstalling, confirm the command is truly gone. Run which -a dsh; a remaining hit means another install or a stale link. Also check PATH and aliases so nothing points at a path that no longer exists.

This step leaves DSH_HOME alone. Sessions and credentials remain; start again after switching and they are still there.

dsh rollback target three: data

Data is the only rollback with loss risk, so it goes last.

  1. Stop every dsh process and confirm the port is released;
  2. Rename the current DSH_HOME as a keepsake instead of overwriting it;
  3. Restore the backup taken before the upgrade or migration;
  4. Check that permissions belong to your user only;
  5. Start and verify sessions, plugins, and a model call.

Rename before restoring; this is the one step you cannot skip. A wrong restore can be undone, an overwrite cannot.

To reset a single profile, do not touch the whole directory. --from-default-profile <template> rebuilds a named profile from a bundled template and leaves other data intact.

Side by side, the boundaries are clearer. Version rollback touches only the executable, method rollback touches only command and PATH, data rollback touches DSH_HOME; risk decides the order, smallest first. If a cheaper step works, stop there.

dsh rollback order and post-rollback verification

The layers depend on each other: while the command is wrong, you cannot tell whether the data is right.

  1. Restore the command and version until dsh --version prints;
  2. Confirm startup works and the page opens;
  3. Only then judge whether data needs reverting;
  4. After a data restore, re-verify command and startup.

Never run two kinds of rollback at once, because changing both hides which step introduced the new behavior; and be extra careful with the desktop app, which uses a reserved profile name the CLI refuses to start or configure, so never operate on the same data from both.

Finish the order, then verify. Four checks define success:

  1. Version: dsh --version matches the target;
  2. Command: which -a dsh shows only the expected path;
  3. Data: history lists and opens;
  4. Function: a message succeeds and plugins appear.

Any failing check means the rollback is half done. The common case is a reverted version with unreverted plugins, which looks like "starts fine, features missing".

When not to roll back dsh, and making rollback repeatable

Some problems are immune to rollback, and rolling back destroys evidence.

  1. Startup failed with no log yet: collect the diagnosis file first;
  2. The problem is a bad setting; reverting the version will not change it;
  3. The cause is network or credentials; changing the install method is irrelevant;
  4. Just upgraded and have not confirmed whether configuration could fix it.

Classify, then roll back. Configuration, network, and credential problems are only detoured by a rollback.

A repeatable rollback is prepared in advance. The enemy of rollback is hunting for commands under pressure, so record three things in advance: the current stable version, the full start command, and a dated DSH_HOME backup. A recorded rollback takes minutes; an unrecorded one takes an afternoon.

dsh next steps

Revert the version before considering data. To pin versions, read pinning a version. To keep rollback points during a move, read migrating an old install. To clean up multiple copies, read disk usage and cleanup. To recover deleted sessions, read session recovery.

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

ChatGPTClaudeGrok / X / CursorGemini

FAQ

How do I quickly return to the previous dsh version after a bad upgrade?

Install the older version explicitly, for example npm install -g @deepseek-ai/dsh@<old>. There is no need to uninstall first: installing over the current version is the rollback. With npx, pin the version inside the command.

Plugins report incompatible versions after I downgrade. Did the rollback fail?

No, the rollback did not fail: that message is a declared range mismatch between dsh and the plugin. Installation and profile startup check the runtime against engines.dsh, and incompatible plugins require an explicit exemption. A version rollback usually needs the matching plugin versions too.

Do sessions and plugins survive when I roll back the install method?

Yes, as long as DSH_HOME is untouched. Data is independent of how the program was installed. Plugin visibility still depends on using the same profile name, since plugins follow profiles.

When is a dsh data rollback actually necessary, rather than a version revert?

A dsh data rollback is necessary only when the data itself was damaged or deleted. Version and command problems should never touch DSH_HOME, and a data restore requires the service stopped plus a backup taken before the upgrade or migration.

Related Terms

rollback
A rollback is a restore of a version, install method, or data set to a known-good state while keeping the parts that were not affected.— DeepSeek Harness docs
version pinning
Version pinning is the practice of writing an explicit package version into an install or run command so resolution always lands on that version instead of latest.— npm docs
engines.dsh
engines.dsh is the runtime range a plugin declares; installation and profile startup both check the running version against it.— dsh CLI README
DSH_HOME
DSH_HOME is the data root for DeepSeek Harness, defaulting to ~/.dsh, holding profiles, settings, sessions, logs, and credentials.— dsh CLI reference

Sources