dsh-any-background

dsh-any-background

English | 中文

A DeepSeek Harness appearance plugin: custom theme color, background wallpaper (image / video / algorithmically generated), and per-surface opacity & blur control. Compatible with DSH 0.2.0-rc.1 through 0.2.2-rc.3 — and every host release above it.

---

Screenshots

Custom homepage · wallpaper + theme color applied	Theme color picker · PS-style wheel + HSL/RGB inputs
Per-surface opacity and blur	Background editor · pan and zoom
Generated background · mesh gradient / Shader / geometric	Generated background · geometric low-poly
Export and import configs to share them

Features

Color & theme

• PS-style color wheel — Hue on the ring, saturation and lightness in the inscribed square; generates 30+ CSS design tokens live.
• Precise HSL / RGB input — Numeric entry, bidirectionally synced with the wheel.
• Smart extraction / eyedropper — One click derives a theme color from the wallpaper (sampling the visible area and discarding gray, near-black and near-white), or hover any pixel to pick it. Video wallpapers contribute an auto-captured frame. All client-side.
• Forced light / dark scheme — Light, dark or auto. In auto the surface and font direction follow the accent color's lightness (dark pick → light text), falling back to the wallpaper's brightness when no accent is set.
• Theme export / import — A self-contained dsh-any-theme.json (config + wallpaper + the whole rotation pool) that restores anywhere.
• Presets & profiles — Six one-click presets plus named profiles that can be renamed and duplicated; deleting asks for confirmation twice.

Background & wallpaper

• Image wallpaper — Upload any image as the background.
• Video wallpaper — Muted, looping, survives refreshes (persisted on disk + HTTP Range streaming), with one frame captured for the preview, color extraction and position editing.
• Position editor & layout modes — Drag to pan, scroll or pinch to zoom, one-click reset; Fit / Fill / Stretch / Tile / Center. Image and video placements are stored separately and never overwrite each other.
• Generated backgrounds — Mesh gradient, Shader or geometric patterns, with adjustable spread and intensity and a lockable seed.
• Wallpaper rotation — Build a pool with the thumbnail picker and rotate by shuffle or order, on every refresh / hourly / daily / weekly; the cadence advances while the page stays open, not only on reload.
• Day / night switch — A day profile and a night profile, switched on a fixed schedule or by following the OS dark mode.

Per-surface opacity & blur

• Eleven parts, each with its own slider pair — main background, sidebar, card panels, input & controls, settings panel, conversation frame, trajectory view, right sidebar (or bettersidebar), produced / highlighted content, header popovers, and the header bar.
• The slider IS the frost amount, and 0 means no frost — including over the host's own default menu frost. Every part still defaults to 30px, so a stock install keeps the frosted look.
• Opacity re-scopes the host's own token — it never stacks a second color over the original, so the wallpaper shows through the content.
• Produced / highlighted content shares one slider — code blocks (with their language banner), inline code chips and produced chips move together.
• Right sidebar / bettersidebar: one pair, two identities — without dsh-better-sidebar it drives the official right sidebar; with it installed the same pair takes over that plugin's bottom workbench panel (the official sidebar keeps responding too).
• On the Windows desktop shell it also drives the caption band — the sidebar pair paints the segment directly above the sidebar, and the cut follows the sidebar's width as it is dragged or collapsed (at width 0 the band returns to the header card). The 「标题栏」 card drives the rest of the band and the native window controls, with a four-state 「标题条带文字」 choice (auto / follow theme / always white / always black) for when a light strip fights the theme.

Interface parts

• Sidebar "Theme" page (dual mode) — The same five pages (Color / Interface / Font / Background / Profiles) register into the official right sidebar's guide page or into dsh-better-sidebar's sidebar, sharing one state with the settings panel, so a change anywhere shows everywhere. On a host without that extension point nothing is registered, silently.
• Conversation view cards — The message list is wrapped in a translucent card automatically, and the trajectory page adjusts as a whole page.
• Header popovers and the header bar are separately adjustable — the Agent Team panel, the background-job list, the session-header dropdowns, and the title / view-tab row at the top of a session each have their own opacity + blur pair.
• Custom font — Upload a ttf / otf / woff / woff2 (up to 100 MB) and apply it across the interface; code blocks stay monospace. Can be disabled or removed at any time.
• Per-part text outline — The same surface groups as the interface page, each with its own -webkit-text-stroke (0–4px, 0 = off) in auto-contrast / gray / black / white / accent / custom. Code blocks, inline code, icons and the host's gradient-shimmer text are exempt automatically.
• Third-party compatibility — When dsh-better-display is detected, its sticky summary band is pinned at a 20% plate + 30px frost outside the sliders. Any other plugin whose surface reads a token this plugin owns is named in the console, and the whole accommodation can be switched off in Settings.

