dsh-windows2macos: One DeepSeek Harness Instruction for Every Windows and macOS Machine

What Does It Do?

W2M is a DSH plugin for DeepSeek Harness that lets one DeepSeek account and one instruction drive every Windows and macOS machine you own through the same project. It fills the gap left by DSH's one-process-per-machine model, its loopback-only transport, and the official agent-team feature that does not support separate working directories or several processes coordinating over one team. The plugin combines a Rabbit relay, a per-machine Localside agent, and a set of DSH tools, and every machine only makes outbound connections, so no public IP, port forwarding, or SSH server on Windows is required.

Core Features

• Cross-platform replication: replicate mode runs the same command on every machine and compares results side by side, answering "does this change pass on both platforms?".
• Work sharding: split mode divides work by index, with explicit and modulo sharding, suited to running one large test suite across several machines.
• Six-state aggregation: results are classified as consistent, divergent, divergent-platform, failed, partial, or unverifiable, keeping "the environments differ" separate from "the results differ" so noise is not turned into bug reports.
• Anchor verification: each machine's Localside agent carries three anchors, and when an anchor does not match the comparison is refused and reported as unverifiable, ensuring the same revision is being compared.
• Outbound-only relay: the Rabbit relay tracks devices, tasks, leases, and state reports, while machines use outbound POST and SSE only, with no inbound port exposed.

How to Use This Plugin?

Start the Rabbit relay on any always-on machine; it prints a pairing code, and after the first machine is paired it immediately prints a new code for pairing the second. Then issue an instruction from a DSH session on any machine, choosing replicate or split mode, and each machine's Localside agent executes the corresponding command and reports results back to the relay. Both the relay and the agent are plain Node scripts with no runtime dependencies, so they can be run from a clone or invoked through the installed entry point as described in the README.

How to Troubleshoot This Plugin?

If a report comes back as unverifiable, an anchor on one machine did not match, so the plugin refuses to compare results; confirm that every machine is on the same project revision before reissuing the instruction. If the state is divergent-platform, the difference is usually just toolchain or platform variation confined to stdout text and is expected rather than a defect; only divergent names the specific field and each machine's value in the report.