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
vlln/dsh-navbar
Conversation node navigation bar for quick jumps between user messages.
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
Installed cleanly when we ran 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 2mo ago.
Show it in your README
For maintainers: the badge serves this listing's latest sandbox verdict, so a re-run updates it on its own — and it links readers to the full result here.
Due diligence
Security
No build script was blocked in our run.
Source: our sandbox install, 2mo 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 — Adds a node navigation rail to the right edge of the DeepSeek Harness conversation area, supporting hover previews, click-to-jump, and scroll-wheel switching between user messages.
Who it is for — Users reading long conversations in DeepSeek Harness who need quick location of different user messages will find this plugin suitable. Users on non-conversation pages or without loaded user messages in DeepSeek Harness do not require it.
Watch out — Sandbox real test passed after installation in a new profile where it registers into the profile via harness. No obvious issues found.
The verdict — I would install it because it automatically loads earlier history until at least one user message is loaded, maintaining the navigation rail's utility.
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-navbar is a DeepSeek Harness plugin that adds a vertical navigation bar for jumping between user messages in the Chat view. Each user message becomes a node on the conversation’s right edge. The active marker follows the reading position; hovering previews the message, and clicking scrolls to the associated message. The bar hides when there are fewer than two user messages or when the current page is not a conversation.
DeepSeek Harness loads dsh-navbar as a browser-only bundle through the dsh.bundle and dshClient channels. The client reads the official data-time-hover-root anchor attributes on user-message rows rather than polling, routing, or using tools. It renders its own DOM, handles hover and wheel navigation, and uses the conversation.chat.assistant-actions slot to add a pin button to assistant message actions. Pinned replies are stored per conversation in browser localStorage.
dsh-navbar is intended for developers who want visual navigation through long conversations without adding an agent command. It is not suitable when a browser-only UI extension is inappropriate, when navigation is needed outside the Chat view, or when fewer than two user messages are normally present. More than 11 nodes are shown through a sliding window rather than all at once, and prefers-reduced-motion disables animation.
DeepSeek Harness displays one circular node for each user message in the Chat view. The active 22px blue pill moves with the current reading position. Hovering a node opens a six-line-truncated preview card. Hovering the bar’s gaps selects the nearest node, and the preview plus an elongated grey pill indicate the prospective destination. Scrolling while the pointer is over the bar moves to the previous or next user message and prevents the conversation area from scrolling. Clicking the bar also selects the nearest node and performs a smooth scroll with a blue highlight ring.
When there are more than 11 nodes, DeepSeek Harness shows a sliding window. The bar is hidden outside conversation pages and when fewer than two user messages exist. Animation is disabled when prefers-reduced-motion is active.
The assistant action row gains a pin button between copy and Good response. Selecting a reply renders its conversation node as a gold, narrow oval that remains visible. Its preview includes a pin badge and the reply text, and clicking the node jumps directly to that reply. Pin state is retained per conversation in browser localStorage; selecting the same pin again removes it. The pin control uses the conversation.chat.assistant-actions slot.
DeepSeek Harness loads the client as a dsh.bundle plugin through the dshClient channel in the web profile. The client reads official data-time-hover-root attributes, including those on user rows from the 0806 update. It uses no polling, routes, or tools. The Node half is empty: src/index.mjs contains an empty apply, while the browser implementation is in src/client/index.ts and builds to lib/client.js.
No configuration keys or plugin commands are documented. Installation is performed through the page’s rendered installation control; after installation, DeepSeek Harness must be restarted before the web client takes effect. The plugin has no user-facing command or tool.
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.
ccch1mneyyy
Claude Code-style full-screen terminal UI: pixel-whale header, live status line, and streaming thought expansion.
Installed cleanly when we ran it
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