Tools & Capabilities

dsh-wsl-port

173787247/dsh-wsl-port · ★ 1

173787247

DeepSeek Harness tool: diagnose WSL port listening and Windows localhost forwarding.

Repository Source

License: MIT
Added: 2026-10-30
Maintenance: active
Install kind: github

Manifest details

Manifest status: Declared
Manifest path: package.json#dsh
Manifest checked: 2026-10-30T09:38:02.320Z
Lifecycle scripts: None found

Static manifest checks report declarations only; they are not compatibility or security review.

安装

dsh plugin --profile web add 'github:173787247/dsh-wsl-port#6456c9e33dda8ef9203754d7b8ae9d039c03337c'

GitHub 源码安装：首次需按提示配置 allowBuilds 构建授权后重试

For install and environment setup, plus plugin development tutorials, see DSH community docs ↗

README

Source README · body: en · Read Chinese README

Table of contents

Where it sits
Compatibility
Why
dsh UI ports (3080 vs 3081)
Install
Config
Test
License

Install set: part of dsh-wsl-kit. Prefer KIT_SET=daily | llm | github | full (see kit README). Fault tree: TROUBLESHOOTING.md.

DeepSeek Harness tool: port_doctor — report WSL IPs and whether a TCP port is listening; advise on Windows localhost forwarding.

Part of dsh-wsl-kit.

中文说明 → README.zh.md

Where it sits

Diagnoses which process owns a WSL port. The Windows chat URL is :3081/?token=, not bare :3080.

flowchart LR
  agent["dsh agent"] --> tool["port_doctor"] --> ports["WSL listeners and :3081 relay"]

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-port` 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.1-rc.5`) — 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: port_doctor for listen state + Windows localhost tips. For dsh UI use 3080 (WSL) and relay 3081 (Windows) with launch ?token= (dsh ≥0.1.2). Do not bind dsh web --host 0.0.0.0.

Why

A server bound in WSL may be reachable as http://127.0.0.1:<port> from Windows—or may need the WSL eth IP / a firewall fix / wsl --shutdown. This tool checks hostname -I and ss listen state.

Default port: 3080 (common dsh web port). Override with the port argument.

dsh UI ports (3080 vs 3081)

Port	Where	Role
3080	WSL `127.0.0.1`	`dsh web` itself — do not open from Windows unless mirrored
3081	Windows relay	Browser entry; needs `?token=` on dsh ≥0.1.2

Ask for port_doctor on both when the UI is blank / ERR_CONNECTION_*. Prefer kit restart-dsh-web.sh + check-dsh-health.sh before inventing netsh rules. For LAN exposure see dsh-wsl-expose — not for local chat UI.

Install

dsh plugin --profile web add github:173787247/dsh-wsl-port

Config

- id: dsh-wsl-port
  name: dsh-wsl-port
  config:
    timeoutMs: 15000
    defaultPort: 3080

Test

npm test

License

MIT

README

Where it sits

Compatibility

Why

dsh UI ports (3080 vs 3081)

Install

Config

Test

License

Related plugins

dsh-weknora

treg

dsh-anchored-standard

Deepseek-Harness-EAC

DSHA-dshapp

deepseek-harness-remote