dsh-ops

What it solves

• DSH repeatedly failing on PowerShell under Windows, wasting tokens, time and model attention. The plugin ships its own bash 5.3.15 and PowerShell 7.6.6; resolution order is toolkit → bash → PowerShell 7, preferring bash and falling back to pwsh7 without changing system PATH or the default terminal (Windows only).
• Oversized tool definitions in the system prompt: Rust-based read/search/replace tools are disclosed progressively, shrinking fixed declaration cost, while keeping the same sandbox and permission model as DSH (Windows/Linux/macOS).
• Heavy escaping burden for multi-line scripts: write long scripts to a file and pass script_path, instead of embedding heredocs in tool-call JSON.
• No managed long-running processes: background jobs for simulations, training and other long tasks.

Main capabilities

• File tools: ops_inspect_local_file, ops_grep, ops_glob, ops_replace (using DSH native sandbox/subprocess boundaries).
• Command execution: ops_bash (short commands via command, long scripts via script_path, strict argument validation).
• Background hosting: ops_run_background, ops_job_output, ops_job_list, ops_job_kill (off by default).
• PTC enhancements (0.3.0, off by default, must be enabled explicitly): ops_batch safe batching and ops_result bounded references/projections.
• Per-component toggles: dsh-ops-bash & powershell 7, dsh-ops-file, dsh-ops-background, dsh-ops-ptc; disabling a component withdraws its prompt text and tools, and nothing is written to AGENTS.md.

Author benchmarks: about 97% token reduction versus the stock Windows standard mode, and about 65% versus the stock Linux PTC mode when using the PTC-specific tools.

Who it’s for

• DSH users on Windows fighting PowerShell errors and escaping problems.
• Heavy users who care about token cost and total task time, or need tight control over prompt footprint.
• Anyone needing managed background jobs (research simulations, model training, long-running services).

Install and caveats

• Search dsh-ops in the plugin marketplace, or run npx --yes dsh-ops@latest install --profile desktop|web|tui (an explicit profile is required); the official dsh plugin --profile ... add dsh-ops also works.
• The first two components are enabled by default; background and PTC require explicit enablement and a native worker.
• Key config: enableShellTools, publishBashTool, promptPolicy, toolCallTimeoutMs, shellPolicy, allowSystemShellFallback; unknown keys are rejected by name.
• Limitations: legacy components target Windows x64; the 0.3.0 PTC component must be built and enabled manually, Linux/macOS have only passed compile checks with on-device and sandbox acceptance still pending, and bugs are possible.
• License: MIT AND Apache-2.0 (with vendor/fastctx/ under Apache-2.0); bundled bash/PowerShell payloads are distributed under their respective upstream licenses.