DeepSeek Harness Plugin

huangfuren/dsh-sync

Category Development & Runtime Added 2026-10-23

Move an entire dsh installation to another machine and check it item by item. Three layers go across: the declaration layer (settings, credentials, plugin declarations and vendored link: sources), the state layer (sessions, storages, skills, attachments) and, optionally, the workspace project code. Sessions are rewritten at the zstd header frame only, workspace paths are remapped through an explicit path mapping, and at the end 14 checks (I1–I13 plus I6b) report PASS / FAIL / WARN. A LAN route pairs two machines and pulls the bundle over directly; merge mode diffs a bundle against a machine that has already been in use and stops before writing anything while conflicts are undecided.

Install

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

dsh plugin --profile web add github:huangfuren/dsh-sync

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.