bertonhan/dsh-plugin-installer-pkg

A plugin installer for DSH delivered as an install script and an in-GUI page. Per the README, installed manifests persist by default in store.json and are restored when their session reopens, with restore failures surfaced on the page; manifests carry an optional version field so reinstalling the same name/id switches to update mode and replaces the running version; and every row has Stop/Remove (remove = stop + delete the persisted manifest + cancel persistence), alongside uninstall.sh, an example plugin package and an MIT licence. Installation is conversational-first — the agent runs the script and offers to restart the service with verification — with the manual script flags documented as an equivalent path.

Plugin Markets & Managers ★ 0 updated 2026-08-14 ✅ runtime-tested
View on GitHub ↗

Install

bash install.sh

README quick start: hand the directory (or an archive) to a DSH conversation and say "install this plugin" — the agent follows AGENTS.md, locates DSH_HOME and the profile, runs the idempotent install.sh, and asks about restarting. The equivalent manual commands are documented verbatim: bash install.sh (auto-detect the only profile), bash install.sh --profile web (explicit profile) and bash install.sh --dsh-home /path (specific DSH_HOME). The script copies the plugin package, creates the @local/dsh-plugin-installer symlink, appends the composition row (skipped when already present) and verifies Node resolution. Uninstall with bash uninstall.sh (--keep-data retains persisted manifests). After a restart, verify with curl -s http://127.0.0.1:3080/ | grep -c "@local/dsh-plugin-installer" (expect 1) and a 200 on /plugins/@local/dsh-plugin-installer/client.js.

Compatibility

DeepSeek Harness with a DSH_HOME and at least one profile; the script auto-detects a single profile or takes --profile. The README also documents a restart-free trial path: hand dsh-plugin-installer.json to the DSH agent and install it with cordis_define + cordis_run (session-scoped, writes nothing to disk, so persistence and in-page approval are unavailable in that mode).

Details

Recent updates

The README documents the persistence semantics (manifests in store.json, restored on session reopen), versioned hot updates, full removal behaviour and the uninstall flags, plus an FAQ table (e.g. a git clone failure check for git availability, repo reachability and the manifest path for monorepos). It does not publish a versioned changelog; the script itself is idempotent and safe to re-run.

FAQ

How do I install this plugin installer?
Hand the directory to a DSH conversation and say "install this plugin", or run the documented manual form: bash install.sh (auto-detect the only profile), bash install.sh --profile web, or bash install.sh --dsh-home /path.
Are installed plugins persistent?
Yes — per the README, manifests are written to store.json and restored when their session reopens, and restore failures are shown on the page as "restore failed". Use uninstall.sh --keep-data to keep manifests when removing the installer.
How do I uninstall it?
bash uninstall.sh (or --profile web / --keep-data variants), then restart the DSH service.

Alternatives

imsai-sh/awesome-deepseek-harness-plugins · LX2000WASD/dsh-web-plugin-manager · 2BingLing/dsh-market

More plugins in Plugin Markets & Managers

Browse more in Plugin Markets & Managers

Guides for Plugin Markets & Managers plugins