Probes nvidia-smi and GPU visibility inside WSL.
Install
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:173787247/dsh-wsl-gpu
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=daily|llm|github|full(see kit README). Fault tree: TROUBLESHOOTING.md.
DeepSeek Harness tool: gpu_doctor — WSL nvidia-smi, VRAM pressure, Blackwell/5080 hints, and whether Ollama / vLLM / Unsloth Desktop ports compete on one GPU.
Part of dsh-wsl-kit.
Where it sits
Reports nvidia-smi, Blackwell hints, and whether an inference port is already taken.
flowchart LR
agent["dsh agent"] --> tool["gpu_doctor"] --> gpu["nvidia-smi / VRAM"]
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-gpu 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.
Why
Local inference needs the Windows NVIDIA driver to expose GPUs into WSL2. On a single ~16GB card (e.g. RTX 5080), opening Ollama and llama-server and vLLM at once is a common OOM path. This tool reports visibility, VRAM, and open inference ports together.
Install
curl -fsSL https://raw.githubusercontent.com/173787247/dsh-wsl-kit/master/install.sh | KIT_SET=llm bash
# or:
dsh plugin --profile web add github:173787247/dsh-wsl-gpu
Ask: “Run gpu_doctor” after driver updates, CUDA build failures, or before loading another large GGUF.
What you get
- Parsed GPU rows: name, driver, VRAM used/total, util, compute capability
- Blackwell / RTX 50 tips (
sm_120, CUDA 12.8+/13.x) - Inference port scan:
11434/1234/8000/8080 - Pointers to
host_reachanddocker_doctor focus=vllm
Config
- id: dsh-wsl-gpu
name: dsh-wsl-gpu
config:
timeoutMs: 20000
probeTimeoutMs: 1200
probeInference: true
Test
npm test
License
MIT
Links
More in this category
6Mikao9/dsh-wsl-workspace★ 81
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.