dsh-ops: Windows Command Execution and High-Performance Tools for DeepSeek Harness

What Does It Do?

T-Auto/dsh-ops is a DSH plugin for DeepSeek Harness that gives Windows users an independent bash and PowerShell 7 execution layer plus a set of Rust-based high-performance tools. It solves the token, time, and model-attention waste caused by repeated PowerShell failures and mixed shell syntax on Windows. Commands are routed in the order toolkit → bash → PowerShell 7, so general commands, builds, Git, and pipelines run in bash while only genuinely native Windows operations use pwsh. It supports Windows x64 only, targets DSH 0.2.0-rc.2, is maintained by T-Auto, and ships under a combined MIT and Apache-2.0 license.

Core Features

• Bundled bash: ships bash 5.3.15 for general commands, builds, Git, pipelines, and scripts, with errors fixed inside bash instead of switching shells.
• Bundled PowerShell 7: ships PowerShell 7.6.6 and reuses the host pwsh tool for necessary native Windows operations.
• Rust-powered tool suite: batch text, encoding, PDF and hex inspection, regex search, multi-pattern path lookup, cross-file replacement, and bounded command output with background job management.
• Three-layer routing policy: injects a compact routing description by default, with extraGuidance available for additional instructions.
• Configurable switches: control shell tool publishing, ops_bash publishing, RPC timeout, whether activation is refused when the runtime is unavailable, and whether host shells are denied.
• Session-scoped permissions: command and background job tools are only published in full-permission sessions, and jobs are isolated per session and connection.

How to Use This Plugin?

After enabling it in DSH, the plugin takes over command execution in the order toolkit → bash → PowerShell 7: general commands, builds, Git, and pipelines go to the bundled bash, native Windows operations go to the bundled PowerShell 7, and batch reading, searching, and replacing go through the Rust tools. To adjust behavior, edit the dsh-ops entry in the DSH configuration editor and save the config; unknown keys are reported by name. Common options include enableShellTools, publishBashTool, promptPolicy, toolCallTimeoutMs, required, and shellPolicy, while binaryPath and bashPath usually need no configuration. Command and background job tools are only published when the session has full access (danger-full-access), and they are published or withdrawn as permissions change, so re-check permissions before calling. Note that the file tools are not wired into the restricted file backend and ops_replace has no workspace confinement, and images should still be handed to the host read_image.

How to Troubleshoot This Plugin?

• Model requests fail because the ops_bash parameter schema lacks an object root: this is a known issue after installing from the official marketplace, fixed in the current patch release, so update to the latest patch per the official instructions.
• The plugin refuses to activate because the runtime is unavailable: check the required option, which decides whether activation is refused when the runtime is missing; binaryPath and bashPath can be set explicitly, and an unusable path errors out instead of silently switching executors.
• Command tools do not appear: confirm the session has full access and check the enableShellTools and publishBashTool switches, since both still require full access to publish.
• Host shells are being denied: shellPolicy defaults to advise, and setting deny-host-shell rejects the host shells in deniedHostTools while also disabling the third pwsh layer, so enable it carefully.
• Background jobs cannot be reclaimed after a disconnect: jobs are isolated per session and connection, so old tasks cannot be reclaimed after a disconnect, and uninstalling or downgrading does not guarantee that already-started persistent background tasks are terminated, so handle your own tasks first.