DeepSeek Harness Plugin Install Command Builder

What this tool does

Installing a DeepSeek Harness plugin is one command, but the details are easy to get wrong: --profile has to come before add, a GitHub repository needs the github: prefix, and the npx form is spelled differently from the global one. This tool builds the command for you from the plugins you pick, so you can copy it instead of retyping it.

It does not install anything and it does not read the plugins. It is a text generator for the commands the install guide already documents.

How to use it

1. Type or paste plugins into the box, one per line or separated by commas, or find them with the directory search and press Add. Plugins that have their own evaluation page here are marked.
2. Choose the profile (web is the default), whether dsh is installed globally or you want the npx form, and whether to get one command or one command per plugin.
3. Copy the command, run it in a terminal, then run the check command below it.
4. Restart dsh web so the plugin tree is rebuilt.

Input forms it accepts

Why the output looks the way it does

• --profile comes first. dsh plugin forwards everything after add to pnpm inside the profile directory, so the launcher's own flags have to precede it. The install guide explains the mechanism.
• Narrow input, no clever fixing. The output ends up in a terminal. The tool therefore accepts only letters, digits and . _ - / : # @, and rejects everything else instead of quoting it. A rejected line is shown, so you can see what to correct.
• A short list of profiles. web, headless, tui and acp are offered because the guides use them. Any other valid name works too.

What it does not do

• It does not check that a plugin exists, works or is safe. Read the plugin's README, and see the safety guide before installing code you have not read.
• It does not know a plugin's extra setup, such as API keys or config entries. Those are in each plugin's README.
• It does not generate removal commands; see uninstalling plugins.
• dsh needs a current Node.js (24.9 or newer at the time of writing). If a command fails to start, check that first, then the troubleshooting guide.

Frequently asked questions

What exactly does the command builder generate?

Only forms the install guide documents: dsh plugin --profile web add <package-or-source> for installing, npx -y @deepseek-ai/dsh plugin --profile web add <package-or-source> when dsh is not installed globally, and dsh plugin --profile web list to check the result. GitHub sources are written as github:owner/repo with an optional #tag, #branch or #commit; npm sources are written as typed.

Does the tool install anything or run commands for me?

No. It only produces text for you to copy into your own terminal. The command is assembled in your browser; the only thing sent to this site is the search text if you use the directory search.

Why does a plugin from a monorepo sometimes not install with github:owner/repo?

github:owner/repo installs the repository root. If the directory lists the plugin as a sub-folder of a larger repository, the root is not the plugin, so the tool shows a warning and you should follow that plugin's own README for the exact source.

Can I install several plugins in one command?

Yes. dsh forwards everything after add to pnpm, so several sources can follow one add. The tool can put them all in one command or write one command per plugin, which makes a single failure easier to spot.

Why was my input rejected instead of being fixed automatically?

The result is pasted into a shell, so the tool accepts a narrow set of characters (letters, digits and . _ - / : # @) and refuses anything else rather than trying to quote it. Version ranges such as ^1.2 or ~1.2 are refused for the same reason; pin an exact version or tag instead.

Related

• Install DeepSeek Harness plugins: the full guide behind these commands
• Must-have plugins and best plugins: where to start
• DeepSeek API cost calculator: what the sessions will cost to run