Aqua restyles the DSH web UI as frosted glass, and its author has stopped

The author stopped updating the plugin when DSH changed its API

The first thing on the page is a notice, and it changes how everything else should be read. Because DSH has been updated, the author says he cannot promptly update the plugin with the new API, and gives the reason as academic commitments. The request to readers is blunt: use an alternative agent to replace or repair the plugin yourself, so you do not hit crashes when installing it. The dates back that up. The three most recent releases, v1.3.0, v1.2.1 and v1.2.0, all landed on 2026-08-16, and the last push to the default branch, main, is 2026-08-22. The package metadata explains the mechanism of the risk: the peer dependencies are DSH client packages pinned at `^0.1.0-rc.5`, release candidate versions, so anything that moved past those candidates is outside what this plugin was built against.

Mica restyles the layout while Compatibility Mode only swaps material

The theme has two modes and the difference between them is ownership of the layout. Mica restyles the layout into floating glass cards, with blur and frost adjustable. Compatibility Mode keeps the stock layout byte-for-byte and only swaps the material to generic glass. The stated advantage of the second mode is that other plugins' UI gets the same treatment automatically, so a plugin that injects its own components does not end up half themed. What is restyled in either case is the same set of surfaces: the header, sidebar, composer, stats line and trajectory view all become panes of frosted glass. Picking Mica means accepting a different arrangement of those surfaces, not just different paint on them, which is the tradeoff for anyone whose muscle memory depends on where things sit.

One master switch in settings hides every other control

Aqua is on by default once it is installed. The master switch lives in Settings, then Plugins, then Glass theme, and it follows the same shape as the other plugin cards. Every other control sits under Settings, then General, then Appearance, which has no title of its own. The controls in that block are mode, blur and frost for Mica mode, fluid color, background brightness, the backdrop choice between fluid and wallpaper with its wallpaper controls, and the particle-whale toggle. With the master switch off, the entire control block under Appearance is hidden rather than greyed out, and off restores the stock UI exactly with every effect removed along with the plugin. That arrangement means a user who dislikes the theme loses the settings surface too, not just the styling.

Fluid board or wallpaper, and a brightness dial that flips per scheme

The backdrop has two sources. One is a living fluid board whose hue is adjustable. The other is your own wallpaper, which fills the page with its aspect ratio preserved and carries its own blur and frost settings, independent of the Mica card settings. The page also gives one piece of advice about pairing: light wallpapers look best in light mode, dark wallpapers in dark mode. Background brightness is a single dial that behaves differently depending on the resolved color scheme. In dark mode it darkens, over the range from 0 to 50. In light mode it brightens, over the range from 50 to 100. The value 50 leaves the background unchanged. So the same slider is a dimmer in one scheme and a lifter in the other, and a number copied between schemes means two different pictures.

Particle whale, gradient nameplate and 5px edge fades

Three pieces of the theme are decoration rather than layout. The particle whale is a 2D port of the particle engine fish that sits at the center of the deepseek.com harness page, placed in the chat area to the right of the sidebar, white on dark and gray on light, with a toggle in settings. The glossy Harness badge is a sidebar wordmark treatment: in dark mode it wears the official nameplate pill with a 135 degree gradient ring and a soft glow, while light mode keeps the stock plate. The edge fades are 5px gradient blur bands pinned to the top and bottom of the page, above the chat content, so scrolling content appears to melt into the edges, with a faint white veil in light mode and faint black in dark. None of the three is described as configurable beyond the whale toggle, so the other two are fixed values in the theme.

The npm one-liner registers a dsh.bundle patch layer

The recommended install is one command:

dsh plugin --profile web add dsh-client-ui-aqua

It installs the latest version from npm and registers the plugin as a profile plugin layer, described as a `dsh.bundle` patch, and the page claims this works on every platform. Reloading the web UI is all that is needed afterward. The published artifact is `@deepseek-ai/dsh-client-ui-aqua`, published with public access, and its metadata has two details worth knowing before you rely on it. The declared license in `package.json` is MIT while the repository itself is recorded as AGPL-3.0. The `repository` url in the package points at `git+https://github.com/WYH66666666/DSH.git`, which is a different repository from the one this plugin is developed in. The package injects six DSH client packages and declares its platform as web. Its entry point is `lib/index.js` with types beside it in `lib/types/index.d.ts`, and the export map exposes three named entries, `.`, `./invariant` and `./client`, plus a passthrough for `./src/*`.

install.ps1 pins a version and is safe to rerun

The fallback route needs no npm account and no git, and it falls back to a plain zip download. On Windows it is a single command:

powershell -ExecutionPolicy Bypass -Command "Invoke-WebRequest 'https://github.com/WYH66666666/DSH-Transparent-UI-Plugin/raw/main/install.ps1' -OutFile install.ps1; .\install.ps1"

That script installs the latest release by default. It links the plugin into the profile's `node_modules` and registers `ui-aqua` in `cordis.patch.yml`, and the page notes that it is idempotent, so running it again is safe. Versions can be pinned or the development branch tracked:

.\install.ps1 -Version 'v1.1.0'   # a specific release
.\install.ps1 -Version 'main'     # the development branch

The idempotence claim matters more than it looks, because it is what makes a repaired install repeatable after you fix the API drift yourself.

macOS and Linux need a symlink plus a YAML insert

The unix route is manual and takes three steps. Clone the repository at a branch or tag, link the result into the profile, then patch the file that registers plugin layers:

git clone --depth 1 --branch v1.1.0 https://github.com/WYH66666666/DSH-Transparent-UI-Plugin.git
ln -s "$PWD/DSH" "$DSH_HOME/profiles/node_modules/@deepseek-ai/dsh-client-ui-aqua"

- insert:
    - id: ui-aqua
      name: '@deepseek-ai/dsh-client-ui-aqua'

The clone command as written assumes the checkout directory is named `DSH`, which the symlink line depends on, so a different clone directory name has to be adjusted there. The YAML block is appended to `$DSH_HOME/profiles/web/cordis.patch.yml`. The id `ui-aqua` here is the same identifier the Windows script writes, so the two routes converge on one registration record. Building from a clone uses the two scripts in `package.json`, `bundle` and `watch`, both driven by tsdown with `tsdown.config.ts` beside them. The rest of the tree is small and conventional for a published plugin: `src/` and `lib/` for sources and output, `assets/` for the images the whale and badge need, `build.ps1` and `publish.ps1` as the PowerShell counterparts of the install script, `cordis.patch.yml` for the registration record, a `CHANGELOG.md`, and a `README.zh.md` alongside the English page.

Editorial conclusion

Aqua suits someone who wants a different look on the DSH web surface and is willing to repair the plugin themselves, since it installs as a patch layer and its effects come back exactly when the switch goes off. It does not suit a team that needs a maintained integration against the current DSH client packages, because the author has said updates stopped and the package pins release-candidate client versions. Before installing, check what your DSH build expects, and be ready to hand the repair to another agent as the notice suggests.

Frequently asked questions

Official sources

1. Issues
2. License: AGPL-3.0
3. README
4. Releases
5. WYH66666666/DSH-Transparent-UI-Plugin on GitHub