Nagi-ovo/dsh-visualize
In-conversation generative UI: the model renders interactive HTML cards into the chat stream, with streaming preview and sandboxed rendering.
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.
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 11d 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
What it is — DSH can embed interactive HTML cards in the conversation stream.
Who it is for — When you need to display simulators, charts, comparison panels or UI mockups in the conversation, this plugin makes the interface more intuitive. Users who only require pure text interaction don't need it, because it is limited to Web UI.
Watch out — Installation from source requires manually allowing the build script. Sandbox testing passed. No obvious pitfalls found.
The verdict — I would install it because it allows the conversation to include interactive content, which is more complete than text output alone.
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-visualize is a DeepSeek Harness plugin that renders interactive HTML cards directly in the Web UI conversation stream. It is intended for generated simulators, charts, comparison panels and interface mock-ups rather than text-only answers.
When the model needs a visual output, it writes an HTML fragment and calls visualize(path, title?, mode?). The plugin reads the fragment from the supplied path and hands the result to the Web UI for rendering. mode: "wide" is available for content that benefits from a wider card. Rendering uses a sandboxed iframe with an opaque origin; the card follows DSH’s light or dark theme and colour scheme. Tool results are persisted, so replay can restore a card without the original fragment file remaining present.
This is suited to agents whose work benefits from an interactive visual explanation and that run with the web profile. dsh-visualize is the wrong choice when the client is TUI or headless, because those clients show an ordinary tool result instead of an interactive card. It is also not suitable for cards that need network access, embedded pages, form submission, or buttons that send follow-up messages to the main conversation. A fragment is limited to 1000000 bytes by default; maxFragmentBytes can change that limit.
The model produces an HTML fragment, then calls visualize(path, title?, mode?). The path identifies the fragment to render; title is optional. For layouts that need more horizontal space, pass mode: "wide". The resulting card is rendered in the DSH Web UI conversation stream.
The fragment size limit is configurable:
| Configuration | Default | Purpose |
|---|---|---|
maxFragmentBytes |
1000000 bytes |
Maximum size of one HTML fragment |
The card follows DSH’s light or dark theme and whale-blue colour scheme. The README does not document other configuration keys.
Each card runs in a sandboxed iframe with an opaque origin and cannot access the host page. Its CSP blocks network requests, nested pages and form submission. Static resources may be loaded only from a fixed CDN. When a conversation is replayed, the card is restored from the persisted tool result rather than from the original fragment file, so that file does not need to remain available.
For a web profile, dsh --profile web --dump-config can be used to check that the plugin is present in the final configuration. If DSH Web is already running after a plugin change, restart it and refresh the page. The repository’s committed build output means no additional build step is required when installing from a local clone.
Interactive cards are currently rendered only by the Web UI. TUI and headless clients display a normal tool result. Buttons inside a card cannot yet send follow-up messages to the main conversation.
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
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.
Installed cleanly when we ran it
zhu1090093659
DeepSeek Harness（DSH）Web 插件聚合生态包 · 一切皆插件，创意工坊分发
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.
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
ccch1mneyyy
Claude Code-style full-screen terminal UI: pixel-whale header, live status line, and streaming thought expansion.
Installed cleanly when we ran it
