dsh-win-multi-bash

Running DeepSeek Harness on Windows, the single pwsh shell seat often leaves a gap: no MSYS toolchain, no full Linux userland. dsh-win-multi-bash closes that gap by routing pwsh, Git Bash, and WSL through one shared ctx.shell slot. The model targets a backend via request.shell, and the shell-select executor dispatches the call to the right engine, while pwsh default behavior stays bit-identical to a stock deployment.

Three capabilities anchor the plugin. First, multi-backend tool registration: git_bash speaks the MSYS dialect, wsl_bash speaks the Linux dialect, and both register on the host plane so every session sees them immediately; executable resolution is lazy, so a machine missing Git Bash or WSL never disturbs pwsh. Second, per-backend sandboxing: pwsh is always confined by a windows-acl restricted-token runner, wsl_bash invokes bubblewrap inside the distro for full file isolation, and git_bash best-effort wraps MSYS bash under the same windows-acl runner; when a probe fails the run degrades to unconfined by contract, and an optional requireSandbox flag can harden that path by refusing workspace-write calls when the probe does not pass. Third, hot-plug deployment: install.ps1 writes a junction and a managed block into cordis.patch.yml so dsh web hot-reloads the change with no restart required.

This plugin is aimed at Windows-based DSH developers whose daily workflow mixes pwsh scripts, MSYS tooling, and Linux shell commands, or teams that need all three backends available in the same session. Existing deployments that already ship their own shell-select row will see it cleanly replaced to avoid duplicate loader entries, and if you only need the occasional bash command the rest of your deployment remains untouched.