AI Agent Hub
Back to plugins
🖥️

dsh-plugin-gitbash

Client Updated 2026.08.23

Run the following command in DeepSeek Harness:

dsh plugin install Jinsight-gif/dsh-plugin-gitbash

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

Run dsh plugin install Jinsight-gif/dsh-plugin-gitbash in DeepSeek Harness; the source lives at https://github.com/Jinsight-gif/dsh-plugin-gitbash. Restart the profile after installation to mount the gitbash tool.

About this plugin

When working with DeepSeek Harness inside WSL or a dual-boot setup, the agent session is stuck on the Linux side and cannot touch the Windows host git repositories, native executables, or paths like D:\ or C:. dsh-plugin-gitbash fills that gap: it is a self-contained, zero-dependency Cordis plugin that registers a single gitbash tool with DSH, letting the model run commands directly in the Git for Windows Bash on the Windows host without switching terminals or leaving the current session.

Every call spawns a fresh, non-interactive Git Bash process with stdin bound to /dev/null, so interactive prompts can never hang the shell. The working directory is transparently mapped between WSL and Windows path conventions, recognising /mnt/d/..., d:/..., and D:... interchangeably. The plugin ships with automatic bash.exe detection across ProgramFiles, every mounted drive, and PATH, and when no path resolves at mount time it re-runs resolution on every call, so installing Git for Windows or mounting a drive takes effect without a DSH restart. Per-profile timeout, output truncation, and other configuration knobs keep production deployments predictable.

It is aimed at developers who work across a WSL and Windows dual environment and want their agent to manage Windows-side git operations or run native Windows scripts, especially when staying inside a single DSH agent workflow without constantly hopping between WSL and Windows terminals is a hard requirement.

Use Cases

  • Managing Windows-side git repositories directly from a WSL DSH session without switching terminals
  • Running Windows-native executables or scripts with D:\ or C:\ path conventions
  • Completing Windows-side tasks within a single DSH agent workflow on a dual-boot setup

Best For

  • Developers working in a WSL + Windows dual environment who need agent-managed git on the Windows side
  • DSH users who want their agent to invoke Windows host tooling transparently
  • Teams that want to minimize terminal switching between WSL and Windows while keeping a focused workflow