atlas5301/dsh-remote-sessions

Runs a remote DSH over strict SSH inside the stock workspace, composer, approvals and history UI — a backend only, no second frontend.

Lets one DSH drive an agent on another machine while keeping the local UI exactly as it is: what runs locally is a metadata-only session plus a backend proxy, and the remote side is an independently supervised DSH with a companion process, joined by a strict, bounded SSH protocol. Remote setup is lifecycle-managed by the plugin instead of being a prerequisite: installing the local plugin never touches SSH, and on first use of a configured machine the transport tries the private socket and, if it is absent, runs the setup facade — a read-only detection probe for the node version, the installed DSH CLI path and version, and the resident marker — before one retry. The remote agent loop, its models, tools, files and persistence stay on that host, so the local machine is a view and a relay rather than a copy, and the same conversation, approval and history surfaces keep working unchanged.

Infrastructure & Deployment ★ 0 updated 2026-10-06
View on GitHub ↗

Install

dsh plugin --profile web add dsh-remote-sessions

The README's first-channel line; --profile desktop also works. It documents three alternatives itself: npm install dsh-remote-sessions inside the profile, a pinned form (dsh plugin --profile web add npm:dsh-remote-sessions@0.8.3), and dsh plugin --profile web add github:atlas5301/dsh-remote-sessions. After installing, restart the profile's runtime and add a machine under Settings → Remote Sessions. The package is backend-only by design — no client entry, no custom chat panel, no browser dependency — so nothing about the existing UI changes.

Compatibility

Requires DSH 0.2.0-rc.2 or later on the 0.2.x line on both hosts, and Node 22.15+. SSH must authenticate non-interactively with a key or agent, as the same Unix user that owns the runtime directory. The README records what has actually been exercised rather than implying general support: 0.8.10 status was tested against installed 0.2.0-rc.2 with isolated real runtimes and verified end to end on a live remote host over strict SSH, covering provisioning, model and credential sync, session proxy, the file tree, terminals, upgrade and restart flows.

Details

Alternatives

btsd321/dsh-remote-explorer · mathangler/dsh-remote-access · wutian122/dsh-remote-shell

More plugins in Infrastructure & Deployment

Browse more in Infrastructure & Deployment

Guides for Infrastructure & Deployment plugins