dsh-computers
Connect your own machines to a DSH deployment and run commands on them from the agent.
Version 1.9.9 of dsh-computers, last published 2026-11-13; the install command and the range come from its own manifest.
Install
dsh plugin add dsh-computers 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-computersCompatibility
dsh-computers 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
Lets the agent run commands on your other machines. dsh-ops and dsh-windows-mcp also register command execution, so the model picks among three tools with different sandboxes and different blast radius.
Who made it
Author: 9Ashwin. Repository: https://github.com/9Ashwin/dsh-computers. Package page: https://www.npmjs.com/package/dsh-computers.
After install
It declares no dsh peer and renders a remote entry point in the profile a client connects to; after dsh plugin add dsh-computers, dsh --profile web --dump-config lists the dsh-computers row that mounts it.
Files it touches
No storage peer appears in the manifest of dsh-computers, 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-computers is the mirror command, dsh plugin --profile web remove dsh-computers. 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-windows-mcp?
dsh-computers is the one to keep here: It is built for many machines rather than one OS surface; keep windows-mcp only if every target is Windows.
What happens when dsh upgrades?
Nothing declares a version window for dsh-computers: dsh --version tells you what you are running, and no check will tell you whether dsh-computers matches it.