dsh-web-all
zhu1090093659
Plugin and skin collection for the DSH Web UI: task board, Git graph, right-side panel, remote mobile UI, pet, live token stats, and a skin center.
Installed cleanly when we ran it
ccch1mneyyy/dsh-TUI
Claude Code-style full-screen terminal UI: pixel-whale header, live status line, and streaming thought expansion.
Install
via npm
Resolves a published tarball rather than cloning the repository, and installs without any extra setup. Swap `web` for your profile name if you run another one.
via GitHub · npm package
Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/web/pnpm-workspace.yaml.
The desktop app keeps its own profile, desktop, and only the dsh command it ships may change it — the npm-installed dsh refuses that profile. Install the command from the app menu (Manage dsh Command…), open Desktop once, quit it fully, run the line below, then reopen Desktop.
via npm
Resolves a published tarball rather than cloning the repository.
via GitHub · npm package
Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/desktop/pnpm-workspace.yaml.
Our install check ran in a web profile on npm's dsh, not in the desktop app.
What happened when we ran it
DeepSeek Harness 0.2.2-rc.1 refuses the latest release
From 0.2 DeepSeek Harness checks a plugin's dsh range before installing anything, and refuses the whole command when the running version is outside it. The latest release asks for ^0.1.0-rc.6 || ^0.1.1-rc.1 || 0.1.2-alpha.3 || 0.1.2-alpha.4 || 0.1.2-alpha.5 || 0.1.2-rc.1 || 0.1.3-alpha.2 || 0.1.5-alpha.1 || 0.1.5-alpha.2 || 0.1.5-rc.1 || 0.1.7-rc.1 || 0.1.7-rc.2 || 0.2.0-rc.1 || 0.2.0-rc.2 || 0.2.1-rc.2 || 0.2.1-rc.3 || 0.2.1-rc.4 || 0.2.1-rc.5, 0.2.0-rc.2 || 0.2.1-rc.2 || 0.2.1-rc.3 || 0.2.1-rc.4 || 0.2.1-rc.5, 0.2.0-rc.1 || 0.2.0-rc.2 || 0.2.1-rc.2 || 0.2.1-rc.3 || 0.2.1-rc.4 || 0.2.1-rc.5, 0.1.7-rc.1 || 0.1.7-rc.2 || 0.2.0-rc.1 || 0.2.0-rc.2 || 0.2.1-rc.2 || 0.2.1-rc.3 || 0.2.1-rc.4 || 0.2.1-rc.5; we ran 0.2.2-rc.1.
No release of it accepts DeepSeek Harness 0.2.2-rc.1 yet. `dsh plugin allow-version … --accept-risk` forces one in, at the risk the harness itself warns about; otherwise wait for an update.
Why DeepSeek Harness refuses plugins, and every way around it ›
Every command here is run in a throwaway container against a clean profile, and the result is whatever the harness recorded — not a guess from the source. Last run 11d agoon DeepSeek Harness 0.2.2-rc.1.
Due diligence
Security
Not measured — DSH refused the latest release before running anything.
Source: our sandbox install on DeepSeek Harness 0.2.2-rc.1, 11d ago.
package.json declares no preinstall, install or postinstall script.
Source: package.json on GitHub, read at our last sync. prepare is not recorded; it runs only on a GitHub install, and shows up under build scripts when pnpm blocks it.
shell commands (bash, exec, spawn …)
Source: a keyword match on the README — a hint about what the plugin touches, not an analysis of its code.
Not an audit. These are the record of one install and two text scans; nobody has read this plugin's code on your behalf. Plugins run with your agent's permissions.
What it is — A full-screen terminal canvas around a DeepSeek Harness session, with thought tokens, job state, and context fill on one view.
Who it is for — You sit in a local terminal driving DSH through repo edits and tool calls, and you need TPS, a context bar, and double-Esc rewind on that canvas. Leave it if DSH only runs headless into logs or CI and nobody watches the session.
Watch out — DeepSeek Harness 0.2.2-rc.1 rejects the current release before install: the declared DSH range excludes that build, and no published version accepts it. The package runs shell commands on the machine. There is no post-install runtime check.
The verdict — I will not roll DSH backward to make this canvas fit; I wait for a release that targets the Harness I already run.
Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.

