[implemented in herdr-win] Windows as a herdr --remote target

[hdosys]

Status

Windows remote-target support is fully implemented and used in daily development by herdr-win. It is not yet part of official upstream Herdr. This discussion tracks upstream direction and compatibility feedback for that implemented behavior.

Implemented scope

• Linux, macOS, and Windows clients can run herdr --remote <host> against a Windows OpenSSH host. Windows x86_64 hosts are supported directly; ARM64 hosts are supported when they can run the matching x86_64 payload through Windows emulation.
• Herdr uses an exact protocol-compatible herdr.exe from the SSH user's PATH or the stable per-user runtime at %USERPROFILE%\.herdr\remote\bin\herdr.exe. If neither matches, interactive attach can offer to transfer and validate the complete digest-verified portable payload without running setup or changing remote PATH.
• Explicit unattended provisioning is available through herdr --remote <host> --provision --yes --json. Named-session creation, reattachment, reconnect, resize, keyboard input, and normal shutdown use the existing Herdr client protocol.
• The Windows OpenSSH default shell must be cmd.exe or PowerShell 7 (pwsh.exe). Ordinary non-interactive attach leaves an unprepared host unchanged, and the supported path uses normal SSH connections and named-session reattachment rather than live handoff.

The executable, command, configuration, state, and protocol identity remain herdr. Implementation and usage details are in the herdr-win cross-platform README.

Upstream question

Would this implemented scope fit Herdr's direction, and what review or PR shape would be most useful for moving Windows remote-target support upstream?

[hdosys]

Test build update: herdr-win v2026.08.17.10 (Herdr v0.8.0) is available with matching Windows x86_64, Linux amd64/arm64, and macOS amd64/arm64 builds.

The most useful checks are:

• Attach when a matching herdr.exe already exists on the Windows SSH user's PATH.
• Interactive provisioning when no matching runtime exists, followed by named-session creation and reattachment.
• Windows x86_64 and emulated ARM64 hosts using cmd.exe or PowerShell 7 (pwsh.exe) as the OpenSSH default shell.
• Reconnect, resize, keyboard input, and normal session shutdown.

Please leave short success reports and compatibility notes here. For reproducible herdr-win failures, open a herdr-win issue with the client and host OS/architecture, SSH default shell, command used, and relevant error text. General behavior that also reproduces with an official Herdr build should still be reported upstream.

The Windows setup is currently unsigned, so a manual GitHub download may show SmartScreen. Use only the tagged release above and verify the GitHub asset digest.

[hdosys]

herdr-sandbox-showcase.mp4