dsh-plugin-pwsh7
Windows DeepSeek Harness 套件，将 pwsh 工具路由至 PowerShell 7，包含设置页面（安装状态、自检、路由切换、卸载、系统迁移）、用户/系统安装和 PATH 配置、带实时下载进度的 Web 设置对话框，以及支持沙箱环境的执行器。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-plugin-pwsh7@0.3.0Plugin Pwsh7 以 dsh-plugin-pwsh7 发布，当前版本为 0.3.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Windows DeepSeek Harness (DSH) bundle that routes the model-facing pwsh tool to PowerShell 7
(pwsh.exe, major version >= 7) instead of falling back to Windows PowerShell 5.1.
dsh-pwsh-sandbox executor: sandbox modes,
sandbox_permissions escalation, denial/runner-failure facts, background jobs, output caps, and
exit markers. It only replaces executable resolution.shell_router tool reports status, diagnoses
sandbox problems, runs a self-check, switches routing, and removes the plugin-managed copy.pwsh run — with a download button and live progress (bytes, percent, phase). Closing it
never cancels an install, and the next failed run re-opens it.English | 中文说明
On Windows, DSH mounts pwsh-sandbox as ctx.shell, but the resolved executable can end up being
Windows PowerShell 5.1 in some environments. This bundle keeps the stock PowerShell executor and
overrides only its pwshPath resolution:
pwsh-sandbox slot: a DSH patch entry's name asserts the targeted row, it
does not replace it, so the stock row is disabled by id and a RouterPwshExecutor extends SandboxPwshExecutor row (id: pwsh7-executor) is inserted. An explicit config.pwshPath still
wins; otherwise the plugin-resolved PowerShell 7 is used.dsh-plugin-pwsh7 row, which registers the shell_router tool
(status / diagnose / selfcheck / route / uninstall), a small system-prompt section, the
setup dialog/settings routes, and the browser bundle.
That row's name is also what DSH's client-module scanner uses to discover client.js; the
executor row's ./pwsh-executor subpath is not a client-bundle source.@deepseek-ai/dsh-base / Web profile). Tested against
DSH desktop 0.2.1-rc.2.Install from npm through the DSH plugin manager:
plugin_manager action=install_bundle target=dsh-plugin-pwsh7@0.3.0
Or install from a local checkout (a directory install links the checkout, which is convenient while developing):
plugin_manager action=install_bundle target=D:\path\to\dsh-plugin-pwsh7
The new bundle is applied through HMR immediately. After changing the plugin's source, restart DSH to load a fresh module generation.
The model-facing shell_router tool:
| Action | What it does |
|---|---|
status (default) | Resolved PowerShell 7 path and version, config file, current sandbox policy, shipped-package resolution. |
diagnose | Runs real PowerShell 7 commands under the current sandbox policy (version + workspace write) and reports exit codes, stdout/stderr, denial/runner-failure classification, and concrete hints. |
install, relocate | Not performed by the tool. They return guidance: installation is user-initiated only, from the setup dialog, Settings → PowerShell 7, or a manual install. |
selfcheck | Runs the same read-only self-check as the settings page and returns ok / warn / fail lines. |
route | Persists route: "plugin" or route: "system" and reports the new route. |
uninstall | Removes the plugin-managed per-user portable install (files, temporary directory, managed PATH entry) while keeping the routing preference. |
The browser half also registers a PowerShell 7 page in the Web GUI's settings menu
(settings.section). It is read-only until an action is chosen:
Program Files, the per-user Programs
directory, the Store alias, and PATH entries outside the plugin root — and falls back to stock
DSH behavior (Windows PowerShell 5.1) when no system PowerShell 7 exists. The choice is stored as
route in config.json and takes effect for the next pwsh command.PATH entry, shipped-package resolution, sandbox policy, and
a running install, each as ok / warn / fail with details.PATH entry
(administrator required), then removes the per-user copy and points routing at the system
executable. An unelevated DSH host is told exactly what to do instead of hanging on UAC.PATH entry, and leaves
system/package-manager installations untouched.The browser half renders into DSH's root shell.overlay slot, so it works in the ordinary Web GUI
and in the desktop shell without a second window:
pwsh.exe cannot be found, and again every time a pwsh
tool run fails for that reason (missingSeq). "Not now" hides it until the next failed run; a
page reload opens it again while PowerShell 7 is still missing.Download and install starts the shared, user-initiated installation job.
The dialog shows downloading → extracting → verifying, transferred bytes, total, and percent.
Cancel download aborts it.%LOCALAPPDATA%\dsh\pwsh7\tmp. The model's shell_router tool never starts one.GET /pwsh7/state (snapshot), GET /pwsh7/events (SSE, progress coalesced to
~7 frames/s), POST /pwsh7/install, POST /pwsh7/cancel. SSE drives smooth progress; a 3 s
/pwsh7/state poll stays active as the fallback for carriers that buffer event streams.
These routes are same-origin and accept POST bodies only as application/json.Retry, and links to the official
PowerShell releases page. A failed install does not affect pwsh routing until one succeeds.shell_router
status/diagnose/selfcheck and the settings routes when the Web app is composed, but installation
without a browser is a manual step.Resolution order for the pwsh executable:
DSH_PWSH_PATH environment variablepwshPath in %LOCALAPPDATA%\dsh\pwsh7\config.json%ProgramFiles%\PowerShell\7\pwsh.exe%LOCALAPPDATA%\dsh\pwsh7\powershell7\…\pwsh.exe (portable installs, newest first)%LOCALAPPDATA%\Programs\PowerShell\7\pwsh.exePATH entry%LOCALAPPDATA%\Microsoft\WindowsApps\pwsh.exe (Store alias)%ProgramFiles(x86)%\PowerShell\7\pwsh.exeThe stock pwsh-sandbox row still accepts its official pwshPath config field; an explicit config
value takes precedence over automatic detection.
route in config.json selects which executable the pwsh tool runs:
| Route | Resolution |
|---|---|
plugin (default) | DSH_PWSH_PATH → config.pwshPath → well-known locations including the plugin-managed portable install → PATH; missing PowerShell 7 raises the setup hint. |
system | System-installed locations only: Program Files, Program Files (x86), %LOCALAPPDATA%\Programs, the Store alias, PATH entries outside %LOCALAPPDATA%\dsh\pwsh7, then Windows PowerShell 5.1 as the stock last resort. DSH_PWSH_PATH and config.pwshPath are ignored. |
The settings page switches the route at runtime (POST /pwsh7/route); no restart is needed.
%LOCALAPPDATA%\dsh\pwsh7\config.json:
{
"version": 1,
"route": "plugin",
"pwshPath": "C:\\Program Files\\PowerShell\\7\\pwsh.exe",
"installed": {
"pwsh": {
"path": "C:\\Program Files\\PowerShell\\7\\pwsh.exe",
"version": "7.6.7",
"method": "existing",
"scope": "user",
"at": "2026-10-17T00:00:00.000Z"
}
},
"updatedAt": "2026-10-17T00:00:00.000Z"
}
Installation is only started by the user, from the Web setup dialog or Settings → PowerShell 7, or by installing PowerShell 7 outside DSH. The model-facing tool never starts an install.
Choose scope: "user" (default) or scope: "system" in the Web dialog.
| Scope | Destination | Persistent PATH |
|---|---|---|
user | %LOCALAPPDATA%\dsh\pwsh7\powershell7\<version> | Current user (HKCU\Environment) |
system | %ProgramFiles%\PowerShell\7 | System (HKLM environment) |
System installation requires starting the DSH host as administrator; an unelevated host fails before downloading. User installation needs no elevation. Both preserve existing PATH entries and registry value types, avoid duplicate entries, refresh the host process PATH, and notify Windows. Already running terminals may need reopening. PATH write failures are reported as installation failures.
The settings page can migrate an existing per-user install to the system scope in one step
(POST /pwsh7/relocate): it installs/reuses the Program Files copy, writes the system PATH, removes
the per-user copy, and points the config at the system executable.
To install without the Web GUI, install PowerShell 7 yourself (official MSI/Store/release zip) and
set DSH_PWSH_PATH or config.json to its pwsh.exe.
Portable download source:
| Component | Source | Destination |
|---|---|---|
| PowerShell 7 | Latest PowerShell/PowerShell GitHub release, PowerShell-*-win-x64.zip | %LOCALAPPDATA%\dsh\pwsh7\powershell7\<version>\ |
%LOCALAPPDATA%\dsh\pwsh7\tmp, with progress callbacks and
cancellation.tar.exe (bsdtar). No downloaded installer is ever executed.pwsh.exe is executed once to verify a major version >= 7 before it is
written into config.json.auto falls back to winget install Microsoft.PowerShell; when elevation would be required the
result carries the exact manual elevated command instead of hanging on UAC.--scope user or --scope machine; fallback never changes the selected scope.7.6.7.ctx.sandbox.confine() and the Windows ACL restricted-token runner, with
the same workspace-write / read-only / danger-full-access semantics as the stock executor.workspace-write can write inside the workspace
and is denied outside it; danger-full-access is unconfined).SetNamedSecurityInfoW failed (Win32 5) / grantWrite(<workspace>),
the workspace DACL is missing rights. Run DSH's bundled diagnose-windows-sandbox-acl skill
against the workspace root (it backs up and verifies), or temporarily switch the session to full
access.shell_router action="status" and check the resolved path/version.shell_router action="diagnose" to execute real commands under the current sandbox policy.DSH_PWSH_PATH or
the pwshPath config entry, then check status again.DSH_PWSH_PATH or config.json.| Path | Role |
|---|---|
index.js | Bare package row: installs shell_router, the system-prompt section, setup/settings routes, and the reload hook |
client.js | Browser half: shell.overlay setup dialog plus the settings.section PowerShell 7 page, SSE + polling, install/route/uninstall/relocate/self-check actions, en/zh copy |
lib/shipped.mjs | Loads the shipped @deepseek-ai/* packages from the running DSH installation (app.asar) |
lib/paths.mjs | PowerShell 7 detection, version probing, config.json IO |
lib/route.mjs | Routing mode persistence, system-default executable resolution, install description |
lib/install.mjs | User/system-scope portable install (official zip) + winget fallback; progress and phase callbacks |
lib/install-scope.mjs | Registry PATH persistence/removal (preserving value kind), elevation probes, Program Files scope |
lib/state.mjs | Process-wide resolution cache shared by the executor and the tool; missing-run signal |
lib/maintenance.mjs | Removes a plugin-managed per-user portable install (files, temp dir, managed PATH entries) |
lib/selfcheck.mjs | Read-only self-check: executable, version, route, config, install, PATH, shipped packages, sandbox, job, routes |
lib/router-features.mjs | Installs shell_router, the system-prompt section, the setup coordinator, and routes from the bare package row |
lib/setup-service.mjs | Single job coordinator: install/relocate/uninstall/route, progress snapshots, cancel, missingSeq |
lib/setup-routes.mjs | The eight /pwsh7/* routes (state, events, install, cancel, route, uninstall, relocate, selfcheck) |
lib/status.mjs | status / implementations |
package.json files ships only the runtime pieces; test/ stays in the repository.
# Plain Node tests (no running DSH required)
node --test test/*.test.mjs
DSH_PWSH7_NETWORK_TESTS=1 enables the live GitHub release / HEAD checks.DSH_PWSH7_* (APP_ROOT, TAR, NETWORK_TESTS).Releases are published by GitHub Actions through npm Trusted Publishing (OIDC) — no npm token, OTP or repository secret is involved.
version in package.json, commit and push to main.v0.2.0)..github/workflows/publish.yml runs on
release: published, verifies the tag matches package.json, runs the test suite, and publishes
with provenance (npm publish --access public --provenance).One-time npm-side setup (already configured for this repository):
npx npm@12 trust github dsh-plugin-pwsh7 `
--file publish.yml `
--repo drliuhuan/dsh-plugin-pwsh7 `
--allow-publish --yes
Manual dry run: Actions → Publish to npm → Run workflow, keep dry_run checked. The workflow
then runs npm publish --dry-run --provenance without publishing.
Only publish.yml in drliuhuan/dsh-plugin-pwsh7 is authorized to publish. Inspect or revoke the
relationship with:
npx npm@12 trust list dsh-plugin-pwsh7
npx npm@12 trust revoke dsh-plugin-pwsh7 --id <trust-id>
0.1.0 was the first public release. 0.1.1 is the first release published through npm
Trusted Publishing (OIDC) by GitHub Actions, and fixes the npm-hosted README cross-links.
0.2.0 adds the Web setup dialog and moves installation into one shared coordinator. 0.2.2 adds
user/system installation scopes with persistent PATH. 0.3.0 adds the settings page with self-check,
route switching, user-scope uninstall, and migration to the system scope.
Earlier internal iterations (0.2.x/0.3.x) included MSYS2 bash routing and used a different package
name; that scope was removed because MSYS2/Cygwin cannot start under the DSH Windows ACL sandbox.
The historical evidence stays in the build workspace (sandbox-recon/FINDINGS.md), not in this
package.
To remove the plugin and restore DSH's native preset:
plugin_manager action=remove_bundle target=dsh-plugin-pwsh7
pwsh then returns to DSH's default resolution. The per-user directory
%LOCALAPPDATA%\dsh\pwsh7\ is not deleted automatically by the plugin manager; use
Settings → PowerShell 7 → Uninstall (or shell_router action="uninstall") first if you also
want to remove the plugin-managed PowerShell 7 installation and its managed PATH entry.
MIT — see LICENSE.
diagnoselib/executors/pwsh.mjs | PowerShell 7 executor (extends the official SandboxPwshExecutor), branches on the route |
cordis.patch.yml | Bundle patch: disables the stock pwsh-sandbox, inserts the executor and bare package rows (Windows only) |
locale/en.json, locale/zh.json, icon.svg | Plugin-manager display metadata |