@1e0zj/dsh-plugin-mall
发现并一键安装dsh-plugin生态仓库的市场与更新入口 适合希望集中管理插件来源的用户,需可联网访问GitHub并在市场页操作
安装
npx -p @deepseek-ai/dsh dsh plugin --profile web add github:1e0zj/dsh-plugin-mall说明文档
阅读完整 README ↗dsh-plugin-mall
An open plugin marketplace for DeepSeek Harness (dsh): search every GitHub repo tagged topic:dsh-plugin, automatically verify which ones are real dsh plugins, install and update with one click.
中文说明 · Install · Why another marketplace · Roadmap
Two surfaces: a Settings → Plugins → Marketplace tab in the dsh web UI, and five agent tools usable from any session.
Why another marketplace?
Curated lists only show what has been reviewed and merged. This marketplace is open by construction: any repo tagged topic:dsh-plugin is discoverable the moment it is pushed — no submission, no approval queue. To keep that openness usable:
- Automatic verification — every search result's
package.jsonis fetched (jsDelivr/raw dual-source CDN, no API quota) and checked for the officialdsh.bundle/dsh.clientmanifest. Verified plugins get a green badge; the default "verified only" view filters out ~73% of topic noise (empty repos and unrelated projects riding the tag). - Browse-time compatibility badges — each card is also statically scanned against your profile before you click anything: declared conflicts, exclusive groups, loader-id collisions (from the repo's patch file), rows the candidate's patch would switch off or reconfigure in the profile you already run, host-module shadowing, and peer/Node/OS ranges. Cards show 适配 / 有风险 / 冲突 / 适配未知 accordingly — advisory only; the install preflight remains the enforcing gate.
- Anti-squatting — an install prefers the npm tarball only when the registry entry's
repositoryURL points back to the same GitHub repo; anything else falls back to the explicitgithub:spec. - npm-first installs — registry tarballs are smaller than whole-repo GitHub downloads and come with integrity checks. Lookups follow the registry pnpm actually installs from (profile
.npmrc→pnpm config get registry→ npmjs), so a mirror user keeps npm-first instead of silently falling back to whole-repo clones. - Update management — installed plugins are compared against the registry
latest; one-click update per plugin. - Conflict guard — every install runs an isolated preflight first: the candidate is installed with scripts disabled into a throwaway directory and scanned against the live profile for loader-id collisions, double mounts, host-module shadowing and version/OS/peer ranges. A patch layer is not read entry by entry but composed the way the loader applies it — the profile is assembled with and without the candidate's layer, in the position dsh would apply it, and the two trees are diffed. That composition is checked against the loader's own
applyEntryPatcheson every test run, over fixed shapes and 300 generated patch combinations, so "what dsh would boot" is not a guess. What gets reported is what would actually change: disabling, re-enabling or replacing the config of someone else's rows warns and names them, past ten such rows the candidate is a rival composition rather than an addition and is blocked, and a bundle that is itself another front door (ownbin, terminal peers, no browser half) is blocked once it switches rows on or off or rewrites a protection row — the fingerprint corroborates, it never blocks on its own. A hard conflict is blocked, warnings require explicit confirmation. The profile's load-bearing files are snapshotted beforepnpmtouches them and restored on failure. A pending install is resolved on the next start, however you start it: this plugin runs recovery as it loads. That proof is narrower than it sounds — it means the loader reached the marketplace's position, not that the whole tree composed (#24). Starting throughguard launchadds a grace window on top, covering both a plugin that crashes seconds later and an import/apply failure in an entry after the marketplace (see Startup protection). - Resilience — rate-limit circuit breaker, GitHub's 1000-result search window handled gracefully,
corepack enable pnpmself-heal when pnpm is missing, one-click dsh restart (loopback-only,allowRestart: falseto disable). The outgoing Host exits only after the on-disk helper explicitly acknowledges the current handoff protocol and stays alive through a stability window; a missing, stale or incompatible helper leaves the existing Web service running. The successor then waits for the outgoing host to be gone before it binds — starting into an occupied port would read as "the pending plugin crashed dsh" and roll back an install that was fine. On Windows started from an interactive terminal, the restart runs in a visible console window (cmd /c start; the wrapped argv travels as a JSON plan file, never through the cmd command line): output is teed to the window and to the log, and closing the window terminates the whole guard/dsh tree (the close event bypasses console input processing entirely, so it always works). Ctrl+C in the window is honored best-effort — live testing showed a component inside dsh can flip the console into raw mode, after which no process on that console receives Ctrl+C at all; closing the window is the reliable stop. Service/scheduled-task/TTY-less Windows and every other platform keep the fully background behavior — no stray console, no re-opened browser (the page that asked is still there and reconnects on its own); whatever the restart prints lands in/guard/restart- .log.
Install
# from npm
dsh plugin --profile web add @1e0zj/dsh-plugin-mall
# from GitHub
dsh plugin --profile web add github:1e0zj/dsh-plugin-mall
# local development — currently unusable, see the note below
dsh plugin --profile web add link:C:\path\to\dsh-plugin-mall
Restart dsh after installing.
link:cannot be set up right now, for reasons upstream of this plugin. Underlink:Node loads from the project's real path, so bare imports must resolve from the project's ownnode_modules— which requiresnpm installinside the project first. That fails: the framework packages' registry dist-tags currently straddle two release trains (dsh-toolslatest is still0.0.1-rc.xwhiledsh-app-bootis on0.1.0-rc.x), their peer ranges do not intersect, and npm stops with ERESOLVE. Neither escape hatch helps —--legacy-peer-depsskips peers so bare imports still will not resolve, and--forceplants a mixed-train copy of the framework inside the project, whichlink:would then load instead of the host's, causing exactly the duplicate-module crash described under 开发说明. Until those dist-tags line up, develop against a local tarball —npm pack, then install the.tgzwith afile:spec (recipe in the 安装 section below). Do not hand-overwrite files undernode_modules: they are hard-linked into pnpm's global store, and any laterpnpm add/removerebuilds the tree and restores them anyway.Re-packing and running
addagain does nothing: thefile:spec and the version are unchanged, so pnpm calls it already installed and never compares the tarball's bytes. The command succeeds,package.jsonlooks right, andnode_modulesstill holds the previous build. Alwaysremovebeforeadd, or give the test build its own version. Then restart dsh completely — the install ran inside the host process still executing the old code.
Startup protection (guard CLI)
Known issue — every version since v0.3.4, including v0.4.17 (#24): a plain
dsh webstart may commit and delete the pending snapshot as soon as the marketplace plugin loads, before later loader entries have finished loading. Downgrading is not a workaround — you would have to go back before v0.3.4 and give up every fix since. If a later entry fails, automatic rollback is no longer available. Until #24 is fixed, useguard launchfor the first restart after every marketplace install or update. The marketplace's "Restart dsh" button already uses the guarded restart path (it spawnsguard launch --await-exit), so restarting from the UI is safe.If the log already shows
startup recovery: committedand the start then fails,guard recoverusually has no snapshot left to restore — repaircordis.patch.ymlby hand, or restore a profile backup.
The last line of defense is at startup. The package ships a standalone, host-independent CLI (bin dsh-plugin-guard, also runnable by path):
# guarded install: isolated preflight → snapshot → dsh plugin add → on-disk validation
dsh-plugin-guard guard add --profile web
# start dsh under startup probation
dsh-plugin-guard guard launch --profile web -- dsh web
The bare dsh-plugin-guard bin resolves only when the profile's (or global) .bin is on PATH. Two PATH-independent forms:
# installed profile: run the bin from the profile's own node_modules/.bin
pnpm --dir
exec dsh-plugin-guard guard add --profile web
pnpm --dir
exec dsh-plugin-guard guard launch --profile web -- dsh web
# development: run by source path
node
/node_modules/@1e0zj/dsh-plugin-mall/src/cli.js guard add --profile web
node
/node_modules/@1e0zj/dsh-plugin-mall/src/cli.js guard launch --profile web -- dsh web
A plain dsh web already resolves pending installs. The marketplace plugin runs
recovery when it loads, so the pending marker is committed — or rolled back, either
because the profile fails validation or because the install was left paused at the
build-script approval gate (an unapproved install is never committed, however healthy
it looks). Without this a single install would wedge the profile — every later install
and uninstall refuses while a marker is outstanding.
What a plain start actually proves is narrower than it looks: reaching the
marketplace's own apply only means the loader got as far as the position the
marketplace occupies — it does not mean the whole plugin tree composed. Entries
after it may still fail to import or apply, and by then the snapshot is already
gone (that is #24).
guard launch is still strictly better, and for two reasons rather than one:
it covers a plugin that boots fine and then crashes seconds later, and it covers
an import/apply failure in a loader entry that comes after the marketplace — the
case a plain start commits straight through. It checks the profile's pending-install
marker before starting the command after --:
- No pending install — the command runs as-is, inheriting the terminal, and its exit code is preserved.
- Clearly broken on disk — the profile is rolled back to its pre-install snapshot before launch, then the command starts on the restored state.
- Alive through the grace period (default 10 seconds;
--grace-msto change) — the pending snapshot is committed and the wrapper keeps waiting on the process. An install still paused at the approval gate is rolled back instead: surviving probation only proves the JS loads, not that you approved its build scripts. - Exits 0 inside the grace period (one-shot command) — the pending snapshot is committed.
- Crashes or exits nonzero inside the grace period — the profile is rolled back and the exact same command is restarted once with the restored state (never in a loop); the restarted process's exit code is preserved. SIGINT/SIGTERM are forwarded to the child where the platform supports it; on Windows
.cmd/.batshims go through%ComSpec%with strict per-argument quoting.
Limitations: the grace window is the probation period — a failure that only surfaces after it (a plugin that crashes minutes in, or on a specific interaction) cannot be rolled back automatically, because committing deletes the active snapshot and guard recover then has nothing to restore. guard validate still diagnoses the on-disk state, but a post-commit failure needs manual repair — uninstall and reinstall the plugin, or restore a backup you kept separately. Both commands do only static on-disk validation; neither proves the plugin actually loads. A corrupt pending marker fails closed: the command is not launched and no unvalidated path is deleted. Preserve the snapshot and repair or restore a trustworthy marker, then run guard recover; quarantine the marker only after you have independently verified the profile, or decided to abandon automatic recovery.
dsh won't start after an update? (affects 0.2.0 – 0.3.2, fixed in 0.3.3)
Symptom: dsh web exits with cannot resolve profile bundle " ".
Cause: updating an already-installed plugin into a rollback (most often the target carries build scripts and the flow paused at the approval card) could lose the package — the rollback's reinstall of the old version was fooled by pnpm's "Already up to date" short-circuit, so the plugin left node_modules while its bundles declaration stayed. Fresh installs and removals are unaffected.
Recovery: add the package back exactly as the profile's package.json declares
it, then run dsh web.
#
= %USERPROFILE%\.dsh\profiles\web or ~/.dsh/profiles/web
# npm package — package.json says "dsh-better-sidebar": "^0.13.1"
pnpm --dir
add "dsh-better-sidebar@^0.13.1" --ignore-scripts
# GitHub source — package.json says "dsh-at-file": "github:omdsh-dev/dsh-at-file"
pnpm --dir
add "github:omdsh-dev/dsh-at-file" --ignore-scripts
Do not reach for 0.3.2's
dsh-plugin-guard recoverhere. Its per-package fallback refuses^(a cmd metacharacter) and skipsgithub:entirely, and pnpm writes nearly every dependency with one or the other — so the fallback never fires and recovery fails closed. Fixed on main: the fallback now pins the version (or commit) the lockfile resolved. Fixed in 0.3.3 — on that versiondsh-plugin-guard recoverdoes repair this.
Update stuck at the install-script approval card? (updates to 0.4.15)
Symptom: updating the marketplace itself pauses at "安装期代码需要确认", and
clicking 允许 fails with allowBuildScripts cannot be specified on initial install. Clicking again does not help.
Who hits it: only profiles that have never approved a dependency with install
scripts (in practice node-pty, pulled in transitively). If your profile's
pnpm-workspace.yaml already carries allowBuilds: {node-pty: true} — most
profiles that have installed anything do — the approval card never appears and
the update just works.
Cause: pnpm installs the new marketplace package before the approval gate, which swaps the running plugin on disk; dsh replays the assembly tree and the whole marketplace UI remounts, losing the browser session the approval token was issued to. The token is then unrecoverable, so the retry arrives without it.
Recovery — restart dsh (startup recovery rolls the paused install back), then either update from the CLI:
#
= web, guard-test, ...
dsh plugin --profile
add @1e0zj/dsh-plugin-mall@0.4.15
or pre-approve the build scripts once and update from the page as usual:
#
/pnpm-workspace.yaml
allowBuilds:
'node-pty@1.1.0': true
Fixed from 0.4.15 onward — the session identity now survives a remount. The fix cannot rescue the hop to 0.4.15 itself: during that update both the page's pre-swap code and the running dsh process are still the old version.
Agent tools
| Tool | What it does |
|---|---|
market_search | Search GitHub repos tagged topic:dsh-plugin (star-ranked, keyword filter, server-side stars:>=1 noise floor) |
market_info | Inspect one repo: stars, license, package.json, whether it declares `dsh.bundle.pat |