dsh-web-tray
DSH 插件：为在 WSL 中运行的 dsh web 提供 Windows 托盘图标和桌面快捷方式——仅支持打开和退出，不含监控程序、配置文件或状态文件（dsh-wsl-tray 的分支）
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-web-tray@0.3.0Web Tray 以 dsh-web-tray 发布，当前版本为 0.3.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
中文 | English
A DeepSeek Harness (DSH) plugin for WSL deployments: a Windows desktop shortcut plus a minimal tray icon with exactly two entries — 打开 DeepSeek Harness and 退出 DeepSeek Harness (which also stops DSH). No watchdog, no idle stop, no configuration file, no status file.
Fork of liyu34/dsh-wsl-tray (upstream
ff03276, v0.1.7, MIT). The upstream architecture — desktop shortcut, hidden tray
helper — is kept; the watchdog, the menu switches and the status monitoring were
removed, and the platform defects below were fixed.
DSH Web on the desktop: DSH inside WSL is started through
start.sh when it is not running (hidden, asynchronous) or reused when it is, and
the browser opens once with this run's ?token= URL.wscript.exe + JScript (no console window):
~/.dsh/dsh-web-tray/stop.sh (hidden, never awaited) and then closes the tray.
stop.sh checks the command line behind the PID file first, so a stale PID file
plus a reused PID cannot kill an unrelated process.CreatePopupMenu look, so the colours and metrics were
measured off both tray icons on the same screen and are reproduced here: dark
#1F1F1F panel 175×97 px, #E3E3E3 labels, #363636 hover, a full-width
#5E5E5E separator, system UI font at 9pt, and DPI-aware scaling. Corners are
Windows 11's own rounding (8 px) instead of the app's 12 px. The constants live in
src/tray-script.ts and tests/tray-menu.spec.ts asserts them through Windows
interop.0.2.0 reduces the tray to Open / Exit and rebuilds the Windows side. Compared with 0.1.0:
netstat sampling and the DSH process facts in /status.tray-config.json and tray-status.json — both are
deleted when the artifacts are regenerated.wscript.exe //E:JScript //B dsh-web-tray.js
instead of a .vbs (VBScript is an on-demand feature since Windows 11 24H2); the old
.vbs is deleted.0.3.0 fixes the Windows side of 0.2.0 and makes two visible changes:
dsh-web-tray-inverted.ico is deleted.tray-shortcut.json records what the desktop shortcut should be — target,
arguments, icon, and the .lnk's own size and digest. A shortcut that was replaced,
restored from a backup or edited by hand is rebuilt instead of being trusted for existing.-Uninstall covers the files older versions left behind, an unhandled error leaves a line
in tray.log instead of failing silently, artifacts are written atomically and
regenerate() is single-flight, ensure() notices leftovers, and the pkill fallback also
covers a globally installed dsh. No manual step: mounting regenerates.WSL_DISTRO_NAME set, or /mnt/c reachable).wscript.exe (JScript), powershell.exe and wsl.exe.# A. official plugin manager — DSH's plugin manager drives pnpm, so pnpm has to be
# on PATH; this plugin never calls pnpm itself
cd /path/to/dsh-web-tray && dsh plugin --profile web add "$PWD"
# B. profile symlink — no pnpm, the path this fork was verified with:
P=~/.dsh/profiles/web
python3 - <<'PY'
import json, os
p = os.path.expanduser('~/.dsh/profiles/web/package.json')
d = json.load(open(p)); b = d['dsh']['profile']['bundles']
if 'dsh-web-tray' not in b: b.append('dsh-web-tray')
json.dump(d, open(p, 'w'), indent=2)
PY
mkdir -p "$P/node_modules" && ln -sfn /path/to/dsh-web-tray "$P/node_modules/dsh-web-tray"
# C. tarball
npm pack && dsh plugin --profile web add ./dsh-web-tray-0.3.0.tgz
All three need a restart of dsh web. On first mount, ensure() writes every
artifact and creates the desktop shortcut. Installing and regenerating are
idempotent: ensure() compares the artifacts, the leftover files of older versions and
the shortcut's own stamp, so nothing is rewritten, no second tray starts and no
PowerShell runs — the only files that grow from normal use are tray.log and
start.log.
Removing a bundle runs no plugin code — DSH has no uninstall hook — so the generated helper carries the cleanup:
# on Windows, before or after removing the bundle:
powershell -NoProfile -ExecutionPolicy Bypass -File "$env:USERPROFILE\.dsh\dsh-web-tray\dsh-web-tray.ps1" -Uninstall
# then, in the profile that has it:
dsh plugin --profile web remove dsh-web-tray
-Uninstall stops any tray started from that directory and deletes the desktop
shortcut, the helper, the launcher, all three icons, tray.log, tray-selftest.json and
the WSL directory (start.sh, stop.sh, start.log, dsh.pid,
project-path.json). It leaves DSH itself running, and running it twice is harmless.
Without it, all of the above stays behind — and keeps working, because the shortcut
and the generated scripts are self-contained.
Installing through DSH's plugin manager adds profile-side files it owns, not the
plugin: dsh-web-tray-<version>.published/ (a packed copy), pnpm-lock.yaml and
pnpm-workspace.yaml. Nothing reads them — the profile resolves the plugin through
its node_modules entry — and dsh plugin remove is what manages that side; delete
them by hand if the profile is to be spotless.
| File | Location |
|---|---|
dsh-web-tray.ps1 (tray helper), dsh-web-tray.js (hidden launcher) | %USERPROFILE%\.dsh\dsh-web-tray\ |
dsh-web-tray.ico (shortcut icon), dsh-web-tray-black.ico / dsh-web-tray-white.ico (tray icon, one ink per taskbar theme) | same |
tray.log (one line per open/exit/error, not rotated) | same |
tray-shortcut.json (what the shortcut should be: target, arguments, icon, .lnk digest) | same |
start.sh, stop.sh, start.log, dsh.pid | ~/.dsh/dsh-web-tray/ |
project-path.json (only when a project path was saved) | ~/.dsh/dsh-web-tray/ |
DSH Web.lnk (targets wscript.exe //E:JScript //B …dsh-web-tray.js) | the Windows desktop |
Running dsh-web-tray.ps1 -SelfTest writes tray-selftest.json (the menu contract,
UTF-8) next to the helper.
~/.dsh/dsh-web-tray.env (optional, chmod 600, one KEY=VALUE per line) is read by
start.sh and exported into DSH's environment — a token for an MCP server, say. The
script only reads it and never creates it; the older, personal
~/.dsh/github-mcp-token is still honoured.
desktop .lnk
└─ wscript.exe //E:JScript //B dsh-web-tray.js
└─ powershell.exe -NoProfile -ExecutionPolicy Bypass -WindowStyle Hidden -File dsh-web-tray.ps1
├─ tray icon + dark rounded context menu (open / exit)
└─ open flow:
probe http://127.0.0.1:3080 (2 s timeout; a 401 counts as alive —
without a cookie DSH answers 401 by design)
alive → open the page (preferring the ?token= URL from start.log)
not alive → wsl.exe -d <distro> -- bash -lc "start.sh" (hidden,
asynchronous, never awaited), then probe every 2 s for up to
120 s and open the page as soon as it answers
wsl.exe … stop.sh
hidden and never awaits it (bWaitOnReturn = $false), then leaves the message
loop. Waiting for wsl.exe on the UI thread is what froze the tray in the old
design. -SelfTest runs the exit handler without the stop switch, so a test run
can never stop a real DSH.FreeConsole) as soon as it enters tray mode, and marks
its menu WS_EX_TOOLWINDOW before the first show. Without those, the process owns a
hidden PowerShell console and its menu is an ordinary unowned top-level window,
which is what makes Windows list the menu as "Windows PowerShell" in the taskbar and
Alt-Tab (and what can surface that console). The command-line flags keep their
console, because they print.--app/--app-id) is preferred, otherwise a normal browser
window whose active tab is DSH. Matching is by title and window class
(Chrome_WidgetWin_1), because a File Explorer window showing the app's folder
carries the same words in its title. A minimized window is restored first — its
resting size comes from GetWindowPlacement, since GetWindowRect reports a 160×28
placeholder for a minimized window — and then brought forward with
SetForegroundWindow, falling back to an attached input queue and then to a synthetic
ALT press, which is what Windows accepts from a process the user is not typing into.
Only when no such window exists does the tray start the WSL instance and open the page
with this run's token. The Electron desktop app is never a candidate: it is a
different program with its own backend, so its window is skipped by process name.
-SelfTest reports what was found, and how many windows were skipped for that reason
(dshWindow, dshWindowIsWebApp, dshWindowsSkippedAsApp, focusReturned).netstat, no status file, no /proc scan. The UI
thread probes the URL once (≤ 2 s) when it is asked to open, and the open flow's 2 s
timer polls for up to 120 s while a DSH it started comes up. Nothing else runs in the
background except one registry read every 5 s for the taskbar theme.Local\dsh-web-tray-single mutex. A second double-click
while the tray runs creates no second tray; that process just opens DSH./dsh-web-tray, loopback + same-origin fence)| Method | Path | Purpose |
|---|---|---|
| GET | /status | platform, the two URLs (web + token), generated files |
| POST | /regenerate | rewrite every artifact and recreate the desktop shortcut |
| GET/POST | /project-path | source checkout path (empty = auto-detect) |
powershell.exe missing from PATH (.wslconfig with
appendWindowsPath = false) → shortcut creation, desktop resolution and profile
resolution all failed. Every mounted drive's absolute
/mnt/<drive>/Windows/System32/WindowsPowerShell/v1.0/powershell.exe is now tried
first and the bare name last: a PATH that does carry Windows still works, and so
does a Windows installed on another drive.Administrator (the first entry in /mnt/c/Users,
not writable) → ask PowerShell for [Environment]::GetFolderPath('UserProfile')
first; the directory scan is a last resort.dsh was rejected by the launcher guard, so nothing was
generated → a dsh on PATH now counts as a usable launcher..vbs, and VBScript
is a Feature-on-Demand now. The launcher is JScript, started as
wscript.exe //E:JScript //B …, which names the engine explicitly. The shortcut
creation probes the engine and only falls back to a hidden powershell.exe when
JScript is missing too; the old .vbs is deleted on regeneration.Get-FileHash then reported "not recognized" while its module listed
itself as loaded, the shortcut stamp was never written, and every mount regenerated
the whole install. The helper now points its own PSModulePath at $PSHOME\Modules
and computes the .lnk digest with .NET.tray.ico uses; the launcher asset draws the same whale at 3/4, which is
why an icon taken from that one looked small next to the app's. Writing the shortcut
invalidates the shell icon cache with SHChangeNotify(SHCNE_ASSOCCHANGED), or
Explorer keeps showing the old art.npm install
npm run typecheck # host and client halves
npm test # 66 tests (30 generated scripts, 12 service lifecycle, 10 real tray menu via Windows interop, 6 icons, 8 wiring)
DSH_WEB_TRAY_REQUIRE_INTEROP=1 npm test # fail instead of skipping when interop is missing
# (10 of the 66 need Windows; the other 56 run anywhere)
npm run build # tsc + tsdown + banner normalisation
npm pack --dry-run
dsh-web-tray.ps1 -SelfTest builds the real NotifyIcon, the real menu and the real
shortcut-target resolution without showing UI, and writes the resulting contract as
JSON. tests/tray-menu.spec.ts runs that through Windows interop and asserts the
entries, the palette and metrics (scaled by the real DPI), the target path, and the tray
icon it picked together with the theme it read; it is skipped where interop is
unavailable. tests/icon-asset.spec.ts pins all three .ico files: size tables, BMP/PNG
rules, the mark's share of its frame and the two inks. tests/service.spec.ts drives the
lifecycle itself — idempotence, an older install's leftovers, a replaced shortcut,
single-flight regenerate — against a temporary home directory and an injected host
bridge, so it needs neither Windows nor WSL.
Verified on WSL2 + Windows 11, 2560×1440 at 100% DPI, dsh 0.2.0-rc.2: typecheck,
tests, build and pack green; the real menu opened, measured and closed again through
the live tray process; double-clicking the real .lnk starts the tray with no console
window; /status returns platform: wsl with every artifact present.
127.0.0.1:19387 on this machine) beside the WSL instance's :3080; the tray
neither focuses nor launches it, and its window is excluded from the reuse match by
process name.bash ~/.dsh/dsh-web-tray/stop.sh does the same by hand.Add-Type source. If that does not compile, the tray
still appears — a system-colour menu, no rounded corners — and writes the reason to
tray.log. Any unhandled error leaves a line there too, because a hidden process
that fails is otherwise indistinguishable from one that never started.src/tray-script.ts. Reproducing Chromium's drawing verbatim
would mean bundling Electron (~90 MB instead of ~125 kB) — the installed desktop app
refuses to host a foreign app path, so there is no free route to it.start.sh launching the CLI: a source checkout must already
be built (start.sh never runs src; when the build output is missing it writes the
reason to start.log). Nothing rebuilds a checkout behind your back.platform: 'unsupported' and starts nothing.stop.sh then finds every
dsh web process with pgrep and kills the ones whose command line really is DSH
(read from /proc, so a grep dsh web of your own is never signalled).Chrome_WidgetWin_1), and that class is not browser-only — QQ, Jitsi Meet and the DSH
desktop app itself draw windows with it. A window only counts as the page if its process
is a browser (a known executable name, or one started with /
, which is how a portable or scoop install identifies itself).git remote -v # upstream = liyu34/dsh-wsl-tray
git fetch upstream && git log --oneline upstream/master ^master
MIT — see LICENSE. The original copyright notice is kept from upstream.
--user-data-dir--profile-directory--app=<url> and share the window
class and the reload chord, so the same code serves all of them. The tray opens the page
in the browser it has already seen the page in (that window's own browser and profile), or
in the default browser when that one is Chromium-like, and only falls back to a plain open
(a new tab) for a non-Chromium default.wsl.exe
reads the raw command line and keeps the quotes WScript.Shell.Run passes, so
-d "My Distro" is read as a distro called "My Distro" and fails with
WSL_E_DISTRO_NOT_FOUND (measured). The name is therefore passed bare, exactly as
WSL expects it.