The name in the Install block on any plugin page. A GitHub URL works too — it becomes github:owner/repo.
dsh plugin --profile web add billion-context
Run it on the machine that runs dsh. If your profile isn't called web, put your profile's name there instead.
The desktop app installs plugins itself, not from a terminal:
- Open Settings → Plugins
- Choose Install and paste the plugin name
The desktop app and dsh web keep separate plugin lists — what you install in one does not appear in the other.
Check that it worked
Reload dsh web and open Settings → Plugins; if the plugin is listed, it's installed. Most plugins take effect on reload; a few need a restart of dsh web.
Update and uninstall
Update: swap add for update and run it again to get the latest version. To stay on a specific version, add @version to the name.
dsh plugin --profile web update billion-context
Uninstall: swap add for remove.
dsh plugin --profile web remove billion-context
In the desktop app, update and uninstall from Settings → Plugins.
When it won't install
These are the failures people actually hit. Match the message you saw.
"Published too recently", or no matching version
npm waits about 24 hours before it lets anyone install a fresh release, as supply-chain protection. Wait it out and install again. Mirrors also sync later than the official registry, so "no matching version" usually means the mirror is still catching up — not that the plugin is gone.
If you must install now and you trust the source, add --config.minimum-release-age=0: dsh plugin --profile web add --config.minimum-release-age=0 name. That skips the wait, so only do it for a plugin whose source you've checked.
Waiting for a write lock, or the install hangs
Another dsh or pnpm is changing the same profile. Quit every dsh — the desktop app included — and try again. If you're sure nothing is running, delete package.json.lock in the profile directory and retry.
Downloads stall or time out
That's the network. Check your proxy works, then make the terminal use it too and retry. On slow routes, point npm at a mirror closer to you.
Installed, but Settings doesn't list it
It probably went somewhere else: the desktop app and dsh web each keep their own list, and if dsh web runs on a server, the plugin has to be installed on that server.
Before you install
A plugin is third-party code that runs with your permissions: it can read your files, use your credentials, and reach the network. Check the source of anything you don't recognise, and pin a commit when you can (github:owner/repo#sha).