DeepSeek Harness Plugin

LinYanZhi/dsh-mesh#dsh-mesh

Category Remote & Mobile Added 2026-11-11

Multi-device DSH network: sidebar topology, peer health, delegation, file transfer and node management over TLS, LAN and public tunnels. DSH spawns its mesh server (127.0.0.1:8124) detached at startup and restarts it if it exits, and the server always answers LAN discovery on UDP 0.0.0.0:8129. Once a peer is paired, the default ACL lets it read, search and write files under ~/Code, read session history and logs, and delegate tasks to your DSH sessions; shell_run, channel messages, remote desktop and repair stay off until you allow them. If SakuraFrp is installed it reads that launcher's account token (or SAKURA_TOKEN) to query api.natfrp.com tunnels. Its /api/dsh-mesh routes are guarded only by a loopback peer-address check.

Install

# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)

dsh plugin --profile web add github:LinYanZhi/dsh-mesh#path:/packages/dsh-mesh

Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).

Links

More in this category

View the whole category →

Community comments

Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.