DSH Toolbox

dsh-agent-compare

Run the same request through several attempts and compare answers, files and pages.

Version 2.0.0 of dsh-agent-compare, last published 2026-11-10; the install command and the range come from its own manifest.

Install

dsh plugin add dsh-agent-compare 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-agent-compare

Compatibility

engines.dsh in dsh-agent-compare declares >=0.2.1-rc.3 <0.3.0-0; run dsh --version and compare it, because outside that range the CLI skips the plugin at boot and prints the requirement instead of booting.

If two plugins fight

Eleven peers including @deepseek-ai/dsh-sandbox and dsh-subprocess; one request becomes 2–4 real runs, so it multiplies token spend. With @nanmicoder/dsh-agent-teams both are spawning agents from the chat surface, and the shared chat row is the collision point.

Who made it

Author: lijiaqi-AI-Product-Manager. Repository: https://github.com/lijiaqi-AI-Product-Manager/dsh-agent-compare. Package page: https://www.npmjs.com/package/dsh-agent-compare.

After install

It declares @deepseek-ai/cordis as a peer and renders agent controls in the composer toolbar; after dsh plugin add dsh-agent-compare, dsh --profile web --dump-config lists the row that mounts it.

Files it touches

No storage peer appears in the manifest of dsh-agent-compare, 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-agent-compare is the mirror command, dsh plugin --profile web remove dsh-agent-compare. 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 @nanmicoder/dsh-agent-teams?

For dsh-agent-compare the recommendation is @nanmicoder/dsh-agent-teams: It peers 23 packages and owns team roles; compare multiplies spend 2–4× per request and is a one-off diagnostic.

Which dsh versions load it, and what happens outside that window?

On >=0.2.1-rc.3 <0.3.0-0 the CLI loads dsh-agent-compare; outside it, boot stops with the requirement instead of running the plugin. dsh plugin allow-version dsh-agent-compare is the per-package override if you accept the risk.