General

• File-based persistence — Everything is stored under ~/.dsh/.dsh-any-background-data/, not in localStorage.
• Bilingual UI — Full Chinese / English interface following the host's locale.
• Theme watchdog — Re-asserts the custom theme if the host resets it.

Changelog (latest two releases)

v0.4.3 (follows dsh 0.2.1-rc.5 and the newly opened 0.2.2 line)

• Newly checked host builds: 0.2.1-rc.4, 0.2.1-rc.5, 0.2.2-alpha.2.
• rc.4 / rc.5 change nothing. Every shipped file of the 296 @deepseek-ai/dsh-* packages in a 0.2.1-rc.3 install was hashed through rc.5: 30 files moved in total, and not one of them is a stylesheet this plugin reads. Three are inlined version-string literals; the rest are the host's settings-tab tooltip becoming conditional and the reasoning-body slot gaining a rawText. No token, no [class*="…"] class shape, no z-index and no data-slot key moved, so both builds join the v0-2-1 row and their verdict rises from line to exact.
• 0.2.2 is a new patch line, so v0-2-2 opens its own facts folder. That release is big (1151 files changed, 1709 added), but every fact this plugin claims was re-read and still holds: _handle{z-index:11} / _leadingSeat{z-index:15} / _overlayLayer{z-index:20} are byte-identical (so the sidebar column's ceiling of 1 and the header row's 10 are argued exactly as before), the four menu-frost tokens and the 8 --dsw-menu-backdrop-filter consumers are unchanged, the host still composes --dsw-font-family on body (the font rule's !important still has to win), the five session-header slot keys stand, and all 75 host selectors this plugin writes still match. The host's peer gate is byte-identical too.
• Two host changes on 0.2.2 worth recording: --dsw-specific-sidebar-nav-item-hover is deleted host-side, together with its only consumer — the plugin still writes the token, which now writes something nobody reads, and since the host stopped painting that hover at all there is no regression against the host default; and ui-plugin-manager gained a new consumer of the token the main-interface slider takes over (a pointer-events:none underlay behind the page header), which paints nothing at the default value but is a new row on the "who reads this token" list.
• The version gate now has its own check: npm test verifies that engines.dsh, the six peer ranges and dsh.compatibility.dsh each name every verified build and all keep their uncapped tail, and that lib/ really carries those builds and their channels — so editing src/ without re-bundling is now caught outright.
• After installing or updating, restart the host once — the compatibility gate runs when the profile is composed.

v0.4.5 (issues #35 / #36 / #38 · verified on 0.2.2-rc.2 / 0.2.2-rc.3)

• Issue #36 — the flickering dark band under the title bar is gone. With a video wallpaper, a semi-transparent title bar at blur 0 and a fully opaque chat card, Firefox (windowed GPU compositing) drew an ~18px band right under the session header that flickered with the video. Root cause: the chat card's frost underlay (backdrop-filter) sits behind an opaque card, where it is a visual no-op — but its filter surface still makes the compositor rebuild every video frame, and the sampling intermittently catches the dark title-bar strip. applyViewCards now skips the underlay entirely when the card's opacity slider is at 100% (verified pixel-identical by the reporter); translucent cards keep their frost, the trajectory view is untouched.
• Issue #38 — dsh-session-manager is registered and pinned. Its whole dialog set (.sm-panelDialog and siblings, the overlay layer hosting the header menu / custom select lists) paints through color-mix of --dsw-alias-bg-layer-1 and reads layer-2/3 directly, so the 「对话框选项面板」 slider faded it translucent with no frost of its own — its text mixed with the wallpaper and the bottom panel underneath. The new pin re-declares the three layer tokens OPAQUE on its roots (the market-popover precedent: token literal only, no frost, and the plugin's own 「弹窗不透明度」 mix keeps working over the pinned literal). The settings card now lists it as pinned; the boot log names it.
• Issue #35 ① — rotation thumbnails are click-to-apply. Until now the pool could only advance (shuffle / order / 立即切换), never land on a chosen picture. Clicking a thumbnail (hover shows an 「应用这张」 label) activates that item through the same path as a cadence advance — theme color re-extraction included — and keeps the rotation clock (lastRotate) intact, like the host's own activation path. Escape/Enter accessible, current item inert.
• Issue #35 ② — URL wallpapers can now refresh daily. After applying a wallpaper from a URL, the 背景 page shows a 「每日自动刷新」 toggle. On the day boundary (next 30 s tick, or the next launch) the host re-downloads THAT URL and re-applies it — for sources that serve a new image over time (Bing daily mirrors and the like). A static URL simply re-applies the same bytes. One attempt per day (a failure is stamped too, so a dead endpoint is not hammered every 30 s), paused while the rotation pool is enabled, cleared when the wallpaper is removed. It rides the existing fetch path (host-side download, bytes never cross the RPC).
• Verified on 0.2.2-rc.2 and 0.2.2-rc.3 (source-tree reads of both tags). Same patch line, same adapter answer, verdict exact. The one behavioral delta: design-platform.css gained darwin-only --dsw-specific-sidebar-wash-top/-bottom (+ -tint, -glass-*) painting the macOS sidebar column — the tint derives from the fill token so it already followed the slider; the two static washes joined the 「侧边栏」 opacity group (own plugin vars; toRgba now also parses the modern rgb(r g b / a) syntax they are written in), and both are inert on non-darwin hosts. conversation.hero.frame / [data-phase='hero'] mounts no [data-chat-flow], which applyViewCards already treats as "view not mounted". Gate ranges, peer enums and dshReleases now name both builds; master-only changes (DocumentStyles data-plugin/data-path pipeline, ThemePresenter style-tag observer) are recorded in the adapter for the next release.

v0.4.4 (real-host check on 0.2.2-rc.1 · issue #34 registry & reporting · issue #33 numeric input & region highlight)

• Checked 0.2.2-rc.1 on a real host. An isolated test profile under launcher homes/0.2.2-rc.1 (local plugin via link, plus dshmarket 1.73.16 / dsh-better-sidebar 0.30.1 / dsh-update-checker 1.7.3) boots dsh web: the gate admits the plugin, read answers host.version=0.2.2-rc.1 / channel=0.2.2, and the config round-trip lands on disk. A separate headless Chrome boot reports 179 style[data-plugin] sheets and all three "unregistered" log lines from issue #34, verbatim. The build now joins all four gate ranges and dshReleases; its verdict rises from line to exact.
• Adapter facts re-read: three evidence literals moved, none is a rule input. Across the tag's 98 lib/client.js artifacts, _handle{z-index:11} / _leadingSeat{z-index:15} / _overlayLayer{z-index:20}, the menu token names, 9 --dsw-menu-backdrop-filter consumers, data-shimmer / data-shell-bottom / data-rightbar-col and the session-header slot keys all still resolve. What moved: --dsw-menu-surface-fill (#f8f9fa94 / #43454a73 → #fcfdfeb3 / #303136a3), --dsw-font-family (now a single var(--dsh-font-family-text-default), still a body declaration so the font rule's !important still wins), and --dsh-dockkit-float-top is no longer emitted (this folder emits no promotion, so it is unaffected). The adapter only asks for token NAMES, so its answer stands; details live in v0-2-2/adapter.ts. Pixel-level A/B for blur / occlusion is still open.
• Issue #34: three plugins now have a verdict instead of "unregistered". Two low-risk pins were added — dshmarket's task popover (--dsw-alias-bg-layer-1) and dsh-update-checker's two buttons (--dsw-alias-bg-layer-2) — re-declaring only the token literal, never background, geometry or frost; all four selector names are 0-hit in that host's artifacts. dsh-better-sidebar is registered as reviewed, deliberately not pinned: its whole panel is exactly what the Main-interface slider is for, so pinning it would take the slider away from the user. Every pin still lives in the one -third-party dynamic sheet, so the switch removes all of it at once.
• Reporting no longer needs the console. The settings card lists each plugin, its status and its tokens, with a "Copy report line" button carrying the host release and switch state. Production builds cannot open DevTools, so the button is the whole feedback path; where the clipboard is unavailable a selectable readonly field appears.
• Issue #33, items 1 and 2. ① Slider values are typeable: every slider gained a number field, kept in sync with dragging in both directions, clamping out-of-range values and leaving an empty mid-edit alone. The original zero-lag DOM path is untouched. ② Hover highlights the matching region: hovering a module card outlines the real region it controls. The three frame columns reuse the very nodes setBlur / applyPartOpacities paint; the rest use only data-* markers and runtime tags from this plugin's own rules. No host node is written and no third-party z-index is touched — a single fixed, pointer-events:none outline layer is removed on mouse-out and on leaving the settings page. Positions update from capture-phase scroll / resize, never rAF. The hint reuses the plugin's own scheme resolver rScheme() (forced override > theme-color lightness > wallpaper brightness verdict) and paints its inverse: a translucent WHITE plate on a dark interface, a translucent BLACK plate on a light one, with the tag inverted the same way. Strictly neutral black/white — not --dsw-alias-brand-primary (extracted from the wallpaper, so it collides after a theme-color change) and not a fixed accent (which collides with a wallpaper of that same color). The plate breathes slowly and continuously (2.4s ease-in-out, fill opacity 22% ↔ 100% — not a one-shot flash); only the fill pseudo-element animates, so the two non-overlapping dashed rings (near-white border + near-black outline) and the tag stay steady. prefers-reduced-motion falls back to a static plate, and nested targets collapse to the outermost box so alpha never stacks. Measured luminance delta: white-on-dark 0.243 / black-on-light 0.240, versus 0.015 / 0 if the direction is chosen wrongly; on an amber wallpaper the white / black plates still give 0.067 / 0.178. When a region is absent on the current page the card says so rather than drawing a guessed box — the honest answer to "some surfaces only exist once a conversation is open". The other three requests (per-module annotations, a post-turn token-usage module, a model-picker submenu) need per-surface structural probing and are NOT in this release.
• After installing or updating, restart the host once — the compatibility gate runs when the profile is composed.

Installation

Method 1: npm install (Recommended)

# published on the npm registry
dsh plugin --profile web add dsh-any-background

# or straight from the GitHub repository
dsh plugin --profile web add github:Tkingxiao/dsh-any-background

Then launch:

dsh web

The plugin appears as a "Theme" section in Settings.

Method 2: npx (No Global Install)

npx @deepseek-ai/dsh plugin --profile web add dsh-any-background
npx @deepseek-ai/dsh web

Method 3: Local Build (Development)

The lib/ directory is committed, so installs need no build step. To rebuild after editing src/:

git clone https://github.com/Tkingxiao/dsh-any-background.git
cd dsh-any-background
pnpm install
pnpm run bundle
pnpm dsh plugin --profile web add "dsh-any-background"
pnpm dsh web

Compatibility

• dsh web: 0.2.0-rc.1 ~ 0.2.2-rc.3, and everything above it. The gate names each build that was checked and then closes with an uncapped >=0.2.0-rc.1. That umbrella is deliberate: the host enforces exactly this peer list — a release it does not name is disabled before a single module is imported — so a range that runs out is a wall in front of a plugin that would have kept working. (More precisely: the host's app-boot unmetRequirements reads engines.dsh alone when that field is present and ignores peerDependencies, so all four places must say the same thing but engines.dsh is what actually decides whether the plugin loads.)

• How an unseen build runs: it gets the closest verified set of facts plus a log line saying how far from exact that is. The worst a stale fact can cost is one slider no longer fading a surface the host has since moved; a version check that failed closed would cost the whole plugin.

• Verified builds (dsh.compatibility.dshReleases):

  Host build	Facts folder	Notes
  0.2.0-rc.1	v0-2-0-rc-1	verified by diffing its tag, package by package
  0.2.0-rc.2	v0-2-0-rc-2	same; this rc renamed the token a sticky menu group heading paints from, so it opened its own facts
  0.2.1-alpha.1 ~ 0.2.1-rc.5	v0-2-1	facts unchanged, folded into one folder; every checked build gets its own row with an exact verdict. rc.4 and rc.5 ship artifacts byte-identical to rc.3, file by file
  0.2.2-alpha.2	v0-2-2	a new patch line, so its own facts folder; every claim re-read and still true (z-index ladder, menu frost tokens, font token composition, header slot keys, 75 host selectors matching)
  0.2.2-rc.1	v0-2-2	checked on a real host: gate / RPC / boot self-check all pass; every rule input still hits across 98 artifacts, three moved evidence literals recorded in the adapter; exact verdict
  0.2.2-rc.2 / 0.2.2-rc.3	v0-2-2	re-read from both tags' source: same line, same answer; the one behavioral delta — darwin-only sidebar wash tokens — joined the 「侧边栏」 slider group and is inert elsewhere; verdict exact
  above 0.2.2-rc.3	reuses the closest row	an unverified build takes that line's adapter, stated in the log

• Facts are isolated per release: the host release is resolved on the Node half and handed down through the read RPC; styling and logic only ask the adapter questions (who owns this surface, which layer carries the frost, which token fades a menu) and never compare version strings. Supporting a new host means adding one version folder and registering it.

• A restart is still needed after installing or updating the plugin: the compatibility check runs while the profile is composed, not when the plugin is updated. Features that depend on a specific host structure (the right sidebar's panel blur, the official sidebar's "Theme" card) enable themselves only where that structure exists; everything else behaves identically across the range.

• The 0.1.5 / 0.1.6 / 0.1.7 era is out of the supported range: those fact folders assert things nothing re-checks any more, and a table nobody verifies is worse than no table. An older host is now refused at composition rather than quietly restyled by the wrong adapter.

• DSHA — the DeepSeek Harness Android launcher (ROOT-free, Termux-free). Its bundled dsh is 0.1.5-rc.2, below this plugin's supported floor: the peer gate refuses it at composition, so the plugin never loads there.

• deepseek-harness-desktop — supported. Windows-only behavior (the caption band, the native window controls) applies on the desktop shell only.

Permissions, side effects & boundaries

• Integration form: an official Profile Bundle — package.json declares dsh.bundle.patch: ./cordis.patch.yml (a loader insert layer) and the repository ships ready-to-use prebuilt artifacts (lib/index.js, lib/client.js). No install scripts, no postinstall, no native binaries, no build step at install time.
• Filesystem: the server half reads and writes only inside <dsh home>/.dsh-any-background-data/ (config, wallpaper, rotation pool, video, font) and touches nothing outside it; config writes are atomic (temp file + rename). These files live on the real disk, so they are outside generation restore — it neither captures nor rolls them back; deleting the directory is a full plugin reset.
• Network: exactly one outbound fetch, and only when the user pastes an http/https image or video URL and presses Apply. No telemetry, no other external calls.
• Shell / native: none. No child_process, no native modules, no dynamically downloaded binaries.
• HTTP surface: only /dsh-any-background/{video,wallpaper,font} (GET/HEAD streaming) with the matching */upload POST routes (100 MB cap), plus the dedicated RPC channel /dsh-any-background, all under the local dsh web server. No extra listening ports.
• Restart required: the first install needs a (re)start of dsh web to load the client bundle; settings changes afterwards apply live and persist automatically. Changing plugin version requires a restart to pick up the new lib/client.js.
• Tests & verification: pnpm run typecheck (full tsc check), pnpm run bundle (tsdown emits lib/), and npm test, which starts the real host half and round-trips config writes, reads and profiles plus the upload fence. Visual changes go through two further paths: a local mock page that measures computed values, and real dsh web testing slider by slider.
• Known limitations:
  • The styling relies on stable host DOM markers (such as [data-sidebar-right-panel]) and CSS token names. A host restyle of those layers can leave a slider ineffective for its surface — cosmetic only, nothing breaks. The version-specific half of those selectors lives inside its own version folder, so a host revision normally means editing that one file.
  • -webkit-text-stroke may clip about 1px at the edge of some single-line ellipsis containers.
  • One rule is a deliberate cross-plugin accommodation: dsh-better-display paints its sticky reading lanes from the token our 「主界面」 opacity owns, so when that plugin is detected its lanes are pinned at a 20% plate + 30px frost outside the sliders. If it ever renames those markers the rule stops matching and its lanes go back to being painted its own way.

Star History

License

MIT