dsh-subprocess-inherit-environment

By default, DeepSeek Harness (DSH) scrubs sensitive variables from child process environments: any entry whose name contains KEY, PASSWORD, SECRET, or TOKEN, along with DSH_* prefixed names, is removed before the subprocess starts. This credential isolation protects most workloads, yet it also blocks tools that legitimately depend on the full parent environment, such as certain MCP servers, package installers, or CLI utilities.

The dsh-subprocess-inherit-environment plugin wraps the three ctx.subprocess operations (resolveExecutable, spawn, spawnTerminal) and injects a complete copy of the current process.env as an explicit environment layer on every call. Caller-supplied entries are merged after a fresh spread of process.env each time, preserving the original semantics of explicit overrides and undefined tombstones without mutating the caller object. Upon disposal the plugin restores the original method descriptors, so any later wrapper still delegates correctly to the native DSH implementation.

This plugin is well suited for developers and researchers running trusted, single-user environments where CLI tools, MCP servers, or installer scripts need access to the full parent environment. A critical caveat: once loaded, any child process spawned through ctx.subprocess can read API keys, tokens, passwords, and other secrets. In shared deployments, untrusted repositories, or multi-user setups, prefer an exact variable allowlist or a dedicated isolation mechanism instead of forwarding the entire environment.