dsh-web-all · Official All-in-One Plugin Bundle for DeepSeek Harness (DSH) Web GUI

English | 中文

The official all-in-one aggregate plugin bundle for DeepSeek Harness (DSH) Web GUI and desktop client: install all family plugins with a single command (Task Board / Git Graph / Desktop Pet / Mobile Remote / SSH Ops / Model Capabilities / Session Archive / Skin Center / Settings / Community Plugins, as defined in aggregate.yml). The client compat layer is integrated directly (src/client) eliminating separate compat packages.

Note (alpha branch, 2026-09-17): this branch vendors no external third-party plugins.

What it is

• One install, everything on: its dependencies pull in every sub-plugin package of the family (task board, Git graph, pet, mobile remote, SSH, model capabilities, skins, settings, community plugins and the rest — aggregate.yml is the complete list), and this branch bundles no external npm plugin at all. @mlgbnb/dsh-archive-manager (the community archive manager: group by project, search and filter, preview conversations, restore and delete) is not bundled — its upstream build still imports the removed @deepseek-ai/dsh-client-runtime face.
• Aggregation carrier: cordis.patch.yml aggregates the insert lines of each sub-plugin plus the external plugin rows, mounted through the dsh plugin profile mechanism. External profile bundles are expanded by the generator: their patch rows become importable aggregate rows, the bundle's own harness-row patches are preserved, and an external row marked "inactive": true gains trailing disabled: true overrides so nothing mounts until you opt in.
• Fault isolation (the shell): the DSH loader mounts all patch rows as one transactional group — a single plugin that fails to import or start would roll back the whole group and abort dsh web. The aggregate therefore mounts every family plugin behind a never-failing shell module (this package's main entry): the row name points at a per-family subpath export @linxin666/dsh-web-all/<family> and the row config names the real plugin package. The subpath is what the official plugin list (Settings → Plugins) displays — one distinct web-all/<family> title per row (the same multi-entry convention as the host's own web-app/startup row) — while all subpaths resolve to the same shared shell re-export, so the isolation semantics are identical. A broken plugin now degrades alone (logged, and listed by the loopback-only health route GET /api/dsh-web-all/degraded) while every other plugin mounts normally. External rows (npm packages outside the family) keep mounting directly; dsh-i18n stays direct (empty host half).
• Its own icon in the plugin list: the package ships icon.svg and declares it as the top-level package.json.icon, the display-metadata field the official Plugins list (Settings → Plugins) reads, so the installed card and detail page show the family whale in both themes instead of the default artwork. Every family package ships the same asset, so a standalone install of one shows it too. The field resolves per module specifier: the aggregate itself exports its package.json, while the family subpath rows do not, so those rows keep the default artwork and their web-all/<family> titles.
• Opt-in rows: low-usage family plugins ship disabled by default in the aggregate (currently SSH and skill-explorer — the inactive list in aggregate.yml; liangshen stays out of it, so the LiangShen mode lever is present on a fresh install). They never load and their settings entries stay hidden until you enable the row under Settings → Plugins → Plugin manager; the standalone packages are unaffected. Bundle rows can also ship a seed config that differs from the standalone default (the patches list); a settings edit wins once made.
• Per-row management: every family plugin toggles individually — under Settings → Plugins → Plugin manager this package's row expands into a child list with one switch per family plugin, written to the profile override layer. The host half tells the browser half which rows are active (GET /api/dsh-web-all/rows), so a disabled row's settings entries leave the page too (any route uncertainty fails open and mounts everything, as before). A disabled child is never loaded while its code still updates with the bundle; install the standalone package when a plugin needs independent versioning (a standalone install wins over the aggregate row).

Install

From npm (recommended)

DSH Web CLI (Browser):

dsh plugin --profile web add @linxin666/dsh-web-all@latest
# Restart dsh web
dsh web

Official Desktop Client (DeepSeek Harness Desktop):

• Open the official desktop client and navigate to "Settings > Plugins" (or the sidebar plugins view)
• Enter @linxin666/dsh-web-all into the install input field and click Install
• Fully quit and restart the desktop client once installation completes

From the repository (development)

git clone https://github.com/zhu1090093659/dsh-web.git
cd dsh-web
pnpm install && pnpm -r build
node scripts/link-profile.mjs
dsh plugin --profile web add link:$(pwd)/packages/dsh-web-all

Restart dsh web (or the official desktop client) for the plugins to take effect.

Manual upgrade

When you upgrade by bumping the version in the profile package.json and running pnpm install, the top-level node_modules/@linxin666/* entries are not always refreshed: they can stay linked to the previous version's store directory until recreated. After upgrading, verify the links resolve to the new version (on Windows: cmd /c rmdir <link> then cmd /c mklink /J <link> <target>), then restart dsh web.

Troubleshooting

"Failed to load plugins ... keyed slot settings.plugin.item requires options.key" (DSH 0.1.0-rc.6+)

Versions up to 0.1.17 of the bundled dsh-client-ui-web-ui-settings registered its card in the keyed settings.plugin.item slot with an id instead of the required key (the other family plugins already registered their cards in the group's list slot). DSH 0.1.0-rc.6 and later reject such entries while the loader entry applies, so the web GUI fails to boot with "Failed to load plugins".

The group moved to a first-level settings.section registration in 0.1.18 and ships in 0.2.0; the code on main is compatible with rc.6 and rc.7. A profile that still fails carries a frozen older install:

1. Bump every @linxin666/* dependency in the profile package.json to ^0.2.0 (at least ^0.1.18).
2. Reinstall the profile dependencies (pnpm install) and recreate the stale node_modules/@linxin666/* links as described in Manual upgrade above.
3. Restart dsh web.

See issue #513.

Known limitations

• Every sub-plugin activates together. For only a subset, install that sub-plugin package directly.
• Aggregate rows are namespaced web-ui-*, so the bundle can coexist with a standalone install of the same plugin: the loader no longer rejects the duplicate id, the host half runs once (the second source is a no-op), and the browser half is deduped by package name. Keeping both sources has no benefit; prefer one. When the bundle is the source, profile patch config rows must use the web-ui-* id (e.g. web-ui-remote-web-ui for the remote-web-ui autoTunnel row); standalone installs keep the plugin's own id. A bundled row's config carries the shell key plugin — the module the row loads — with the plugin's own fields beside it; the settings card writes that shape, and a hand-written override must keep plugin or the row mounts nothing.
• Dependencies on the @deepseek-ai/* SDK are pinned; compatibility follows the repository's release cadence.