T-Auto/dsh-dpx

dsh-dpx is a multi-environment package manager built specifically for DeepSeek Harness (DSH); it creates, installs, discovers, and launches named, mutually isolated DSH environments on a single machine. The project explicitly states it is not a DSH plugin and does not modify DSH core or the plugin protocol; instead it ships as an npm package installed globally via npm install -g dsh-dpx (or invoked through npx dsh-dpx --help) and can also be built locally with git clone https://github.com/T-Auto/dsh-dpx.git followed by npm link. Each registered environment owns an independent npm global prefix, download cache, DSH_HOME, DSH_AGENTS_HOME, working directory, and a self-describing dsh-distribution.json descriptor that implements the DistributionDescriptor, ManagedLayout, and EnvironmentDiscovery faces of the dsh-distribution meta-protocol.

The typical workflow starts with dpx npm install -g @deepseek-ai/dsh @deepseek-harness-tui/dsh-tui --test --"D:\DevEnvs\Projects", which scaffolds a brand-new environment named test (ASCII letters, digits, hyphens; must begin with a letter) inside the parent directory supplied via the second --"path" argument. After creation, operators inspect state with dpx env list, dpx env show --test, dpx env doctor --test, dpx which --test, and dpx descriptor --test; registry corruption, duplicate names, instance-identity conflicts, or missing roots trigger fail-closed behaviour rather than automatic rescans or rebuilds. On Windows the first creation also drops a double-clickable DSH DeepSeek Harness Desktop.exe showing a minimal black-and-white splash (DSH / DeepSeek Harness Desktop / 隔离环境：<名称> / 正在启动本地 DSH 服务…) before loading that environment's DSH Web UI inside a bundled WebView2 control; --no-desktop opts out, and macos/linux hosts always remain pure CLI. Launching the in-environment TUI is currently done with dpx run --test dsh-tui, since a global dsh-tui --test adapter must still be merged into the separate dsh-tui project.

Dependencies are deliberately narrow: Node.js >=22.19.0 is the only runtime requirement, and the project is labelled experimental with Windows as the priority target. Isolation is a per-directory npm/DSH partitioning rather than an operating-system sandbox, so npm package lifecycle scripts still execute with the current user's privileges and untrusted packages must not be treated as a safe execution environment. The repository ships with npm test, npm run check, and npm run pack:check, all of which use temporary directories and a fake npm binary without downloading upstream packages or touching real DSH profiles. The descriptor can be validated offline using the dsh-distribution conformance CLI (node ..\dsh-distribution\packages\conformance\lib\cli.js "$PWD\dsh-distribution.json"), and the Windows discovery pointer HKCU\Software\DSH\DPX is purely a non-executable location hint for compatible managers. Cleanup uses dpx env remove --test to unregister while preserving the root, and dpx env remove --test --purge to delete a registry-validated environment root; neither command removes global Node/npm, default DSH directories, or other environments. The license field is not declared in the repository metadata, which should be checked before redistribution.