How to update DeepSeek Harness and its plugins

Updating DeepSeek Harness has two layers: the binary (npx stays latest, npm update -g, source git pull) and plugins (click Update in the Plugin Center or reinstall via command). This guide walks through prepare, update the binary, update plugins, and post-update checks — each with commands, plus a troubleshooting table.

Overview: updates come in two layers — binary and plugins

The binary is the program, plugins are the extensions, and the two update independently. Knowing the layers prevents confusion (source):

1. Binary update: swap @deepseek-ai/dsh for a new version;
2. Plugin update: upgrade installed plugins to newer versions;
3. Layers are independent: updating the binary never updates plugins, and vice versa.

The ways for each layer at a glance:

Step 1: prepare before updating

Record the version, back up sessions, then act — so you always have a way back. Steps:

1. Record the current version for comparison and rollback:

dsh --version
# or the npx route
npx @deepseek-ai/dsh --version

2. Back up key session data:

cp -r ~/.dsh/sessions ~/.dsh-sessions-backup

3. Confirm enough disk space and a stable network; keep the terminal window running and do not interrupt the process.

Step 2: update the binary

How you update the binary depends on how you installed it — run the matching command.

Route 1: npx (automatic)

npx re-pulls the latest version on every run, so no manual update is needed. Just start:

npx @deepseek-ai/dsh web

Fallback: if the version has not changed, clean the cache and restart:

npm cache clean --force && rm -rf ~/.npm/_npx
npx @deepseek-ai/dsh web

Route 2: npm global update

If you installed globally, upgrade to the latest in one command:

npm update -g @deepseek-ai/dsh

Confirm the version with dsh --version afterwards; on an EACCES permission error add sudo, or switch to the npx route.

Route 3: source build update

If you cloned and built from source, pull the latest code and rebuild:

# Enter the source repo directory
cd ~/dev/deepseek-harness

# Pull the latest code (git stash first if you have local changes)
git pull

# Reinstall dependencies and rebuild (same as the initial install)
npm install
# Run the build command from the repo docs, e.g. npm run build

Once the build finishes, restart dsh web to use the new version.

Step 3: update plugins

Use the Plugin Center for a visual plugin update — one by one or in batch.

Route 1: Plugin Center (recommended)

1. Open Settings → Plugin Center → Installed (install DSH Plugin Hub first);
2. Rows showing an Update button have a new version; click Update and confirm the plugin and its source in the dialog;
3. Wait for the in-place reinstall; refresh the page after the progress finishes;
4. For multiple updates, go through them one by one or batch-process them in the list.

Route 2: command-line overwrite

Prefer the terminal? Overwrite-install to the latest directly:

# Overwrite install: re-fetches the latest version if already installed
dsh plugin --profile web add <package>

If a plugin update fails (e.g. a git source missing build artifacts), reinstall the npm version from DSH Plugin Hub — a more reliable source.

dsh-plugin-hub · system logs

Step 4: check after updating

Run a verification round to confirm it is a real update, not a fake one. Steps:

1. Confirm the version number changed (dsh --version);
2. Open http://127.0.0.1:3080 and confirm the UI works;
3. Open the Installed list in the Plugin Center and confirm plugin states and refreshed versions;
4. Check the system logs for update-related errors; the notification center records both successes and failures.

Update failed? Troubleshooting table

Read the error type first, then fix accordingly. Common issues:

Quick reference

In one sentence: update the binary and plugins separately — binary by install type (npx / npm update -g / git pull + build), plugins via the Plugin Center "Update" button or a command-line overwrite; back up before, verify after. Four reminders:

1. Record the version and back up sessions before updating so you always have a way back;
2. The binary and plugins are two different things — no single command updates both;
3. Prefer the Plugin Center for plugins: visual, with progress and records;
4. Four checks after updating: version, web page, plugin list, system logs.

Sources: dsh CLI README, dshplugin/dsh-plugin-hub, DeepSeek Harness docs - Quickstart