AI Agent Hub
Back to plugins
🖥️

dsh-msys2-bash-executor

Client Updated 2026.08.15

Run the following command in DeepSeek Harness:

dsh plugin install 3223698962/dsh-msys2-bash-executor

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install 3223698962/dsh-msys2-bash-executor in the DeepSeek Harness terminal to install this plugin; the source is available at https://github.com/3223698962/dsh-msys2-bash-executor .

About this plugin

On Windows, DeepSeek Harness routes agent shell calls through PowerShell by default. Developers whose workflows lean on MSYS2, UCrt64 toolchains, or Git Bash need a first-class Bash path with its own timeout, abort, and output-spill guarantees. dsh-msys2-bash-executor provides exactly that: a standalone, isolated Bash executor mounted at the Host layer that spawns bash via DSH's managed subprocess service using raw argv, never touching Node's shell: true flag.

A bilingual (English / Chinese) configuration card lives in the DSH Web settings page, letting you point at any bash.exe, set launch arguments, prepend PATH entries, inject environment variables, and toggle activation per preset. You can enable Bash globally across every preset or restrict it to Standard, Code, Cordis, Minimal, or any custom preset ID. When Minimal is enabled, the plugin shadows the built-in persistent-terminal tool with a standalone definition, sidestepping the unsupported terminal-inspection path on win32 and giving the agent a clean, stateless shell per call.

This plugin is best suited for engineers who drive AI agent coding or ops tasks on Windows through DSH and rely on Unix utilities such as grep, awk, or make, or who need a UCRT64 cross-compilation environment. Because the executor is unsandboxed—commands inherit the full privileges of the DSH process—enable it only in trusted repositories and with vetted prompts.

Use Cases

  • Running Unix toolchain tasks (grep, awk, make) from a DSH-driven AI agent on Windows
  • Configuring an isolated Bash invocation path for UCRT64 cross-compilation
  • Enabling or disabling Bash per preset to replace the default PowerShell executor

Best For

  • Windows developers whose daily workflow depends on MSYS2 or Git Bash
  • Engineering teams that need a Unix environment inside AI-agent coding or ops tasks
  • Advanced DSH users who want fine-grained per-preset shell visibility control