dsh-subprocess-win32

Windows support bundle for DeepSeek Harness. It is a DSH Cordis bundle, not a Codex plugin. The runtime and Loader identity are subprocess-win32; that is also the name shown in DSH's plugin inventory.

What is included

• A Windows-aware replacement for the stock local subprocess runtime. It supplies the process-inspection and Windows teardown seams required by DSH terminal tools, and keeps the replacement limited to process.platform === 'win32'.
• Minimal (Windows): a Minimal-aligned Agent preset with persistent Git Bash and str_replace_editor.
• Anchored Standard (Windows): a low-resident Standard preset. Its first request exposes only the Minimal pair; after promotion it keeps the pair plus dev_tool_search, skill_search, and skill_load, unlocking heavier tools on demand.
• An explicit PowerShell lifecycle manager for setup, diagnostics, updates, rollback, and complete uninstall. There is no post-install script and no silent PATH or permission change.

The bundle was tested against the Windows native DSH 0.1.0-rc.6 layout with Node.js 24 and Git for Windows. It is a source release on GitHub; it is not published to npm by this repository.

Runtime plugin versus Agent preset

subprocess-win32 is the actual Cordis runtime plugin. It can be enabled or disabled in DSH's plugin list. The two Windows modes are user Agent presets that ship alongside it. A preset can disappear from the selector when its preset files are removed or its host profile no longer mounts them; disabling the runtime plugin does not turn a preset into a different kind of plugin.

The standalone repository dsh-anchored-standard-windows contains only the Anchored preset and is intentionally not a second Cordis bundle.

Relationship between the two repositories

Repository	DSH object	Role	Can it run alone?
dsh-subprocess-win32	Cordis runtime bundle	Registers subprocess-win32, supplies the Windows subprocess seams, and carries both managed preset sources	Yes, as the runtime plugin; the presets are optional
dsh-anchored-standard-windows	User Agent preset package	Supplies only the Anchored Standard composition and its tests	No; Windows use requires dsh-subprocess-win32

For the managed installation, install or update the first repository and let its lifecycle manager render both Minimal (Windows) and Anchored Standard (Windows). You do not need to clone the second repository unless you want to inspect, test, or distribute the Anchored preset independently. The second repository never replaces the runtime plugin. Conversely, installing only the runtime plugin does not force you to use Anchored Standard; you can select Minimal, Standard, or neither.

Install in another DSH profile

Prerequisites:

1. Windows x64, Node.js 22.19+ (24 LTS is recommended), Git for Windows, and a working DSH installation.
2. A profile whose bundle list can load local packages.

Clone this repository, then add the local package to the profile. On DSH builds that expose the plugin command, the usual form is:

dsh plugin --profile web add C:\src\dsh-subprocess-win32

If the installed CLI does not provide add, add the package as a local dependency in that profile's package.json and add dsh-subprocess-win32 to dsh.profile.bundles, then run the profile's package-manager install. Do not put the package in the DSH core release directory.

The bundle patch disables the stock subprocess row only on Windows and inserts subprocess-win32. On Linux and macOS the stock row remains unchanged.

For the managed layout created by the Windows installer, the explicit lifecycle entry point is:

$setup = "$env:LOCALAPPDATA\DeepSeekHarness\setup\dsh-subprocess-win32.ps1"
& $setup -Action doctor
& $setup -Action setup -PackageSource C:\src\dsh-subprocess-win32

After setup, start a new empty session and select Minimal (Windows) or Anchored Standard (Windows). Existing sessions retain their original Agent composition.

Updating and rolling back

Core DSH updates and this bundle's updates are deliberately separate. Keep the current package directory and install a new source tree beside it; do not replace the active directory in place. Before applying a change, run:

& $setup -Action doctor
& $setup -Action update -DryRun -PackageSource C:\src\dsh-subprocess-win32

Only apply the update after reviewing the manifest and test results:

& $setup -Action update -PackageSource C:\src\dsh-subprocess-win32
& $setup -Action rollback

The manager backs up the DSH profile, keeps the previous package, and restores the active pointer and profile files on failure. It does not automatically update third-party DSH bundles or Codex plugins.

Complete uninstall

Preview first, then confirm the destructive operation in an elevated PowerShell only if Windows asks for it:

& $setup -Action uninstall -DryRun
& $setup -Action uninstall

The managed uninstall reads its install manifest, stops only registered DSH processes/tasks, removes the two DSH presets and the dedicated %LOCALAPPDATA%\DeepSeekHarness root, and performs a residue audit. It does not delete project source, .agents\skills, .codex\skills, Codex plugins, Codex MCP configuration, or other Edge applications. Use the manager's export option when you need a backup before removal; do not delete the root manually while a host process is running.

Windows limitations and safety

• Git/MSYS Bash can exit with 0xC0000142 when DSH's restricted workspace-write token is applied to this Windows process tree. The full-access validation passed; the package does not widen permissions, bypass approval, or silently select danger-full-access.
• The Windows fallback cannot provide Linux landlock; treat command output as untrusted and keep the DSH approval policy enabled.
• The Minimal alignment is about the model-visible schema and prompt surface. It is not a claim that Windows is a Linux kernel or that every workload will have identical latency, caching, or completion rate.
• Do not copy Codex .codex-plugin manifests into this package. Codex plugins, DSH Cordis bundles, Agent presets, Skills, and MCP definitions use different loaders. Only explicitly compatible SKILL.md and MCP Tools configurations may be shared.

Development

Use the Node runtime from your DSH installation (or Node 22.19+):

npm test

The tests cover preset phase gating, context suppression, tool discovery, compaction recovery, and the Windows subprocess adapter. They do not claim that the host's model provider, API key, or sandbox policy is configured.

References and acknowledgements

This project is an integration and Windows adaptation. It is not affiliated with DeepSeek, OpenAI, or the upstream maintainers.

• DeepSeek Harness, including the official preset, Skills, Cordis bundle, and MCP designs.
• sjh9714/dsh-win32, fixed source commit f8a68a9836b84fdfec5c1f36ab60cea9923c689f, for the Windows subprocess direction.
• xiaobright/dsh-anchored-standard, fixed source commit f57a1bde2dbaba3039bdae8631f78a0cb3ae3ebe, for the two-phase Agent preset idea.
• Anchored Standard issue #24, which documents resolving tool schemas in the current Agent scope.

Thanks to the DeepSeek Harness and community contributors for publishing the runtime seams, preset experiments, tests, and issue reports that made this Windows package possible. See NOTICE for license and provenance details.