Install a DSH plugin

Last updated 2026-11-09

DSH installs plugins through its own package manager: the plugin becomes a dependency of the profile, and its bundle patch is inserted into the startup configuration.

One command

$ dsh plugin --profile web add <package or source>

The source can be an npm name, a git URL pinned to a commit, a local directory, or a tarball. DSH runs pnpm, records the dependency in the profile, and inserts the plugin row into cordis.patch.yml.

Why nothing happened

With HMR the plugin loads in place — refresh the page. Without HMR the row is written but not loaded until DSH restarts.

Incompatible versions are refused up front

Before running pnpm, the host checks the plugin's engines.dsh (or its @deepseek-ai/dsh-* peer ranges) against the running DSH version. A mismatch installs nothing and runs no scripts; you can grant an exact-version exemption and retry.

Build scripts are blocked by default

pnpm 11 blocks dependency build scripts. A failed install reports pendingBuilds; approve them explicitly and retry, knowing they run with your user's permissions.