dsh-TUI is a DeepSeek Harness plugin that provides a full-screen, Claude Code-style terminal interface for agent sessions. It adds a pixel-whale header, live work status, streaming thought expansion, context progress, TPS and token information, while retaining DSH’s existing session and tool services.
The plugin mounts as a Cordis patch in the dsh-tui profile rather than modifying the DSH core. Session and tool events are projected into React components and rendered through Ink/Yoga; the persistent session log remains the source of truth, while activity tracking supplies TUI-only status data. DSH services continue to own model calls, tool execution, fork/resume, compaction and persistence. It also reads and writes named local settings such as ~/.dsh-tui/agent-preset.json and ~/.dsh-tui/model.json, and can load themes from ~/.dsh-tui/themes/<name>.json.
dsh-TUI is intended for developers who want terminal-native interaction, message search, file and command completion, slash commands, session rewind/fork and detailed agent telemetry. It is a poor fit where a plain DSH interface is preferred, or where no usable TTY is available. The terminal surface is the plugin’s main reach: it captures keyboard and mouse input, renders session content, and supports terminal clipboard paths including OSC 52 and local clipboard utilities. Running a model also requires DEEPSEEK_API_KEY; startup requires the official dsh CLI and pnpm 10 or later.
The dsh-tui profile applies a Cordis patch to DSH and projects session and tool events into terminal-rendered React components. Ink/Yoga handles rendering. Session logs remain the source of truth; model calls, tool execution, fork, resume, compaction and persistence remain with DSH services. TUI-only activity data is kept in an in-memory ActivityTracker.
The interface supports streaming Markdown, structured tool cards, message and session search, @ file completion, text and image attachments, inline or alternate-screen rendering, and /lang language switching. Long sessions use event-driven projection, differential terminal output, message virtualisation, replay merging and bounded caches.
| Setting | Behaviour |
|---|---|
DSH_TUI_THEME |
Takes precedence over the persisted theme and automatic terminal-background detection. |
~/.dsh-tui/agent-preset.json |
Persists the selected agent preset. |
~/.dsh-tui/model.json |
Persists the model selected through /model. |
~/.dsh-tui/themes/<name>.json |
Stores custom JSON themes. |
Built-in themes include auto, light, dark and dark-ansi. The liangshen preset is shipped with the TUI alongside the official standard, code, minimal and cordis presets. A preset cannot be changed after a conversation has produced messages; it can be changed in a blank conversation.
Session commands include /new, /resume, /rename, /workspace resume|rename|open, /clear, /compact, /export, /trace and /btw. Status and setup commands include /status, /cost, /doctor, /config, /init, /tokens, /permissions and /add-dir. Model and interface commands include /model, /thinking, /theme, /lang, /vim, /terminal-setup, /help and /exit. /mcp reports MCP connection status, while /agents, /plan and /goal expose agent or registry features. /update updates and restarts the TUI, restoring the current session.
A usable terminal TTY, the official dsh CLI and pnpm 10+ are required. Model use requires DEEPSEEK_API_KEY. Windows can use the repository’s dsh-tui.cmd; macOS extended ⌘ bindings require terminal support for the extended keyboard protocol. Full-screen mouse mode is enabled by the profile patch, although fullscreen: true is otherwise off by default. The plugin operates on the terminal surface, including keyboard and mouse input and clipboard handling.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub
Same category
zhu1090093659
Plugin and skin collection for the DSH Web UI: task board, Git graph, right-side panel, remote mobile UI, pet, live token stats, and a skin center.
Installed cleanly when we ran it
zhu1090093659
Task board for the dsh web GUI: a sidebar multi-column kanban whose cards run in real DSH agent sessions and can also be scheduled with cron expressions, executed host-side even with the browser closed.
Installed cleanly when we ran it
zhu1090093659
Plugin and skin collection for the DSH Web UI: task board, Git graph, right-side panel, remote mobile UI, pet, live token stats, and a skin center.
No one-line install — this plugin lives inside a larger repository and publishes no npm package.
MeteorNOX
A fixed-corner whale widget for the DSH web GUI — balance, today's usage and per-turn cost with peak/off-peak pricing, editable balance-alert and daily-budget bubbles, a module-based custom bubble queue with A/B weighted choices and random lines or images, 30+ vendor templates (OpenAI, OpenRouter, Kimi, SiliconFlow, Ark, Zhipu, MiniMax and more) with per-model balance and subscription quota, plus task-end sound, imported audio, custom roles and a resource manager. Local-only, no telemetry.
Installed cleanly when we ran it
omdsh-dev
Full sidebar workbench with file rendering and editing, terminal, Git, and subagents; third-party plugins can register new tabs.
Installed cleanly when we ran it