MIT native DSH plugin bundling free oil-ui with five design tools (explorer, shoot, media, image, skill status) and slash shortcuts for status, explore, and review.
DSH integration
Native runtime
Author-claimed
Safety audit
Unaudited
Last verified
2026-11-18
License
MIT
01What can it help you accomplish?
Compare three distinct UI directions before locking a visual style in DeepSeek Harness
Three first-screen candidates under `explore/` and a single-file `style-explorer.html` comparison page in the current directory
Developers and designers who run DSH and want agent-led UI exploration without an extra nested project sandbox
Implement and iterate full pages with real browser screenshots inside DSH
`index.html` or multi-screen layouts plus captures, interaction checks, and layout diagnostics from `oil_ui_shoot`
Teams shipping landing pages or product UI who need viewport-faithful review loops in the same cwd as native `read` / `write`
Use bundled Lite oil-ui while detecting locally installed Oil UI Pro
Built-in free `oil-ui` Skill plus diagnostics when a separate `oil-ui-pro` install is visible to Harness
DSH users who may add Oil UI Pro for deeper visual review but want the plugin to stay a single publisher for bundled Lite
02How to install into DeepSeek Harness
Prerequisites
- DeepSeek Harness within the plugin range `>=0.2.1-rc.2 <0.3.0-0` (not a guarantee for all future prereleases)
- Node version required by your DSH build (README notes DSH `0.2.2-rc.1` needs Node `>=24.9.0`; DSH Desktop uses its bundled runtime)
- Local Chrome / Chromium for `oil_ui_shoot`; `ffmpeg` when using `record` or `motion` capture
Installation steps
- 01
Confirm `node --version` and `dsh --version` in the terminal or app you will actually use, and note whether you target `web`, `headless`, or DSH Desktop (they use separate profile data).
$ dsh --version
- 02
For the Web UI (`web` profile), run `npm exec --yes --package=pnpm@10.16.1 -- dsh plugin --profile web add github:oil-oil/dsh-oil-ui`. On Desktop, add `github:oil-oil/dsh-oil-ui` under Settings → Plugins instead of using `--profile desktop` in the shell.
$ npm exec --yes --package=pnpm@10.16.1 -- dsh plugin --profile web add github:oil-oil/dsh-oil-ui
- 03
If Git reports the plugin as already installed but an old version persists, run `npm exec --yes --package=pnpm@10.16.1 -- dsh plugin --profile web remove dsh-oil-ui`, then add again with the target Release commit or a official `.tgz`.
$ npm exec --yes --package=pnpm@10.16.1 -- dsh plugin --profile web remove dsh-oil-ui
- 04
Restart the same profile you installed into, then have the Agent call `oil_ui_skill_status` and load the returned `activeSkillName` with the native `skill` tool.
Verify the integration
- After restart, call `oil_ui_skill_status` and expect `skillReady=true`, then load `activeSkillName` with the native `skill` tool; five tools present but skill load errors still count as failure.
Rollback
- Remove `dsh-oil-ui` from Settings → Plugins (Desktop or Web UI), or run `npm exec --yes --package=pnpm@10.16.1 -- dsh plugin --profile web remove dsh-oil-ui` for the CLI profile you used, before reinstalling.
03DSH integration and capability boundaries
Native DeepSeek Harness plugin: add with `dsh plugin`, register five oil-ui tools and oil-ui slash commands, and bundle the public oil-ui Skill against the current working directory.
Skill status and updates
Optional `{"update": true}` on `oil_ui_skill_status` or `/oil-ui-status`→Active skill name, image source, balances, and version update notices
May query `https://ui.oiloil.org/api/store/versions` about every ten minutes and cache under `~/.local/state/oil/`May update filesystem-installed Lite/Pro via oil-cli when explicitly requestedStyle explorer pack
`explore/manifest.json` and candidate HTML under `explore/`→Interactive `style-explorer.html` comparison page
Reads and writes files under the current working directoryBrowser shoot and review
Local page paths or URLs plus viewport, states, steps, or stitch options→Screenshots, interaction traces, console and layout checks
Launches local Chrome / Chromium or Playwright ChromiumMay invoke `ffmpeg` when recording motionPublic-domain media search
Search terms for images, video, or map assets→Preview and download paths for museum and open collections
Network access to public catalog APIs listed in the READMEAI image generate and edit
Prompts and resolution options for `oil_ui_image`→Saved image files on disk with returned paths
Prefers local `image-gen` via `python3` when availableMay call oiloil APIs using `OIL_TOKEN` or `~/.config/oil/config.json` credentials
04Who is it for? When not to use it?
Good for
- Developers and designers who run DSH and want agent-led UI exploration without an extra nested project sandbox
- Teams shipping landing pages or product UI who need viewport-faithful review loops in the same cwd as native `read` / `write`
- DSH users who may add Oil UI Pro for deeper visual review but want the plugin to stay a single publisher for bundled Lite
Not for
- The plugin declares DSH compatibility `>=0.2.1-rc.2 <0.3.0-0`; README warns that repeating `add` on a Git URL does not replace an old lockfile—remove first or install from a Release `.tgz`.
- DSH Desktop uses a separate `DSH_HOME` and `profiles/web` path from terminal `dsh web`; install and restart must target the same profile and do not use `--profile desktop` in the shell per README.
- `oil_ui_skill_status` may call `https://ui.oiloil.org/api/store/versions` (cached, eight-second timeout); `oil_ui_image` may reach oiloil at `https://api.oiloil.org` when local `image-gen` is absent.
- All five tools use the current working directory for pages, screenshots, and manifests; browser tools need local Chrome/Chromium and optional `ffmpeg`.
05Compatibility, maintenance and safety notes
- The plugin declares DSH compatibility `>=0.2.1-rc.2 <0.3.0-0`; README warns that repeating `add` on a Git URL does not replace an old lockfile—remove first or install from a Release `.tgz`.
- DSH Desktop uses a separate `DSH_HOME` and `profiles/web` path from terminal `dsh web`; install and restart must target the same profile and do not use `--profile desktop` in the shell per README.
- `oil_ui_skill_status` may call `https://ui.oiloil.org/api/store/versions` (cached, eight-second timeout); `oil_ui_image` may reach oiloil at `https://api.oiloil.org` when local `image-gen` is absent.
- All five tools use the current working directory for pages, screenshots, and manifests; browser tools need local Chrome/Chromium and optional `ffmpeg`.
MIT · last push 2026-11-11 · release v0.4.13
06Frequently asked questions
Which DeepSeek Harness versions does the README pair with this plugin?
The plugin declares DSH `>=0.2.1-rc.2 <0.3.0-0`, and the README ties Node requirements to specific DSH builds—for example DSH `0.2.2-rc.1` expects Node `>=24.9.0`. Desktop ships its own runtime; match versions instead of using `allow-version --accept-risk` to bypass checks.
Web CLI install versus DSH Desktop—do they share one plugin folder?
No. Desktop installs into its own `DSH_HOME` under `profiles/web`, while terminal `dsh web` uses `~/.dsh/profiles/web`. Install and restart the profile you actually run; the README says not to use `--profile desktop` from the shell.
How do I know the plugin loaded, not just that `dsh plugin add` exited 0?
After restart, have the Agent call `oil_ui_skill_status` and expect `skillReady=true`, then load `activeSkillName` with the native `skill` tool. The README states five tools alone are not enough if skill loading errors remain.
What is the difference between built-in Lite oil-ui and Oil UI Pro?
The plugin bundles free `oil-ui` for direction exploration and `style-explorer.html`. Oil UI Pro adds deeper visual review, richer shoot states, full media/image playbooks, and scenario skills when you install it separately; the plugin discovers Pro locally but does not publish Pro itself.
What local or network access should I expect?
`oil_ui_shoot` needs Chrome/Chromium (and `ffmpeg` for some capture modes) and writes under your cwd. Optional oiloil calls for `oil_ui_image` use `OIL_TOKEN` or oil config, and version checks may hit `https://ui.oiloil.org/api/store/versions` with cached results.
07Related DSH workflows
dsh-tui
by ccch1mneyyy
Claude Code 风格全屏终端 TUI:像素鲸鱼顶栏、双流光大字、实时工作状态行、思考流式展开、双击 Esc 时间回溯、上下文进度条 + TPS 仪表;接入 Agent preset(standard/code/minimal/cordis)、Skills、MCP、Goals、Todos、子代理,/ 命令注册表与随附技能(audit/bug/review/practice/pr_comments/release-notes/vuln-check);纯插件挂载零核心改动。
dsh-better-sidebar
by omdsh-dev
Full sidebar workbench with file rendering and editing, terminal, Git, and subagents; third-party plugins can register new tabs.
dsh-media-desk
by woniuniuniu
Capture ideas and generate scripts, titles, covers, images, storyboards, schedules, and review data in a sidebar media workspace.
dsh-drawai
by fourzkw
Create diagram artifacts and use Draw.io-oriented tools from a DSH profile.
08Data and sources
**`dsh-oil-ui` 是 [oil-ui](https://github.com/oil-oil/oil-ui) 的 DeepSeek Harness 原生插件。**
`dsh-oil-ui` 直接按 DeepSeek Harness 的原生插件机制设计:
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-11-18. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.
