ds-harness-remote

Q: Does it collide with dsh-mobile-plugin?

ds-harness-remote is the one to keep here: It exposes the gateway itself over P2P with end-to-end encryption, so the boundary is one place instead of two route groups.

Q: What happens when dsh upgrades?

Nothing declares a version window for ds-harness-remote: dsh --version tells you what you are running, and no check will tell you whether ds-harness-remote matches it.

Peer-to-peer, end-to-end encrypted remote access to DSH.

Version 0.6.4 of ds-harness-remote, last published 2026-11-08; the install command and the range come from its own manifest.

Install

dsh plugin add ds-harness-remote writes one dependency line into the profile manifest; pnpm then unpacks it under $DSH_HOME/profiles/<name>/node_modules.

dsh plugin --profile web add ds-harness-remote

Compatibility

ds-harness-remote 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

Twelve peers including dsh-api-gateway and the settings pages; it exposes the gateway over P2P. dsh-mobile-plugin exposes its own gateway routes, so both mean two entry points into the same host — one of them will be the one you forget to lock down.

Who made it

Author: liguobao. Repository: https://github.com/liguobao/ds-harness-remote. Package page: https://www.npmjs.com/package/ds-harness-remote.

After install

It declares @deepseek-ai/cordis as a peer and renders a remote entry point in the profile a client connects to; after dsh plugin add ds-harness-remote, dsh --profile web --dump-config lists the row that mounts it.

Files it touches

ds-harness-remote routes whatever it persists through @deepseek-ai/dsh-settings under $DSH_HOME, and its own dependency line sits in $DSH_HOME/profiles/<name>/package.json.

Removing it

Removing ds-harness-remote is the mirror command, dsh plugin --profile web remove ds-harness-remote; the surface goes with it, and whatever it stored under $DSH_HOME stays until you delete it.

Common questions

Does it collide with dsh-mobile-plugin?

ds-harness-remote is the one to keep here: It exposes the gateway itself over P2P with end-to-end encryption, so the boundary is one place instead of two route groups.

What happens when dsh upgrades?

Nothing declares a version window for ds-harness-remote: dsh --version tells you what you are running, and no check will tell you whether ds-harness-remote matches it.