DeepSeek Harness Plugin Hub

Publish and manage complete Harness Profiles. Discover Plugins for your next setup.

Explore

PluginsPresetsDocsNews

Community

Publish a pluginContactReport an issue

Resources

Plugin Hub on GitHubDeepSeek HarnessSystem statusPrivacy notice
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

Independent and unofficial. Not affiliated with, authorized by, or endorsed by DeepSeek.

Wsl Portproxy — DSH Plugin for DeepSeek Harness
DeepSeek Harness Plugin Hub
ProfilesPluginsCategoriesNewsDocsSign inManage Profiles
ProfilesPluginsCategoriesNewsDocsSign in
← Plugins
W

dsh-wsl-portproxy

Wsl Portproxy

WSL port expose advisor; local UI uses :3081/?token= on dsh ≥0.1.2.

The plugin will be installed here. Keep web if you are unsure.

npx -y @deepseek-ai/dsh plugin --profile web add github:173787247/dsh-wsl-expose#d731e529bce9e050b4a7ef378e67e3cc497b563c
READMECompatibilityVersions

Compatibility and provenance

Wsl Portproxy is published as dsh-wsl-portproxy and currently resolves to version 0.2.2. The Hub verifies its manifest and preserves the exact installation source for reproducible installs.

DSH compatibility
*
Runtime surfaces
any
Release source
github
Registry updated
10/9/2026

Versions

0.2.2stable
10/9/2026

Related plugins

Loading related plugins…

Latest
0.2.2
DSH
*
HMR
Process restart
Tree shaking
Safe tree shaking not declared
Unpacked size
Unavailable
Files
Unavailable
Surface
any
License
MIT
Source
github
GitHub
★ 1
Weekly downloads
0
Last push
10/9/2026
View source ↗
README badge

Click the badge to copy Markdown for your README.

Do you maintain this Plugin?Claim benefit · Priority security scan

Verify the GitHub repository declared in package.json to manage this listing. After you claim it, Hub will prioritize a security scan of the current version and publish the result when it passes.

Claim this Plugin →
Report an issue

Related plugins

More verified plugins in security-access.

Experimental Auto Review@deepseek-ai/dsh-experimental-auto-reviewPer-tool LLM authorization review for the DeepSeek Harness Auto permission presetCc Safety Netcc-safety-netA coding agent CLI hook - block destructive commands and secret file accessDoctor@linxin666/dsh-doctorTransactional rescue mode for DSH profiles with a supervised launcher, isolated recovery capsule, deterministic repairs, health monitoring, and a local Web recovery consolePocketdsh-pocketPut DeepSeek Harness in your pocket: one package, one settings page, and scan a QR code on your phone to access DSH on your computer in sync (LAN + public network, real-time screen mirroring).

README

dsh-wsl-expose

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.

中文说明 → README.zh.md

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

FieldValue
Plugindsh-wsl-expose 0.2.2
Minimum dsh≥ 0.1.2 (web UI one-shot ?token= on Windows relay :3081)
Latest verifiedSee dsh-wsl-kit Compatibility (currently 0.2.0-rc.2) — single source of truth for the suite
Kit setllm / full (some also useful alone)
Cloud FlashUse model id deepseek-flash (V4.1 Flash) in ~/.dsh/settings.yaml / llm-deepseek — not configured by this plugin
Agent TeamsUpstream 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”:

GoalDo this
Chat UI on this Windows boxkit restart-dsh-web.sh → printed URL on :3081?token=…
Expose a dev server to LANwsl_expose (allowlisted ports) after you understand firewall risk
Bind dsh on 0.0.0.0Never — 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 notes
  • wslconfig_hint — mirrored vs NAT

Test

npm test

License

MIT