Fixes the Windows workspace-open action: the shipped opener spawns explorer.exe with windowsHide, so the File Explorer window is created invisible and the click reports success without appearing.
Install
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:King20260919/dsh-open-folder-visible
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
Windows fix for DSH: makes the Session-header "open workspace in File Explorer" action raise a visible window.
The problem
The Session header has an "Open In…" split button whose default action opens the
session's workspace directory in File Explorer (also bound to Ctrl+Alt+O).
On Windows, clicking it starts Explorer, creates the correct directory window — and that window is invisible. The button settles back to idle and reports nothing, so the click looks like it did nothing at all.
Why
The shipped explorer catalog entry in @deepseek-ai/dsh-host-open-in-app is
kind: 'shell-open', which on Windows ends at @deepseek-ai/dsh-native-command:
execFile('explorer.exe', ['<file:// URI>'], { encoding: 'utf8', signal, windowsHide: true })
windowsHide: true exists to suppress the transient console window a CLI child
would flash. Applied to Explorer it means the window is created with
IsWindowVisible() false.
Upstream judges the launch by exit code alone, and Explorer's exit 1 counts as a
delegated handoff (runExplorer), so the route answers { ok: true } whether or
not a window ever became visible.
Measured
Same host, same call shape, only the flag differs:
| Call | New window | IsWindowVisible() |
|---|---|---|
windowsHide: true (shipped) |
1 | false (6/6, still false 9 s later) |
windowsHide: false |
1 | true (6/6) |
The fix
The Host half adds one route, POST /open-folder-visible/open, that spawns the
same explorer.exe with windowsHide: false. Everything else mirrors the
shipped opener: an argv array (never a shell string), Explorer's exit 1 accepted
as a delegated handoff, and a watch window so a launcher still running is counted
as launched rather than killed.
The browser half wraps globalThis.fetch and reroutes only the file-manager
launch to that route. Everything else — every other application, every other
request on the page — is passed through untouched.
What this deliberately does not do
It does not replace the split button. The shipped button, its application
menu, its icons, its per-gesture feedback and the Ctrl+Alt+O shortcut
(workspace.openLocal) all stay exactly as they are. Replacing the component
would mean re-registering that shortcut, and forgetting to is how a "fix" ends up
removing the hotkey.
Install
dsh plugin --profile web add github:King20260919/dsh-open-folder-visible
Installing any plugin runs third-party code with your own permissions. Pin a
commit if you want a fixed revision:
github:King20260919/dsh-open-folder-visible#<sha>.
Restart DSH after installing: the Host half registers a route at load time.
Configuration
| Field | Default | Meaning |
|---|---|---|
launchWatchMs |
1500 |
Early-failure watch window for the explorer.exe handoff. Launch success is decoupled from process exit, because Explorer exits as soon as it has asked the running shell to raise the window. |
Known limitations
- Windows only. On other platforms the route answers
501; nothing else changes. - This fixes the workspace-open action only. The file-location action
("reveal in File Explorer",
explorer.exe /select,<file>, used by the delivered-file cards and the changed-files review) is affected by the samewindowsHideflag through a different code path (@deepseek-ai/dsh-api-session-controller→revealNativePath), and is not covered here. - It reroutes one request by wrapping
globalThis.fetch. If a future release changes the shipped launch route or the request body shape, the reroute simply stops matching and the shipped behaviour returns — the wrapper never breaks the original request.
License
MIT
Links
More in this category
6Mikao9/dsh-wsl-workspace★ 124
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.
XINY11451/dsh-wsl★ 14
Extends the working range of DSH into WSL. Files in the distribution can be read, written, edited and searched by DSH directly. Depending on the task, the AI chooses for itself: run a one-off command, or open its own terminal and run several commands there to finish the job. Typing `dsh` in a WSL terminal calls DSH (type `dsh help` there for details), fusing WSL and DSH deeply. Every terminal you open can collaborate visually with the AI.
Edge-Echo/dsh-win-toolkit★ 4
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.
Han-1413141/dsh-wsl-native★ 4
Use Windows and native Linux DSH sessions in one Windows window, with WSL environment switching and bidirectional system tools.
stallenlu/dsh-wsl-suite★ 4
WSL workspaces for DeepSeek Harness. A sidebar W button lists installed distros and registers a Linux folder as a host workspace addressed by a UNC path, and the sidebar terminal opens a real Linux pty inside the distribution for WSL sessions. A persistent zero-dependency agent running in the distro answers file, shell and search requests over a JSON-lines pipe, so no polling timers touch the distribution while it is idle and /mnt drives stay reachable from tools and the terminal (registering one as a workspace is refused, because the host realpaths workspace paths and Windows cannot resolve drvfs); grep and glob run the distro's own ripgrep. WSL preset twins such as wsl-standard swap in the WSL shell and fs tools. A rebuild of 6Mikao9/dsh-wsl-workspace — do not install both: they mount the same W entry in the Workspaces header, publish the same wsl-<mode> presets, and each wrap the host's single-slot terminal provider.
173787247/dsh-wsl-env★ 3
Injects WSL distro, Linux path mapping, /mnt/c CRLF and git caveats, and NODE_USE_ENV_PROXY into the system prompt.
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.