Advises or applies allowlisted Windows portproxy for a WSL listen port, preferring the kit :3081 relay and launch token for local dsh UI.
Install
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:173787247/dsh-wsl-expose
Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).
README
Install set: part of dsh-wsl-kit. Prefer
KIT_SET=llm|full. Fault tree: TROUBLESHOOTING.md.
DeepSeek Harness tool wsl_expose: advise or apply Windows portproxy so LAN clients can reach a service listening inside WSL. Reads .wslconfig networkingMode.
Where it sits
Advises how a WSL port is reached from Windows or the LAN. Local chat still uses :3081/?token=.
flowchart LR
agent["dsh agent"] --> tool["wsl_expose"] --> port["WSL port to Windows or LAN"]
Suite diagram and version snapshot: dsh-wsl-kit. This plugin is 0.2.2 (full; also in llm). Do not copy that matrix into this README.
Compatibility
| Field | Value |
|---|---|
| Plugin | dsh-wsl-expose 0.2.2 |
| Minimum dsh | ≥ 0.1.2 (web UI one-shot ?token= on Windows relay :3081) |
| Latest verified | See dsh-wsl-kit Compatibility (currently 0.2.0-rc.2) — single source of truth for the suite |
| Kit set | llm / full (some also useful alone) |
| Cloud Flash | Use model id deepseek-flash (V4.1 Flash) in ~/.dsh/settings.yaml / llm-deepseek — not configured by this plugin |
| Agent Teams | Upstream experimental; not required here |
Suite floor versions: kit check-plugin-versions.sh. Fault tree: TROUBLESHOOTING.md.
Scope: LAN / non-local portproxy only. Local dsh UI should use kit relay :3081 + token, not netsh portproxy to expose 3080.
Why
Phone / another PC on the LAN sometimes needs a Windows-published port that forwards into WSL. That is different from “open dsh in the local Windows browser”:
| Goal | Do this |
|---|---|
| Chat UI on this Windows box | kit restart-dsh-web.sh → printed URL on :3081?token=… |
| Expose a dev server to LAN | wsl_expose (allowlisted ports) after you understand firewall risk |
Bind dsh on 0.0.0.0 |
Never — dsh must stay on 127.0.0.1:3080 |
Under NAT-mode WSL, Windows localhost forwarding can be flaky; mirrored networking changes the story — the tool reports networkingMode so you do not guess.
Install
# With LLM / full kit:
curl -fsSL https://raw.githubusercontent.com/173787247/dsh-wsl-kit/master/install.sh | KIT_SET=llm bash
# Or alone:
dsh plugin --profile web add github:173787247/dsh-wsl-expose
Restart dsh web, open a new session. Tool: wsl_expose.
Related tools
port_doctor— is something listening?check-dsh-health.sh— 3080/3081 + token noteswslconfig_hint— mirrored vs NAT
Test
npm test
License
MIT
Links
More in this category
6Mikao9/dsh-wsl-workspace★ 85
Add a WSL workspace from the web GUI without needing to install dsh or related tools again inside WSL. Bash commands and file read/write operations run within the local WSL distribution on the host machine, while Windows files remain accessible.
173787247/dsh-wsl-open★ 3
Opens WSL Linux paths from DeepSeek Harness chat in the Windows default app or Explorer.
liyu34/dsh-wsl-tray★ 3
Windows desktop shortcut and system-tray launcher for DSH running in WSL, with fully hidden startup, tray open/restart/exit menu, and a plugin-configuration card to manage the shortcut.
173787247/dsh-wsl-env★ 2
Injects WSL distro, Linux path mapping, /mnt/c CRLF and git caveats, and NODE_USE_ENV_PROXY into the system prompt.
173787247/dsh-wsl-net★ 2
Adds a net_doctor tool that reports proxy environment, NODE_USE_ENV_PROXY, and reachability of the DeepSeek API and the npm registry, and sets NODE_USE_ENV_PROXY on bash and npm child processes.
Edge-Echo/dsh-win-toolkit★ 2
Windows-native tools for DSH agents: clipboard read and write, system notifications, hosts file inspection and network diagnostics, each returning structured data with UI cards from injection-safe PowerShell.
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.