dsh-permission-remote

Q: Which dsh versions load it, and what happens outside that window?

On >=0.2.2-rc.1 <0.3.0 the CLI loads dsh-permission-remote; outside it, boot stops with the requirement instead of running the plugin. dsh plugin allow-version dsh-permission-remote is the per-package override if you accept the risk.

SSH remote workspaces that reuse the session sandbox mode and the approval flow.

Version 0.18.1 of dsh-permission-remote, last published 2026-11-13; the install command and the range come from its own manifest.

Install

dsh plugin add dsh-permission-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 dsh-permission-remote

Compatibility

engines.dsh in dsh-permission-remote declares >=0.2.2-rc.1 <0.3.0; run dsh --version and compare it, because outside that range the CLI skips the plugin at boot and prints the requirement instead of booting.

If two plugins fight

Twelve peers including the approval service; it reuses the session sandbox mode for SSH targets. dsh-remote and ds-harness-remote add more remote paths, and each one asks for approval its own way.

Who made it

Author: weicy98. Repository: https://github.com/weicy98/dsh-permission-remote. Package page: https://www.npmjs.com/package/dsh-permission-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 dsh-permission-remote, dsh --profile web --dump-config lists the row that mounts it.

Files it touches

dsh-permission-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 dsh-permission-remote is the mirror command, dsh plugin --profile web remove dsh-permission-remote; the surface goes with it, and whatever it stored under $DSH_HOME stays until you delete it.

Common questions

What does it hook into, and how do I check that slot is free?

Its manifest names no community counterpart, so the check is manual: after dsh plugin add dsh-permission-remote, run dsh --profile web --dump-config and look for two rows claiming the same slot.

Which dsh versions load it, and what happens outside that window?

On >=0.2.2-rc.1 <0.3.0 the CLI loads dsh-permission-remote; outside it, boot stops with the requirement instead of running the plugin. dsh plugin allow-version dsh-permission-remote is the per-package override if you accept the risk.