dsh-devices

English · 简体中文

Turn your devices into a fleet.

Zero core changes, pure plugin mounting. A dsh plugin that lets your devices collaborate. Tools auto-register in dsh sessions — any dsh-hosted agent can call them directly. Uninstall leaves no core patches.

Requirements: ① At least 2 devices, each with dsh-devices installed (pairing is two-sided; a single device has nothing to pair with). ② Connectivity: same LAN with mDNS multicast allowed (UDP 5353; doesn't cross routers/subnets), or publicly reachable devices with SSH (port 22) open. NAT-isolated devices cannot connect to each other in this version (V2 = P2P/tailscale planned).

---

┌──────────────┐          ┌──────────────┐
│  dsh + devices  │◄────────►│  dsh + devices  │
└──────────────┘          └──────────────┘

npm install -g @deepseek-ai/dsh

dsh plugin add dsh-devices

Tools

Module	Tool	What it does
mdns	fleet_discover	Scan the LAN for devices
mdns	fleet_pair	Pair with a device key
ssh	fleet_ssh_exec	Run a command on a paired device
ssh	fleet_workspace	Set/view remote workspace
ssh	fleet_upload	Upload a file to a paired device
ssh	fleet_download	Download a file from a paired device
ssh	fleet_status	Liveness probe for all paired devices (online/latency/last used)

Disabled modules don't register their tools (modules: mdns | ssh | both).

No commands to memorize — discovery, pairing, and execution are all done by the agent calling fleet_discover / fleet_pair / fleet_ssh_exec in your session.

Or grab the tgz from Releases: dsh plugin add ./dsh-devices-<version>.tgz.

---

dsh plugin add dsh-devices

dsh plugin add ./dsh-devices-<version>.tgz

You should see a clean install with no warnings. Four fleet_* tools are then auto-registered in dsh sessions.

git clone https://github.com/polaris-smart/dsh-devices.git

---

Scenario A: Same LAN (recommended start)

Both devices need dsh-devices (pairing is two-sided). Devices A and B on the same LAN.

B's user asks B's dsh agent to "start fleet broadcast" (agent runs fleet7 serve), or manually:

fleet7 serve

B generates a device key (fleet-d-..., printed in the terminal) on first fleet7 serve. Then on A:

Pair once, use forever — B has authorized A's public key; A remembers how to reach B.

Scenario B: Cross-network (SSH direct)

When devices are not on the same LAN (e.g., commanding a cloud server from home):

echo "ssh-ed25519 AAAA... my-server" >> ~/.ssh/authorized_keys

fleet8 ssh my-server "hostname"

Then use fleet_ssh_exec / fleet_workspace in dsh sessions.

---

|---|---|---|---|

Disabled modules don't register their tools.

|---|---|---|

Errors carry next-step guidance; file transfer & workspace go through the agent tools.

After install, just say "call fleet_discover" in your dsh session to see LAN devices; pair once, then command remote devices with fleet_ssh_exec. No extra config — tools are exposed to every agent in the dsh session.

Only paired devices are reachable; key files must be 0600; all errors return readable text instead of throwing.

|---|---|---| | modules | both | mdns / ssh / both |

┌─────────────────────────────────────────────────────┐
│                     dsh (DeepSeek Harness)                        │
│  ┌──────────────┐  ┌──────────────┐  ┌───────────┐  │
│  │ fleet_pair    │  │ fleet_workspace│  │           │  │
│  └──────┬───────┘  └──────┬───────┘  └───────────┘  │
│         │ mDNS            │ SSH                     │
└─────────┼─────────────────┼─────────────────────────┘
          ▼                 ▼
   ┌────────────┐    ┌──────────────┐
   └────────────┘    └──────────────┘
          │                 │

For full troubleshooting see TROUBLESHOOTING.md.

A: Both devices must be on the same LAN (mDNS multicast doesn't cross routers); the target must run fleet7 serve; allow UDP 5353 through firewalls.

A: Use Scenario B manual pairing; check port 22 reachability and that the public key is in authorized_keys.

A: You likely have an outdated package — download the latest tgz from the Releases page.

A: After restarting the dsh session, type /fleet — seeing your device identity and paired devices means it works. Or ask the agent to call fleet_discover.

A: Check: ① the plugin was added to the profile you're booting (dsh plugin --profile <name> add dsh-devices) ② the session was restarted ③ Node 22+ (node --version). Still missing? Open an issue with the dsh plugin output.

A: Verify port 22 reachability (nc -vz <ip> 22 or fleet8 ssh <name> hostname) and that the public key is in the target's authorized_keys. Timeouts are usually network/firewall issues, not plugin issues.

Found a bug or have an idea?

  Task-board claiming: post tasks from any device, paired devices claim them

v0.2.10（2026-08-20）

v0.2.9（2026-08-19）

v0.2.8（2026-08-19）

v0.2.7（2026-08-19）

v0.2.6（2026-08-19）

v0.2.5（2026-08-19）

v0.2.4（2026-08-17）

v0.2.0（2026-08-18）

MIT © polaris-smart