47f943859bef, package version 0.1.0-rc.5.Quick answer
DeepSeek Harness already has an official Web UI, so a custom theme is a client plugin rather than an Appearance option. Inspect the bundle, add it to one named profile with the official plugin command, verify it in the profile configuration and the live UI, then remove the plugin and restart to get the default tokens back.
DeepSeek Harness already has a Web UI
A common claim in community posts is that DeepSeek Harness has no graphical interface. That is incorrect. The official README starts a browser Web UI, served on a local address by default, and the official user guide configures models, selects a workspace, and runs agent tasks inside it. The built-in Appearance preference offers light, dark, and system. What the project does not provide is a durable list of third-party color themes, which is why custom themes arrive as plugins instead of settings entries.
Know what a third-party theme actually is here
The official client theme runtime exposes token overrides that must supply both a light and a dark value for each semantic token; a bare color string is rejected. A third-party theme is therefore an in-process extension: while the client plugin is loaded, its override layer sits on top of the default tokens, and the disposer returned by the override call restores the previous layer when the plugin unloads. A custom theme never appears in the built-in Appearance preference, and it does not modify the DeepSeek Harness source tree when installed through the documented plugin flow.
Safety pre-check: prefer prebuilt, readable files
The official publishing guide warns that a git dependency with a prepare script executes build code at install time. A prebuilt bundle of plain JavaScript avoids granting that permission. Before installing any theme, read every file. A theme needs only the injected theme service and its token table; it has no reason to open a network connection, read files or storage, spawn a shell, ship a minified blob, or ask for API keys, provider settings, or credentials. A ZIP downloaded from a website is inert data until you run a command yourself, and no website can install it for you.
Install into one named profile
Extract the archive so a single root folder holds package.json, the patch declaration, the host entry, the client entry, the README, and the license. Then add it with the official plugin command for the profile you intend to change, pointing at the absolute path of that folder: dsh plugin --profile <name> add /absolute/path/to/<theme-folder>. Use a profile you can afford to break while the upstream project is a developer preview, and record the exact commit and package version you installed against.
Verify the theme with two independent checks
First, run dsh --profile <name> --dump-config and confirm the bundle layer and plugin row are listed rather than silently skipped. Second, start or reload that profile's Web UI and compare the live surfaces against the token values you chose: page background, raised panels, overlay surfaces, both borders, brand color, primary and secondary text, the error, success, and warning states, and the sidebar fill. The official theme runtime can also export its inspectable token values. Do not treat one screenshot as verification; check primary and secondary text on the base surface, both raised layers, and the sidebar, because a palette can look correct in a heading and fail on compact metadata.
Remove the theme and restore the default appearance
Remove the plugin from the same profile with the official plugin removal command, then restart the Web UI process so no stale client bundle remains loaded. Because the override layer is disposed when the plugin unloads, the default token values return on their own; there is no separate uninstaller and no leftover theme state to clean up. Appearance continues to control light, dark, and system exactly as it did before. Delete the extracted folder only after you are sure you no longer need to inspect it.
Community Electron shells inherit the plugin you already installed
Several unofficial desktop shells wrap the official DeepSeek Harness Web UI in an Electron window. Because they load the same Web UI, an override layer installed as an official client plugin appears inside them without any second theme format: there is nothing extra to generate, copy, or patch. Those shells are community projects rather than DeepSeek releases, they can change or stop tracking upstream at any time, and their own window chrome is not part of the official token contract. Install and verify the plugin against the official Web UI first, and treat a wrapper as an additional place the same theme happens to render.
When an upstream change breaks the theme
DeepSeek Harness is explicitly a developer preview and warns that compatibility-breaking changes will occur. A theme built for one commit can stop applying, apply partially, or apply to renamed tokens after an update. Diagnose in this order: confirm the stock Web UI works without the plugin, confirm the plugin is still listed in the profile configuration, then compare the current semantic token names against the ones in your bundle. Re-verify against the new commit instead of forcing an old bundle to load, and never patch the upstream source tree to make a visual layer stick.
Completion checklist
- Official Web UI runs before the theme is added
- Every bundle file was read, with no network, storage, or shell access
- Plugin was added to one named profile by absolute path
- Profile configuration lists the plugin
- Primary and secondary text pass on base, both layers, and the sidebar
- Removal plus a restart returns the default appearance
Frequently asked questions
Does DeepSeek Harness have a Web UI already?
Yes. The official README starts a local browser Web UI and the official user guide runs agent tasks inside it, with a built-in light, dark, and system Appearance preference. Custom color themes are a separate plugin layer.
Can I select a custom theme in Appearance settings?
No. The durable built-in preference lists only light, dark, and system. A third-party theme is an in-process override that is active while its client plugin is loaded, so you enable it by installing the plugin and disable it by removing or unloading the plugin.
Is installing a custom DSH theme safe?
It depends on the bundle. Prefer a prebuilt bundle of readable JavaScript with no install-time build script, and reject anything that requests network access, storage, shell execution, credentials, or provider settings. Reading the files before running the plugin command is the actual safety step.
How do I fully restore the default appearance?
Remove the plugin from the profile you installed it into, restart the Web UI process, and confirm the default token values are back. The override layer is disposed on unload, so nothing else needs cleaning up.