AI Agent Hub
Back to plugins
🧰

dsh-workspace-git

Web Tools Updated 2026.08.25

Run the following command in DeepSeek Harness:

dsh plugin install leonardoxr/dsh-workspace-git

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

Run dsh plugin install leonardoxr/dsh-workspace-git in your terminal to install this plugin; the source code is available at https://github.com/leonardoxr/dsh-workspace-git .

About this plugin

Bootstrapping a Harness workspace from a remote repository used to be a two-step detour: clone in a terminal first, then go back and pick the folder in the UI. dsh-workspace-git collapses that into a single interaction inside the existing Add workspace dialog. Alongside the original Existing folder tab, a new Clone Git repository tab lets you enter the repository URL, a parent directory, and a folder name, then hands the finished path straight back into Harness standard workspace-creation flow.

The clone runs on the host side via a direct git clone call, never through a shell, and always inside a private staging directory. If the clone fails, the staging area is simply discarded, so an existing destination is never overwritten or removed. Interactive Git prompts are disabled to prevent hung requests, and two tunable knobs are exposed for constrained environments: a clone timeout (default 10 minutes) and a cap on captured Git output returned on failure (default 64 KiB). SSH agents and credential helpers you have already configured continue to work as-is.

This plugin is best suited for developers who regularly bootstrap Harness workspaces from shared team repositories or open-source projects and want to turn the fetch-and-create cycle into a single click without losing context.

Use Cases

  • Pull code from a shared team repository and open it as a new workspace in one click
  • Clone and create a workspace entirely within the Web UI without switching to a terminal
  • Automatically discard the staging directory on failed clones, leaving existing folders untouched

Best For

  • Harness developers who frequently bootstrap workspaces from remote repositories
  • Teams that want to minimize switching between terminal and Web UI
  • Tech users who prefer a one-stop, low-friction workflow