DeepSeek Harness Plugin Hub

Publish and manage complete Harness Profiles. Discover Plugins for your next setup.

Explore

PluginsPresetsDocsNews

Community

Publish a pluginContactReport an issue

Resources

Plugin Hub on GitHubDeepSeek HarnessSystem statusPrivacy notice
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

Independent and unofficial. Not affiliated with, authorized by, or endorsed by DeepSeek.

Theme Brick — DSH Plugin for DeepSeek Harness
DeepSeek Harness Plugin Hub
ProfilesPluginsCategoriesNewsDocsSign inManage Profiles
ProfilesPluginsCategoriesNewsDocsSign in
← Plugins
T

dsh-theme-brick

Theme Brick

Brick — a restrained, token-only theme layer for DeepSeek Harness Web. Warm plaster neutrals, mortar hairlines, one fired-clay accent, and a Settings on/off switch. 一切皆插件,每一块砖都可承重。

The plugin will be installed here. Keep web if you are unsure.

npx -y @deepseek-ai/dsh plugin --profile web add github:ShanHaiFish/dsh-theme-brick#1d660510103f0f98167a2c82148c7d8f2456f6b7
READMECompatibilityVersions

Compatibility and provenance

Theme Brick is published as dsh-theme-brick and currently resolves to version 0.2.1. The Hub verifies its manifest and preserves the exact installation source for reproducible installs.

DSH compatibility
*
Runtime surfaces
web
Release source
github
Registry updated
8/30/2026

Versions

0.2.1stable
8/30/2026

Related plugins

Loading related plugins…

Latest
0.2.1
DSH
*
HMR
Process restart
Tree shaking
Safe tree shaking not declared
Unpacked size
Unavailable
Files
Unavailable
Surface
web
License
MIT
Source
github
GitHub
★ 0
Weekly downloads
0
Last push
8/30/2026
View source ↗
README badge

Click the badge to copy Markdown for your README.

Do you maintain this Plugin?Claim benefit · Priority security scan

Verify the GitHub repository declared in package.json to manage this listing. After you claim it, Hub will prioritize a security scan of the current version and publish the result when it passes.

Claim this Plugin →
Report an issue

Related plugins

More verified plugins in ui-customization.

Remote Web Ui@linxin666/dsh-remote-web-uiScan-to-pair remote access for the dsh web GUI that shares one official interface: a QR beside the settings button pairs phones and PCs into the same Web GUI (a portrait-touch adaptation layer for phones, full desktop on PCs) through one-time tokens and rClient Ui Task Board@linxin666/dsh-client-ui-task-boardHost-authoritative task board for the DSH Web GUI with real session execution, Host cron scheduling, and optional cross-platform idle-sleep protection; mounted without DSH source changes.Client Ui Git Graph@linxin666/dsh-client-ui-git-graphExternal dsh web GUI plugin: a blank-session git branch selector + Git graph, with real host-side git operations and guards, as a dsh profile bundlePet@linxin666/dsh-petMulti-pet companion plugin for the dsh web GUI: a registry-driven floating pet that reacts to model activity, with per-pet naming, petting/feeding interactions and an affinity score

README

dsh-theme-brick · 砌砖 / Brick

一切皆插件,每一块砖都可承重。Every plugin is a brick: load-bearing, replaceable, honest.

A restrained, token-only theme layer for DeepSeek Harness Web — warm plaster neutrals, mortar hairlines, one fired-clay accent, and a Settings on/off switch.


Why Brick

The folder name says it: bricks. DSH's architecture is plugs-within-plugs, a wall of bricks — each unit load-bearing and interchangeable. So the theme follows masonry, not decoration:

  • 面是材料 — surfaces read as limewashed plaster / paper / kiln clay, not glowing glass.
  • 缝是灰缝 — borders are honest, even mortar hairlines with a warm undertone.
  • 一砖一色 — a single fired-clay / ember accent, carried through the exact channels the product itself uses for its brand blue.
  • 克制是纪律 — one theme.overrideTokens() call. No DOM hacking, no global CSS, no animation, no new chrome.

Design rationale: DESIGN.md · phase plans: PLAN-PHASE2-LAYOUT.md

Features

  • 84 live tokens (verified defined + consumed, zero-dead gate) across five phases.
  • Warm palette, both modes — light = plaster & paper, dark = kiln & embers.
  • Settings → General on/off switch for statically installed bundles: toggle the theme off without uninstalling; state persists in localStorage.
  • Composes with any other plugin via token layers; removing restores exactly what was covered.
  • No global CSS — the switch is drawn entirely with theme CSS variables (auto-adapts to light/dark).

Install

As a dsh bundle (recommended)

# From a published release / registry:
dsh plugin --profile web add dsh-theme-brick

# Or from this repository (Windows note: a path with spaces breaks through the
# dsh.ps1 shim — put it on a space-free path first; a junction copies nothing):
#   New-Item -ItemType Junction -Path $HOME\.dsh\plugins-dev\dsh-theme-brick -Target <repo path>
dsh plugin --profile web add "file:C:/Users/<you>/.dsh/plugins-dev/dsh-theme-brick"

dsh --profile web --dump-config   # confirm the `brick` loader entry is composed
dsh web                           # restart to activate (bundle layers compose at boot)

The plugin loads and applies on boot (default on). Open Settings → General → Brick 主题 to toggle it off (restores the default look) or on; the choice persists across reloads. To fully uninstall: dsh plugin --profile web remove dsh-theme-brick.

Golden triangle for a dsh bundle: the npm name, the patch layer name, and the client.js __ModuleLoader__.load({ id }) must all be equal. This package satisfies it (dsh-theme-brick everywhere). See the dsh plugin install guide.

Developing locally

node scripts/build.mjs          # src/client.js -> lib/client.js (__ModuleLoader__ bundle)
node scripts/verify-plugin.mjs  # materialize + token gate + on/off switch logic tests
node --check lib/client.js

Package layout

lib/client.js         browser half (bundle; served at /plugins/dsh-theme-brick/client.js)
lib/index.js          host half (no-op loader entry)
src/client.js         readable source of truth (token map + switch); build transpiles it
cordis.patch.yml      profile patch — injects the `brick` loader entry
DESIGN.md             design rationale (philosophy, palette, token map, compatibility)
PLAN-PHASE*.md        phase-by-phase plans
scripts/*             build + verification tooling

Contributing

PRs welcome. Design decisions are recorded in DESIGN.md and the phase plans — please read them before changing tokens. Road rules: override only tokens actually consumed by the product (the scripts/sweep-tokens.mjs gate enforces it); keep every change composable and reversible; add a regression check to scripts/verify-plugin.mjs when behavior changes; and respect restraint — no DOM hacking, no global CSS selectors, no decorative animation.

License

MIT © ShanHaiFish