DSH Plugins Marketplace

DSH Plugins

Plugins

/

Tools & Capabilities

/

dsh-better-plugin-updater

d

dsh-better-plugin-updater

Manifest valid

Update checker for plugin bundles installed in a DSH profile: a Version section on the detail page of a plugin installed from a GitHub repository or release tarball compares the installed commit or ve

UI (client)hasBundlePatch

dsh-better-plugin-updater

English | 简体中文

Check for and install updates to your DeepSeek Harness plugins, without leaving DSH.

It uses DSH's plugin manager to change packages. Open a GitHub-sourced plugin's detail page to check and review its update, or use the commands below. npm registry packages keep DSH's native update controls. Updates never run without your confirmation.

Requirements

  • Node.js 22 or later.
  • A managed DSH profile, in the Web app, the desktop app or the terminal.

Install

dsh plugin --profile web add dsh-better-plugin-updater

The package is published to npm, so this fetches a bundle that is already built: the install runs no build step and needs no toolchain on this machine. Its own dependencies need no install scripts either, though a profile policy can still prompt for other packages.

Replace web with the profile you use. Then refresh an already-open Web page so the browser half loads.

Installing from the repository works too, but that source holds no built files, so the install has to build the bundle and may ask you to approve that step:

dsh plugin --profile web add github:Mooling0602/dsh-better-plugin-updater

To remove it:

dsh plugin --profile web remove dsh-better-plugin-updater

If the update commands do not appear after a refresh, restart DSH once. DSH remembers that an installed package had no browser code, and an installation that was already running without the browser half keeps that cached answer until DSH starts again. A fresh installation does not hit this.

Use

Update from a plugin's page

Open Plugins and then the detail page of a plugin you installed from GitHub. A Version section appears under its source information and checks for an update as soon as the page opens. It shows the current commit or version against the exact target, and the update runs only after you accept the risk in the confirmation dialog.

This section is for plugins installed from a GitHub repository or a GitHub release tarball. npm registry packages keep DSH's own version control, and a linked or local plugin has no update source to check.

Use the commands

/plugin-updater                   list installed plugin bundles
/plugin-updater check             check every bundle for updates
/plugin-updater check foo         check one bundle
/plugin-updater update foo        show the exact target and confirm
/plugin-updater ok                carry out the confirmed update
/plugin-updater help              show usage

Updates are never applied until you confirm them. /plugin-updater update foo bar accepts several packages at once, and * or ? match package names. Repeating the command, or sending ok or confirm, performs the update you were just shown.

If you already know what you want and accept the risk described below:

/plugin-updater update foo --accept-removal-risk

Choose a language

Commands follow your interface language. To force one:

/plugin-updater --lang zh
/plugin-updater check foo --lang zh

Let the agent check for you

The same checks are available to the agent as the read-only plugin_updates tool. It can list bundles and check for updates, but it cannot install updates, accept the removal risk, approve a build script or grant a compatibility exemption. Updates require your confirmation in the detail page or a slash command.

What it can check

Where the plugin comes fromHow an update is found
npmThe highest stable version in your registry. Downgrades are never proposed.
A Git repositoryThe newest commit on the tracked branch, compared with the commit you installed.
A GitHub releaseThe highest version tag, prereleases included. GitHub's "latest" marker is ignored.
A local folder, or anything elseReported as unsupported rather than guessed at.

Fixed npm versions and GitHub source commits remain protected from updates. Use /plugin-updater update foo --allow-pinned to authorize one update and confirm it normally, or set allowPinned in the configuration for ongoing authorization. A fixed Git commit is compared with the repository's default branch unless sources.foo.ref selects a ref. Use /plugin-updater update foo --allow-pinned --git-branch feature/name to select a branch for one operation. With several packages, the branch applies to each GitHub source package. The selected branch may not contain the installed commit, so review the exact target before confirming. --allow-pinned and --git-branch cannot be combined with --accept-removal-risk, and the newly installed target remains pinned. See configuration.

DSH's own bundles and protected packages are skipped. This plugin can check its own supported installation source, but it cannot update itself. Use an external method appropriate for its source. A local linked installation is not supported by the update checker.

Risks

An update is not atomic. The old package is removed before the new one is installed. If the install then fails, or the package needs a build script you have not approved, the package can be left missing. A recovery target is printed whenever one is known, but recovery is manual and there is no automatic rollback.

For a package from an npm registry, the new version and its dependencies are downloaded before the old package is removed, so the installation itself needs no network. If that download fails, the update stops and the installed package stays as it is. GitHub sources and release tarballs are not downloaded in advance, so those updates still need a network connection when the installation runs.

