Big-Dao/dsh-plugin-wsl-env

dsh-plugin-wsl-env is a cordis plugin shipped as a DSH bundle manifest and exists solely for DeepSeek Harness on Windows hosts with WSL2 installed. It rebinds the harness's working environment to a chosen WSL distribution: commands execute inside the distro via wsl.exe -d <distro> --cd <linux> --exec <login shell> -lc <cmd>, file tools read and write the distro's real files rather than /mnt/c mirrors, the GUI folder picker lists installed distros at its root, and the right-sidebar New terminal opens a shell inside the same distro in the session folder. The README shows no support for any non-DSH target, and the product is not a generic MCP server or cross-agent launcher: it is layered on top of DSH's own terminal-controller, directory-picker, and file-system providers. Installation runs four commands in a Windows terminal — dsh wsl --from-default-profile web --dump-config, dsh plugin --profile wsl add dsh-plugin-wsl-env, dsh --profile wsl --dump-config, and dsh --profile wsl — and the second step applies cordis.patch.yml as a configuration layer rather than merging anything by hand.

The intended user is a DSH operator on Windows who wants the model to operate directly on Linux paths inside WSL without copying files across the 9p share. A typical session opens \\wsl.localhost\ubuntu\home\you\project as the workspace, after which a prompt such as "what kernel am I on, and what is in /etc/os-release" runs uname -r and reads that file through the distro's own filesystem. The wsl preset is bound at session creation so the very first tool call already targets the correct distro, and DSH_WSL_DISTRO, DSH_WSL_SHELL, and DSH_WSL_HOME are registered in the managed DSH_* namespace so the model can see its shell environment. The Permissions selector switches between read-only, workspace-write (the default), and danger-full-access; a refused command or write returns alongside an offer to rerun that single call with wider permissions, except for FS_OUTSIDE_DISTRO, which is a path-policy refusal that cannot be lifted by expanding permissions. Configuration overrides go into $DSH_HOME/profiles/<name>/cordis.patch.yml keyed by row id, with distro, sandbox, restrictToDistro, and includeHostHome as the rows the README highlights.

Dependencies are minimal: Node 22.8+ for the coverage script, npm test runs on Node 20, 22, and 24 across Linux and Windows CI, and the only runtime prerequisite inside the distro is bubblewrap from apt, without which every command fails closed by the sandbox. The package itself has no third-party dependencies and every tested module imports only Node built-ins, so there is nothing to install beyond the bundle manifest itself. There are several limits a first-time user should know about: pnpm cannot link a \\wsl.localhost\... UNC path and will leave a broken symlink, so developing inside the distro needs the runtime mirror; glob and grep stay slow because the Windows-side ripgrep walks the 9p share, and the README recommends narrowing the path or invoking the tool from bash; shell activity reads unknown when the session is opened inside WSL, and idle reclamation does not run for those terminals. Any change under lib/ requires restarting DSH to clear the ES-module cache, and the project is distributed under the MIT license.