dsh-style-hub
DeepSeek Harness Web GUI 的主题工作室：预设样式、微调和主机端壁纸上传。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:Au1314/dsh-style-hub#dfd42aa92d6e7d38cd5b998b95d9761602489e1e
Style Hub 以 dsh-style-hub 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
English | 中文
dsh-style-hub is a composition plugin (host half + browser half) that gives the DeepSeek Harness Web GUI three things in one settings card:
Everything lives in the Plugins → Style Hub card. Turning the master switch off restores the appearance exactly as it was: this plugin never decides what "normal" looks like for your deployment.
The package wires itself: dsh.bundle.patch points at the bundled cordis.patch.yml, which inserts one host row (dsh-style-hub) over whatever layers the profile already composes. The browser half is discovered separately, through the dsh.client manifest in package.json. Neither half needs a hand-written row.
In a DSH Desktop profile (the usual way to try it):
Unpack the package into the profile's node_modules, named after the package:
cd "$DSH_HOME/profiles/web/node_modules" # e.g. %APPDATA%/dsh-desktop/harness/profiles/web/node_modules
tar -xzf dsh-style-hub-0.1.0.tgz && mv package dsh-style-hub
In that profile's package.json, add "dsh-style-hub" to dependencies and to dsh.profile.bundles.
Re-install the profile (pnpm, hoisted) and restart the app.
In a composition you own: add dsh-style-hub to the same bundle list that carries @deepseek-ai/dsh-base and @deepseek-ai/dsh-web-app, install, restart.
Requirements. A web composition that already carries dsh-client-ui-settings-plugins (the card's slot), dsh-client-ui-theme (the theme registry), and dsh-client-locale. The runtime peer range is >=0.1.5-rc.2 <0.2.0; npm run build typechecks against 0.1.5-rc.3, the first release of that line that ships type declarations.
The Host registers the style-hub settings namespace, serves /api/style-hub/wallpapers, and answers every page load with the boot wallpaper rule. webServer is an optional peer: in a profile with no HTTP surface the bundle still loads, and the route plus the boot rule simply stand aside.
Open Settings → Plugins → Plugin configuration → Style Hub.
1 keeps the theme's own fills.The card writes immediately — there is no save button — because each field is a single revision-fenced write through the client settings scope.
setTheme only ever persists light, dark, or system, so a style this plugin registered cannot survive a reload on its own; the style-hub section is what replays it. That also means the preference the user held before this plugin ever selected one of its own has to be remembered somewhere else. It is: the browser half captures it at start and observes every later theme/change, so switching the master switch off hands the preference back rather than pinning a default. Stock never writes to Appearance at all — selecting it means "leave that preference where the user put it".
The section is flat (one field, one write) and every value below is validated twice: by the Host schema, and again by validateSettings, which is where the ranges live.
| Field | Type | Range / values | Default |
|---|---|---|---|
enabled | boolean | master switch | false |
themeId | string | stock, or a bundled preset id | stock |
accent | string | #rrggbb, or empty to follow the style | "" |
panelOpacity | number | 0.8 … 1 | 1 |
wallpaperId | string | hex storage id, or empty | "" |
wallpaperFit | string | cover | contain | cover |
wallpaperOpacity | number | 0 … 1 | 1 |
wallpaperBlur | number | 0 … 50 px | 0 |
wallpaperDim | number | 0 … 1 | 0 |
Bundled preset ids: nord, dracula, mocha, tokyo-night, gruvbox-dark, solarized-light, github-light, latte. The registered theme ids are those with an sh: prefix, so they can never collide with another plugin's themes.
$DSH_HOME/dsh-style-hub, overridable with DSH_STYLE_HUB_DIR): images/ holds the bytes, catalogue.json holds the index./api/style-hub/wallpapers, dispatching on its own sub-path: GET the catalogue, POST an upload, GET/DELETE /:id.Origin/Referer, ids are 32 hex chars and are the only path segment the route will read, and display names are stripped of anything a header or markup context could misread.The Host renders the same wallpaper rule into index.html as an injection row, so the very first paint already shows your picture; the browser half then owns that layer for the rest of the session.
No menu blur. A backdrop-filter on the menus would need a stable hook the design system does not offer — --dsw-mask-blur is declared but never consumed, and the menu cards carry no class this plugin may rely on. The equivalent effect is delivered with tools this plugin does own: panel translucency (the surfaces above the picture go translucent) and wallpaper blur (the picture itself is softened). If the design system later publishes a menu hook, a blur option can be added without breaking anything here.
The canvas is capped while a wallpaper shows. ui-layout paints the frame with an opaque --dsw-alias-bg-base, so with a wallpaper active the base is held at 0.85 alpha — enough for the picture to read through, not so much that the frame stops being a frame.
Tokens are derived, never copied. Each preset is twelve swatches; tokensFor derives the whole --dsw-alias-* directory from them, and no preset emits a --dsw-static-* value (those are shared constants, and overriding them would leak one style into every other). The test suite reads the required token names out of the installed design-system stylesheet, so the derivation is checked against the system rather than against a stale copy.
One tweak layer. Accent and translucency are stacked as a single override layer with a fingerprint, so a reconciliation pass that changes nothing writes nothing — and an empty layer is torn down instead of being registered as "applied but empty".
style-hub section; the built-in Appearance preference stays light/dark/system. Reloading replays it from the section.index.html, but the colour scheme is not: there can be a beat before the selected style lands. Injecting the boot palette is a known follow-up.menuBlur does not exist. See Design decisions.npm install --legacy-peer-deps
npm run check # typecheck, build all three artifacts, syntax-check, test
npm run build produces:
lib/index.js — the Host half, ESM, bare specifiers external.lib/client.js — the browser half, wrapped in the window.__ModuleLoader__.load({ id, factory }) shell the composition's module loader expects.lib/types/** — the declaration tree (emitted separately, because the sources import .ts extensions).test/build/*.test.js — the tests, bundled because they import TypeScript sources directly.Tests are plain node:test:
npm test
See docs/architecture.md for how the two halves fit together.
MIT — see LICENSE.