dsh-wsl-workspace: Seamless WSL Workspace Support for DeepSeek Harness

6mikao9/dsh-wsl-workspace

Development & OperationsVerified
Listed on 2026-08-20
Page last updated 2026-08-20

Add WSL workspace support to DeepSeek Harness, letting you run agent sessions inside WSL without installing dsh there.

Let the DeepSeek Harness web GUI add WSL workspaces directly, running full sessions in a local distribution without installing dsh inside WSL.

install
dsh plugin --profile web add github:6mikao9/dsh-wsl-workspace
Category
Development & Operations
Platform
DSH-Plugin
Author
6mikao9
Distribution
Plugin

dsh-wsl-workspace Key Features

Add WSL workspace from GUIRun bash inside WSLFile tools use Linux pathsOptional Linux usernameNo dsh install inside WSL

dsh-wsl-workspace Repository

6mikao9
Publisher
6mikao9
Repository
6mikao9/dsh-wsl-workspace
24
Stars
4
Forks
0
Watchers
1
Open issues
LanguageTypeScript
LicenseMIT License
Website
Repo last push2026-08-16 15:45:59
Repo created2026-08-14 21:21:23
Topics
dshdsh-plugindsh-plugins
Default branchmain

dsh-wsl-workspace Repo Summary

dsh-wsl-workspace is a WSL workspace plugin (DSH plugin) for DeepSeek Harness, maintained by 6Mikao9 under the MIT license, last updated in 2026-08. It solves the problem of running DSH sessions inside a local WSL distribution on Windows without needing to install dsh inside WSL. Once installed, you can add a WSL workspace directly from the DSH web GUI, and run the entire agent session—bash commands and file reads/writes—inside the WSL distribution with Linux paths. The session can reach both WSL and Windows simultaneously: bash commands run inside the WSL distribution, while Windows files remain accessible via /mnt/<drive> (e.g., /mnt/c/Users/...). Core capabilities include adding WSL workspaces from the GUI, selecting distributions, verifying paths, specifying a run user, and automatically mapping the four modes (Standard, PTC, Minimal, Creative) to their WSL variants.

What core features does the dsh-wsl-workspace DSH plugin support?

This plugin offers the following key features:

  • WSL workspace management: A W button appears at the sidebar foot (beside Settings) in the DSH web GUI. Clicking it opens the "Add WSL workspace" dialog, where you can pick a distribution, browse the directory tree, or type an absolute Linux path (e.g., /home/me/proj), and use the Check button to verify the path exists before creating the workspace.
  • User identity control: The username field is optional; leaving it empty runs commands as the distribution's default user (often root), while specifying a username is equivalent to wsl.exe -u <username>, affecting only the bash tool's run identity—file tools are unaffected.
  • Session mode mapping: The mode picker (Standard, PTC, Minimal, Creative) automatically lands on their WSL variants, with bilingual entries (e.g., WSL · Standard mode(标准模式)).
  • Path and file access: All paths seen by the model are Linux paths, and Windows files remain reachable under /mnt/<drive>.

How do I install dsh-wsl-workspace?

There are three ways to install this DSH plugin (choose one), then restart dsh web:

bash
# 1) npm package
 dsh plugin --profile web add dsh-wsl-workspace

# 2) GitHub repository (ships the prebuilt lib/, no local build required)
 dsh plugin --profile web add https://github.com/6Mikao9/dsh-wsl-workspace

# 3) Local directory (development / self-hosted)
 dsh plugin --profile web add D:\path\to\dsh-wsl-workspace

After restarting, a W button appears beside Settings at the sidebar foot.

How do the bash and file tools behave differently in dsh-wsl-workspace?

  • bash tool: Runs inside the WSL distribution as the configured username (empty = the distro default user), so it can read and write anywhere in the distro. Because the Windows ACL sandbox cannot wrap wsl.exe (its children run on the Linux kernel side), WSL itself is the isolation boundary, and the DSH file policy does not apply to bash.
  • File tools (read/write/edit): Go through the Windows-side WSL 9P share and run under the DSH file policy. Under workspace-write, reads work anywhere but writes are restricted to the session workspace; switch to danger-full-access to allow writes outside it. The username field does not affect the file tools.

What is the license and attribution of dsh-wsl-workspace?

This plugin is MIT-licensed, as detailed in LICENSE and NOTICE. The NOTICE precisely lists adapted/inherited source code: DeepSeek Harness (MIT) — dsh-bash-local (executor mechanics), dsh-fs-local (WslFileSystem subclasses it), and the shipped agent presets (read and transformed by the variant generator); design references (no source copied) include dsh-bash-terminal (MIT, wsl argv / WSLENV approach) and dsh-side-panel.

Which DeepSeek Harness versions and platforms does dsh-wsl-workspace support?

This plugin targets Windows and requires the DeepSeek Harness web GUI (dsh web). It depends on official packages such as @deepseek-ai/dsh-fs, @deepseek-ai/dsh-fs-local, @deepseek-ai/dsh-shell, @deepseek-ai/dsh-subprocess, and @deepseek-ai/dsh-timeout, ensuring seamless integration with the DSH ecosystem. The plugin is written in TypeScript, currently has 6 stars and 3 forks, with no open issues.

View more DSH plugins at dsh-plugin.org

DSH-Plugin FAQ