MIT native DSH plugin for Windows+WSL: GUI WSL workspaces, pipe-backed bash in the distro, 9P file tools with sandbox fences, in-distro grep/glob, and optional `wsl_terminal` for interactive prompts.
DSH integration
Native runtime
Author-claimed
Safety audit
Unaudited
Last verified
2026-11-20
License
MIT
01What can it help you accomplish?
Run a DeepSeek Harness agent session against Linux project files inside a local WSL distribution
Bash commands and `read`/`write`/`edit` on Linux paths in the chosen distro, without installing `dsh` inside WSL
Windows users who develop in WSL and want DSH shell and file tools to operate natively on Linux paths
Reach Windows files from a WSL workspace session when the agent needs cross-filesystem access
Windows paths exposed under /mnt/c-style drive mounts while bash stays inside the distribution
Developers who keep code in WSL but still reference Windows-side assets or configs
Register a WSL-backed workspace from the DSH web UI with a verified Linux root path
A new session opened on "Create & open" where the model sees Linux paths and mode picker WSL variants
DSH web users who add workspaces from the GUI instead of only Windows-native folders
02How to install into DeepSeek Harness
Prerequisites
- A Windows host with at least one local WSL distribution (README routes tools through `wsl.exe` and /mnt drive mounts)
- DSH web profile available so you can run `dsh plugin --profile web add` and restart `dsh web`
Installation steps
- 01
Pick an install path: run `dsh plugin --profile web add dsh-wsl-workspace`, or add the GitHub repo URL, or add a local clone path (README lists all three)
$ dsh plugin --profile web add dsh-wsl-workspace
- 02
Restart `dsh web` after adding the plugin
$ dsh web
- 03
In Workspaces, click the W button or choose Add WSL workspace, select a distribution, set an absolute Linux path (use Check to verify), optionally set a Linux username, then click Create & open
Verify the integration
- After restarting `dsh web`, a W button appears in the Workspaces section header beside the add-workspace control
03DSH integration and capability boundaries
Cordis plugin installed with `dsh plugin --profile web add`; adds a W button in the web GUI to create WSL workspaces whose sessions route bash and file tools into a chosen local distribution.
WSL workspace picker in the web GUI
Chosen WSL distribution, absolute Linux workspace path, optional Linux username→A WSL-bound workspace session with Linux paths in the model context
Persists per-workspace username in wsl-workspaces.json under the DSH home directoryStateful bash inside the distribution
Shell commands for the configured Linux user (empty uses the distro default, often `root`)→Command stdout/stderr and exit codes from a long-lived bash inside WSL
Spawns and keeps `wsl.exe` bash processes; `cd`, env vars and background jobs persist between callsRuns with Linux-side permissions — not wrapped by the Windows ACL sandboxFile read/write/edit via the WSL 9P share
Linux paths for `read`, `write`, and `edit`→File contents and edits as seen on the WSL side; sidebar paths stay Linux-shaped
Uses the Windows-side WSL 9P share — the workspace username field does not change file-tool identity`write`/`edit` honor `ctx.sandboxPolicy` writableRoots like the host backendgrep and glob inside the distribution
Search patterns and paths under the Linux tree→Ripgrep-shaped grep output and sorted glob listings from GNU grep/find in WSL
Runs search inside the distribution, not on the 9P share; does not read `.gitignore` for grepInteractive terminal door (`wsl_terminal`)
open/send/read/signal/close actions for programs that need a TTY (sudo password, ssh fingerprint, editors)→PTY-backed terminal I/O typed by the agent; keystrokes become part of the conversation record
Uses the host PTY registry pointed at this plugin's relay; anything typed (including passwords) is logged in the session
04Who is it for? When not to use it?
Good for
- Windows users who develop in WSL and want DSH shell and file tools to operate natively on Linux paths
- Developers who keep code in WSL but still reference Windows-side assets or configs
- DSH web users who add workspaces from the GUI instead of only Windows-native folders
Not for
- Targets a Windows host with local WSL: bash and searches run inside a distribution via `wsl.exe`, and Windows files appear under /mnt drive mounts.
- The bash tool runs on the Linux kernel side with the configured user's distro permissions; the Windows ACL sandbox cannot wrap `wsl.exe`, so DSH file policy does not apply to bash commands.
- File tools use the Windows-side WSL 9P share and still fence `write`/`edit` with the host `writableRoots` sandbox; symlink resolution can block outside writes under `workspace-write`.
- Only the DSH releases listed in `dsh.compatibility.dshReleases` are verified; other versions may work but are unverified, and unsupported generations fail loudly at runtime.
05Compatibility, maintenance and safety notes
- Targets a Windows host with local WSL: bash and searches run inside a distribution via `wsl.exe`, and Windows files appear under /mnt drive mounts.
- The bash tool runs on the Linux kernel side with the configured user's distro permissions; the Windows ACL sandbox cannot wrap `wsl.exe`, so DSH file policy does not apply to bash commands.
- File tools use the Windows-side WSL 9P share and still fence `write`/`edit` with the host `writableRoots` sandbox; symlink resolution can block outside writes under `workspace-write`.
- Only the DSH releases listed in `dsh.compatibility.dshReleases` are verified; other versions may work but are unverified, and unsupported generations fail loudly at runtime.
- Optional per-workspace Linux usernames are stored locally in wsl-workspaces.json under the DSH home directory on the Windows host.
MIT · last push 2026-11-07 · release v0.7.13
06Frequently asked questions
Do I need to install DSH inside WSL?
No. README states nothing needs to be installed inside WSL — you add the plugin on the Windows host, pick a distribution in the GUI, and the session routes bash and file tools into that distro.
How do bash permissions differ from file tools?
Bash runs inside WSL as the configured Linux user and can read/write anywhere in the distro; Windows ACL sandbox cannot wrap `wsl.exe`, so DSH file policy does not apply to bash. File `read`/`write`/`edit` go through the Windows-side 9P share and still honor `writableRoots` sandbox fencing.
Which DSH versions are supported?
The README lists releases verified in isolated instances (mirrored in `package.json` `dsh.compatibility.dshReleases`). Versions outside the list may work but are unverified; a host exposing neither supported API generation fails loudly.
Can the agent reach Windows files from a WSL workspace?
Yes. While bash stays in the distribution, Windows files remain accessible via /mnt/c-style paths. The plugin also translates some Linux sidebar addresses back to Windows UNC paths for previews.
What does the optional username field do?
It sets which Linux user runs bash commands (like `wsl.exe -u` with a named user). It does not change file tools, which always use the 9P share. Usernames are stored in wsl-workspaces.json under DSH home; delete the entry or recreate the workspace to revert to the distro default.
07Related DSH workflows
ds-harness-remote
by liguobao
Lets authorized desktop, web, and Android clients operate a remote Harness host.
dsh-windows-mcp
by hellohub1212
Windows desktop automation for DeepSeek Harness: the in-box MCP client bridge mounted against CursorTouch/Windows-MCP, with an off-by-default Computer Use switch and an in-app dependency installer.
dsh-desktop
by anywhere-labs
Modern desktop client for the DeepSeek Harness (dsh) plugin ecosystem. Everything is a plugin — even the desktop shell itself.
dsh-go
by ccch1mneyyy
Run DeepSeek Harness on your phone and remotely control your desktop from a native Android app.
08Data and sources
Add a WSL workspace from the DeepSeek Harness web GUI and run the whole agent session — bash commands and file reads/wri…
Nothing needs to be installed inside WSL.
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-11-20. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.
