dsh-plugin-wsl-env: Run DeepSeek Harness Sessions Inside a WSL2 Distro

What Does It Do?

Big-Dao/dsh-plugin-wsl-env is a DSH plugin for DeepSeek Harness that runs a harness session against a WSL2 distro instead of Windows. It solves the split where commands land on cmd.exe, file tools only see Windows paths, and the folder picker cannot reach Linux directories. With it enabled, commands execute in your distro's login shell, the model's file tools read and write real distro files, and the GUI terminal opens inside the distro, confined by bubblewrap. Maintained by Big-Dao under the MIT license, it targets Windows + WSL2 only.

Core Features

• Commands run inside the distro: they use your login shell, so PATH, nvm, cargo, pyenv and rc files all apply rather than a hardcoded bash.
• File tools hit real Linux files: read/write/edit/glob/grep work through the \wsl.localhost\ share, and /mnt/c/… still reaches the Windows disk.
• One folder picker lists the Windows home plus every installed distro, so a session can open paths like /home/you/project.
• The terminal opens inside the distro: New terminal in the right sidebar starts a shell as your distro user in the session's folder, not cmd.exe in a UNC directory.
• bubblewrap sandboxing: commands are confined inside the distro and fail closed when bubblewrap is missing.
• The wsl agent preset is bound at session creation, so the very first tool call is already correct.

How to Use This Plugin?

After enabling it in DSH, open a folder under \wsl.localhost\ from the GUI (the picker lists every distro at its root level), or press New terminal; the session workspace, the shell's working directory and the terminal all follow that folder. Commands run as wsl.exe inside your distro, and the model learns its shell through DSH_WSL_DISTRO, DSH_WSL_SHELL and DSH_WSL_HOME. To check it works, ask the model to run uname -r for a WSL2 kernel or echo $WSL_DISTRO_NAME. Permissions behave as on a Linux host, switching between read-only, workspace-write (default) and danger-full-access; a denied command returns an escalation hint, and an approved escalation runs that one call unconfined. Install bubblewrap inside the distro as the official instructions require, and override any row by id in your own profile layer.

How to Troubleshoot This Plugin?

If every command fails closed, the distro is most likely missing bubblewrap; install that dependency inside the distro as the official instructions describe. If edits to lib/ in a checkout seem to have no effect, a running process is caching ES modules, so restart the app to pick up the new code.