dsh-gitbash-preset

The official Minimal mode in DSH is a dead end on Windows — and it's not your fault. The README lays out two layers of failure: the bundled subprocess-local simply refuses PTY support on win32 ("terminal inspection is unsupported on platform win32"), and dsh-bash-local hardcodes a PATH lookup for bash, which Windows doesn't ship by default. Even if you have Git installed, the minimal mode never actually starts.

dsh-gitbash-preset turns that "unusable" into "usable." It ships an installable preset variant that keeps the exact same tool surface as the original minimal mode — persona + str_replace_editor — but re-implements the bash tool as a per-command bash -c execution, with auto-detection for Git for Windows' bash (GIT_BASH env var → common install directories → PATH → plain bash fallback). Installation is idempotent: on DSH startup the preset is copied to your user preset root, skipped if already present, and never clobbers existing files unless you force it.

The most interesting part is the sandbox-aware gating. MSYS cannot create a signal pipe inside Windows restricted-token sandboxes, so commands only run under the "danger-full-access" policy (or when deployment has no sandbox). If the session is workspace-write or narrower, the first call fails with clear instructions to upgrade once via sandbox_permissions: "danger-full-access" + justification through the normal approval flow. It doesn't bypass the sandbox — it simply makes the boundary explicit.

Who is this for? Windows developers using DeepSeek Harness who want to actually use Minimal mode's bash and are stuck on the PTY limitation. After installation, open a new session, pick Minimal (Git Bash), switch the sandbox to full access, and start working. Just have Git for Windows installed — no hardcoded paths or extra setup required.