Plugin directory / Automation / dsh-wsl-bridge
dsh-wsl-bridge
Verified · install-tested on dsh ch1bug
What it does
Windows access tools for WSL agents: win_ls/win_read/win_write/win_run/win_open/win_path/win_drives as a DeepSeek Harness bundle
Works — verified, early-stage project
Windows access tools for WSL agents: win_ls/win_read/win_write/win_run/win_open/win_path/win_drives as a DeepSeek Harness bundle It installs cleanly and boots without issues in our testing. It's early-stage but functional.
“Verified” means our automated CI actually ran dsh plugin add in a clean profile and it booted — nothing more. Feature descriptions and version compatibility are the author’s claims. This is not a security audit and not an endorsement of third-party code.
README
wsl-bridge
DSH (DeepSeek Harness) Cordis plugin that lets an agent running inside WSL
(Windows Subsystem for Linux) access and invoke Windows-side files and
programs.
Built for agents that live in WSL but need the Windows host: read/write files
on C:\, run .exe programs, open things in Explorer, list drives, convert
paths.
Tools
| Tool | Purpose |
|---|---|
win_ls |
List a Windows directory (accepts C:\... or /mnt/c/...) |
win_read |
Read a Windows text file (utf8/gbk, line offset/limit) |
win_write |
Write UTF-8 text to a Windows file (creates parent dirs) |
win_run |
Run a Windows program (cmd / powershell / direct interop) |
win_open |
Open a file/folder with the default Windows handler |
win_path |
Convert between C:\... and /mnt/c/... (wslpath) |
win_drives |
List mounted Windows drives |
Optional (when codebase-memory-mcp is installed):codebase_search, codebase_arch — knowledge-graph code search.
How it works
Everything runs through the host shell service (the same seam the built-inbash tool uses) with the calling session's sandbox policy applied per call.
Path normalization handles both C:\Users\me and /mnt/c/Users/me forms.win_run writes temp .bat/.ps1 files to C:\Windows\Temp and cleans up
after itself; PowerShell output is forced to UTF-8 console encoding.
Install (DSH bundle)
Standard DSH bundle — install with the official plugin command (auto-inits
the profile, pnpm-installs, and appends the bundle layer perdsh.bundle.patch):
dsh plugin --profile web add /path/to/dsh-wsl-bridge
# or: dsh plugin --profile web add github:you/dsh-wsl-bridge
# Restart dsh web; the tools mount automatically.
Dependencies are declared as peerDependencies (ecosystem convention —@deepseek-ai/dsh-tools is already loaded in the DSH process). Optional env
vars at apply time: CODEBASE_MEMORY_BIN for the codebase-memory tools
(default /usr/local/bin/codebase-memory-mcp; they error if absent).
Requirements
- WSL with Windows interop enabled (
cmd.exe,powershell.exe,wslpath,explorer.exereachable — standard on WSL1/WSL2) - DSH host with the
shellandsandboxPolicyservices
License
MIT
Install
Install the catalog once, then DeepSeek Harness can find and install any plugin from this site automatically:
dsh plugin add dshbase-catalog Then say "install dsh-wsl-bridge for me" — your agent finds it in the directory and installs it. Docs: dshbase-catalog · verified packs.
This plugin is GitHub source (not published to npm) — install it straight from the repo:
Web profile:
dsh plugin --profile web add github:ch1bug/dsh-wsl-bridge Headless (CLI) profile:
dsh plugin --profile headless add github:ch1bug/dsh-wsl-bridge Test report
Verified: L1 install + L2 load + L3 runtime from GitHub source on dsh 0.1.0-rc.6.
When to use it
Automate a repetitive job — scheduling, chaining tasks, or reacting to events — so it runs without you starting it.
Who it's for
Users with recurring work who want it cron-style and hands-off rather than manually triggered.
For developers — extending it
Triggers and task templates are the seams — add event-driven or file-watch triggers, and richer workflow composition.