deep-view

Q: Does it collide with dsh-genui?

For deep-view the recommendation is dsh-genui: 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 deep-view: dsh --version tells you what you are running, and no check will tell you whether deep-view matches it.

Rich views — charts, tables, inputs — inside an answer.

Version 0.1.2 of deep-view, last published 2026-11-05; the install command and the range come from its own manifest.

Install

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

dsh plugin --profile web add deep-view

Compatibility

deep-view 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-tools and @deepseek-ai/dsh-web, and it parses view blocks out of answers. dsh-genui produces blocks from the same prompt section; when both are loaded, a malformed block fails in one renderer and renders in the other.

Who made it

Author: Fei2411. Repository: https://github.com/Fei2411/deep-view. Package page: https://www.npmjs.com/package/deep-view.

After install

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

Files it touches

No storage peer appears in the manifest of deep-view, 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 deep-view is the mirror command, dsh plugin --profile web remove deep-view. 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 dsh-genui?

For deep-view the recommendation is dsh-genui: 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 deep-view: dsh --version tells you what you are running, and no check will tell you whether deep-view matches it.