173787247/dsh-wsl-env
Inject WSL/Windows path and shell facts into the DeepSeek Harness system prompt.
Injects WSL / Windows path and shell facts into the DSH system prompt so the model stops assuming a Windows shell when the agent actually runs in Linux/WSL. The injected section is deliberately short: the distro name and Linux user, the Linux path mapping (for example C:\Users\... -> /mnt/c/Users/...), CRLF/git caveats on /mnt/c, a preference for the Linux home over the Windows mount for day-to-day work, and NODE_USE_ENV_PROXY=1 for when Node 24 must use HTTP(S)_PROXY.
Install
dsh plugin --profile web add github:173787247/dsh-wsl-envREADME install (the same command accepts a local absolute path: dsh plugin --profile web add /absolute/path/to/dsh-wsl-env). Restart dsh web, then open a NEW session — existing sessions keep the old system prompt. This plugin is part of the dsh-wsl-kit install set; the kit README documents KIT_SET=daily | llm | github | full presets and a TROUBLESHOOTING fault tree.
Compatibility
DSH plugin that injects a short system-prompt section. Non-WSL hosts skip injection by default (when: wsl); set when: always to inject everywhere. Later profile layers that set config replace the whole object, so restate every key you keep (when, order, extraNotes).
Details
- Repo: 173787247/dsh-wsl-env
- Category: Agent Capabilities
- Stars: 0
- Version: GitHub main (README-documented; not published to npm)
- Last push: 2026-08-18
- First seen: 2026-08-18
Recent updates
README documents verification: after installing, send any message and check Trajectory → SYSTEM → System Prompt (not the Tools tab) for Windows Subsystem for Linux — you should see the distro name and path mapping (the UI concatenates sections, so the internal id runtime:wsl-windows may not appear as a heading).
FAQ
- How do I install dsh-wsl-env?
- Run: dsh plugin --profile web add github:173787247/dsh-wsl-env (or point it at a local absolute path), restart dsh web, and open a new session — existing sessions keep the old prompt.
- How do I verify the injection worked?
- Send any message, then open Trajectory -> SYSTEM -> System Prompt (not the Tools tab) and search for Windows Subsystem for Linux; the distro name and path mapping should be present.
- Does it inject on non-WSL hosts?
- No — injection defaults to WSL only (when: wsl); set when: always in the plugin config to inject everywhere. Note that a later config layer replaces the whole object, so restate keys you keep.