This plugin never approves build scripts and never grants a compatibility exemption for you.

Configuration

Most settings have a form in DSH's plugin settings page. Open the plugin's entry there, edit the fields and press Save, and the new value applies the next time the plugin uses it, without a restart. The form's labels follow your interface language. sources and indexes are set in the profile patch, because a nested per-package override is not a form field.

Every field is optional.

FieldDefaultPurpose
languageautoauto, en or zh. auto follows your interface language.
sourcesemptyPer-package overrides, described below.
githubTokenEnvGITHUB_TOKENThe credential reference to resolve. Not a token value.
requestTimeoutMs15000Deadline for one metadata request.
maxMetadataBytes4194304Largest metadata response accepted, in bytes.
planTtlMs600000How long a confirmation stays valid.
sources:
  example-plugin:
    kind: npm
    registry: https://registry.npmjs.org/
    channel: latest
    allowPinned: true
  github-plugin:
    kind: github-source
    repository: owner/repository
    ref: main
  release-plugin:
    kind: github-release
    repository: owner/repository
    assetTemplate: plugin-{tag}.tgz

An override must match the source the plugin was actually installed from. It cannot point a package at an unrelated repository.

index sources and the global indexes list are reserved interfaces. This version accepts them and never fetches them.

GitHub token

GitHub allows far fewer anonymous requests. If checks fail with a rate limit, add a token once and the limit stops getting in the way:

# ~/.dsh/.credentials.yaml
version: 1
refs:
  GITHUB_TOKEN: "<your GitHub token>"

Only that one reference is read, and only when a GitHub request needs it. The token is sent to api.github.com and nowhere else. It does not apply to the package download itself, which DSH and pnpm handle separately.

To use a different reference name, change githubTokenEnv to match.

Troubleshooting

Checks fail with a rate limit. Add a token, as described above. GitHub reports a suggested retry time when a limit is confirmed, but this plugin never retries on its own.

A check reports unsupported. The package was installed from a local folder or another source this plugin cannot read. Reinstall it from npm, a Git repository or a release asset.

The package disappeared after a failed update. Reinstall it using the recovery target printed in the update result. Recovery is manual by design.

The update command is missing. Refresh the Web page. If it is still missing, restart DSH once so the package metadata is read again.

See the maintainer context for architecture, wire formats and extension boundaries.

License

MIT

Comments

Loading…

Similar plugins

dsh-plugin-upgrader

by zuwenyin

Adds a Versions tab to the Plugins page: one-click upgrade of all upgradable plugins or a multi-selected subset, version history back to any published release, and GitHub links for each repo and each

Tools & CapabilitiesDevelopment & InfrastructureManifest valid

★ 3

MIT

TypeScript

Oct 30, 2026

dsh plugin --profile web add dsh-plugin-upgrader

by windrover

A DeepSeek Harness plugin that adds a Check-updates button to the Plugins settings: scans every installed bundle for published updates and DSH-runtime compatibility, with a per-plugin update action.

Tools & CapabilitiesManifest valid

★ 0

MIT

JavaScript

Nov 2, 2026

dsh plugin --profile web add dsh-plugin-update-checker

by DogEgg-alR

Install, update and remove DSH plugins from a tab in the Plugins page. Installs call the profile's in-process pluginManager service, so a plugin can be added while the desktop app is running instead o

Tools & CapabilitiesManifest valid

★ 0

MIT

JavaScript

Nov 1, 2026

dsh plugin --profile web add dsh-plugin-installer

by Gty2408

Publish or update a DSH plugin on GitHub in one command: validates the manifest and bundle identifiers, creates or reuses the repo, uploads the tree as one commit, honours .gitignore, and sets the req

Manifest valid

★ 0

MIT

JavaScript

Oct 1, 2026

dsh plugin --profile web add dsh-plugin-publish

by ymh0000123

DeepSeek Harness 插件:检测 DSH / @deepseek-ai npm 包与 GitHub 源插件的更新,设置页给出详细表格,并支持带显式构建授权的一键更新。A DSH plugin that detects updates for installed DSH/@deepseek-ai npm packages and GitHub-sourced plugins, with

Manifest valid

★ 0

MIT

JavaScript

Aug 17, 2026

dsh plugin --profile web add dsh-update-checker

by darkings

A DSH-native plugin update center: check and update installed plugins from the sidebar with snapshots, rollback, queued updates and uninstall-leftover cleanup.

Tools & CapabilitiesDevelopment & InfrastructureManifest valid

★ 2

MIT

JavaScript

Nov 5, 2026

dsh plugin --profile web add dsh-plugin-update-center