dsh-genui

Q: Does it collide with deep-view?

dsh-genui is the one to keep here: It peers dsh-client-ui-slots and writes the block format into the system prompt, so the producer and the renderer stay in one package.

Q: What happens when dsh upgrades?

Nothing declares a version window for dsh-genui: dsh --version tells you what you are running, and no check will tell you whether dsh-genui matches it.

Interactive charts, forms and calculators in the conversation.

Version 0.3.3 of dsh-genui, last published 2026-11-06; the install command and the range come from its own manifest.

Install

dsh plugin add dsh-genui writes one dependency line into the profile manifest; pnpm then unpacks it under $DSH_HOME/profiles/<name>/node_modules.

dsh plugin --profile web add dsh-genui

Compatibility

dsh-genui ships no engines.dsh entry, so nothing checks it against your CLI version at boot. Read the npm page before installing.

If two plugins fight

Peers @deepseek-ai/dsh-client-ui-slots and @deepseek-ai/dsh-system-prompt; it teaches the model to emit interactive blocks. deep-view renders rich views from the same replies, so a reply that contains both kinds of block gets two different renderers guessing.

Who made it

Author: lhuans. Repository: https://github.com/lhuans/dsh-genui. Package page: https://www.npmjs.com/package/dsh-genui.

After install

It declares @deepseek-ai/cordis as a peer and renders a renderer for answer blocks in conversation replies; after dsh plugin add dsh-genui, dsh --profile web --dump-config lists the row that mounts it.

Files it touches

No storage peer appears in the manifest of dsh-genui, so the dependency line in $DSH_HOME/profiles/<name>/package.json is the only file you can point at; the package description names nothing else.

Removing it

Removing dsh-genui is the mirror command, dsh plugin --profile web remove dsh-genui. Its manifest declares no storage peer, so it writes nothing under $DSH_HOME; removing it leaves no files behind.

Common questions

Does it collide with deep-view?

dsh-genui is the one to keep here: It peers dsh-client-ui-slots and writes the block format into the system prompt, so the producer and the renderer stay in one package.

What happens when dsh upgrades?

Nothing declares a version window for dsh-genui: dsh --version tells you what you are running, and no check will tell you whether dsh-genui matches it.