dsh-shell-wsl

On Windows, DeepSeek Harness disables the bash tool by default and exposes only PowerShell. The common community workarounds each carry trade-offs: Git Bash (MSYS2) is not a real Linux kernel and frequently fails to integrate permission presets correctly; a directly mounted WSL distro accumulates state across sessions and can bypass DSH file-policy constraints. dsh-shell-wsl takes a different approach: every bash tool call is routed into a disposable Docker container on the WSL2 backend, trading a single cold start for genuine Linux semantics, per-call isolation, and native permission-preset linkage.

Each call spawns a short-lived container (default image: Ubuntu 24.04) with the workspace bind-mounted for two-way file sharing. Permission presets map directly to mount modes: read-only sessions mount the workspace as read-only, while workspace-write and danger-full-access both mount read-write. The container is destroyed after every call via docker run --rm, leaving no residual directory changes, environment variables, or installed packages. Background jobs, timeout tree-kill, orphan-container lazy reaping, and infrastructure-error classification are all inherited from the official executor contract with zero reimplementation on the plugin side.

This plugin is purpose-built for Windows dsh users who need genuine Linux bash semantics (apt, pipes, Unix process model) and value permission-constrained, reproducible execution. If you only require a fast-starting POSIX approximation, a Git Bash approach is lighter; if you want a persistent, stateful Linux environment tightly coupled to a specific WSL distro, direct WSL access is a better fit. dsh-shell-wsl focuses on one thing: making every single bash call run in a clean, reproducible, permission-aware real-Linux environment.