dsh-mobile-plugin

Q: Does it collide with ds-harness-remote?

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

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

On >=0.2.0 the CLI loads dsh-mobile-plugin; outside it, boot stops with the requirement instead of running the plugin. dsh plugin allow-version dsh-mobile-plugin is the per-package override if you accept the risk.

A mobile API and relay client so a phone can drive DSH.

Version 0.5.49 of dsh-mobile-plugin, last published 2026-11-13; the install command and the range come from its own manifest.

Install

dsh plugin add dsh-mobile-plugin 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-mobile-plugin

Compatibility

engines.dsh in dsh-mobile-plugin declares >=0.2.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

Adds /api/mobile/v1 routes on dsh-host-webserver and requires dsh >=0.2.0. ds-harness-remote and dsh-remote open their own channels; three remote paths on one profile means three tokens and three places to rotate them.

Who made it

Author: WNLUO. Repository: https://github.com/WNLUO/dsh-mobile-plugin. Package page: https://www.npmjs.com/package/dsh-mobile-plugin.

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-mobile-plugin, dsh --profile web --dump-config lists the row that mounts it.

Files it touches

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

Common questions

Does it collide with ds-harness-remote?

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

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

On >=0.2.0 the CLI loads dsh-mobile-plugin; outside it, boot stops with the requirement instead of running the plugin. dsh plugin allow-version dsh-mobile-plugin is the per-package override if you accept the risk.