deepseekplugins

DeepSeek Harness plugin

dsh-wsl-bridge

Windows access tools for WSL agents: win_ls/win_read/win_write/win_run/win_open/win_path/win_drives.

Tools & Capabilities
Jump to install

Source facts

Repository
ch1bug/dsh-wsl-bridge
Latest update
Aug 14, 2026
Category
Tools & Capabilities
GitHub stars
1
Format
plugin
Catalog evidence
Upstream dsh.bundle evidence
Evidence path
package.json#dsh.bundle
Checked against
0.1.0-rc.8
Upstream check date
2026-08-20

This evidence comes from the upstream catalog. This site has not installed, run, or security-reviewed the plugin.

Install

Start with a prompt that asks an agent to review the GitHub repository and source. Switch to the command if you want to install it yourself.

Copy this prompt into DSH, Codex, or another agent and ask it to review the GitHub repository and source first.

Do not install or run any commands yet. Read this plugin's GitHub repository, README, and relevant source code. Then answer the questions below clearly and directly so I can decide whether it fits my needs:

1. What is this plugin, and what problem does it solve?
2. Who is it for, and what are its typical use cases?
3. How is it used after installation? Include one minimal example.
4. What known limitations or privacy, security, compatibility, or maintenance risks does it have?
5. Give a clear recommendation: recommend, conditionally recommend, or do not recommend, with reasons.

Distinguish statements documented by the repository, inferences from source code, and unknowns. If evidence is insufficient, say so explicitly. Do not guess or simply repeat the README.

GitHub: https://github.com/ch1bug/dsh-wsl-bridge
Plugin: dsh-wsl-bridge
Author: ch1bug

Check the source files

Read the README and other files from this plugin directory before installing.

File explorer3 files
README.mdSource · read only

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

ToolPurpose
win_lsList a Windows directory (accepts C:\... or /mnt/c/...)
win_readRead a Windows text file (utf8/gbk, line offset/limit)
win_writeWrite UTF-8 text to a Windows file (creates parent dirs)
win_runRun a Windows program (cmd / powershell / direct interop)
win_openOpen a file/folder with the default Windows handler
win_pathConvert between C:\... and /mnt/c/... (wslpath)
win_drivesList 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-in bash 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 per dsh.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.exe reachable — standard on WSL1/WSL2)

  • DSH host with the shell and sandboxPolicy services

License

MIT

Back to searchOpen GitHub repository

More related plugins

View category