AI Agent Hub
Back to plugins
⚙️

dsh-plugin-multi-root-workspace

Workflow Updated 2026.09.16

Run the following command in DeepSeek Harness:

dsh plugin install cherrchen/dsh-plugin-multi-root-workspace

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

Run dsh plugin install cherrchen/dsh-plugin-multi-root-workspace in DeepSeek Harness to install this plugin (source: https://github.com/cherrchen/dsh-plugin-multi-root-workspace)

About this plugin

A real project is rarely one repository: front-end, back-end, and shared libraries each live in their own Git repo, yet DSH natively treats only the session working directory as the sole writable root. Every time an Agent needs to cross a repository boundary, the developer has to switch sessions and re-explain context—a tax that compounds fast in large codebases. dsh-plugin-multi-root-workspace extends the writable scope from a single canonical directory to one main root plus N additional roots, while Agents keep using the native read / write / edit / bash tools with zero new interfaces to learn.

On the safety side, multi-root authorization rides the same kernel-level mechanism as upstream (macOS Seatbelt, Linux bwrap or Landlock). fs and bash/PTY share one scope; the plugin never degrades to prompt-level constraints or blanket full-access. With no additional roots configured, behaviour is identical to the unpatched baseline; a misconfiguration produces a loud error, never a silent fallback. v0.1.1 adds a cross-process Registry Authority Lease so that two DSH processes sharing a single $DSH_HOME grant additional roots to only the lock holder, while the other fails closed.

Who it is for: DSH users working with front-end / back-end separation, micro-services, or multi-repo monorepos. If you find yourself repeatedly switching directories and re-describing project structure inside Agent sessions, a one-time install brings the entire project topology under a single hardened sandbox. Supported runtimes are DSH 0.1.5-rc.2 and 0.1.6-alpha.1; full coverage on macOS and Linux, with fs write-path coverage on Windows.

Use Cases

  • Agent reads, writes, and runs bash across separate front-end and back-end repos in one session
  • Multiple micro-service repositories operated inside a single Workspace without switching contexts
  • A shared library and business code modified together during integration, all under one additional-root sandbox

Best For

  • Engineers who use DSH for day-to-day multi-repository work
  • Agent users on teams built around front-end / back-end separation or micro-services
  • Developers who want one session to span the full project topology without manual directory switching