dsh-wsl-launch

When working inside WSL with a DeepSeek model, asking the agent to open VS Code, Explorer, or a browser is a high-frequency need. But handing raw .exe execution to a model shatters the security boundary overnight. dsh-wsl-launch locks down what can be launched behind an explicit allowlist, so the agent can only touch a handful of pre-approved apps and everything else is refused by default.

The core capability is a single tool called win_launch. It accepts a target (an executable name or Windows path that must match the allowlist) and an optional args string. The default allowlist covers everyday tools such as code, explorer.exe, notepad.exe, wt.exe, msedge.exe, chrome.exe, and firefox.exe. To extend it, drop entries into config.allowlist using exact names, path suffixes, or prefix wildcards. It ships as part of the dsh-wsl-kit suite and pairs cleanly with dsh-wsl-open: the latter handles file opening, while this one handles app launching.

Who is it for? Developers who frequently reach into the Windows side from WSL for dev tooling, and who want