AI Agent Hub
Back to plugins
⚙️

dsh-workspace-overlay

Workflow Updated 2026.08.24

Run the following command in DeepSeek Harness:

dsh plugin install TTTPOB/dsh-workspace-overlay

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

Run dsh plugin install TTTPOB/dsh-workspace-overlay in the DeepSeek Harness terminal; the full source repository is at https://github.com/TTTPOB/dsh-workspace-overlay .

About this plugin

In DSH multi-workspace, multi-agent workflows, resources such as configurations, tools, and MCP connections often end up scattered across individual sessions with no unified ownership or lifecycle boundary. dsh-workspace-overlay addresses this by providing a shared Cordis scope per canonical workspace path: every session and agent in the same workspace lease that scope, and it is fully disposed only when the last lease is released, eliminating resource leakage and half-updated state.

Around that shared scope the plugin layers three core capabilities. First, top-level config mounting and hot-reload — on initial acquire the system resolves /.dsh/cordis.yml and builds a composition subtree; afterwards, saving the file triggers a strictly serial full-tree swap where tools, prompt sections, MCP connections, and every other workspace contribution are torn down and remounted atomically, so partial updates never surface. Second, Agent integration — workspace binding is wired before ctx.agents.create/resume, and the official agentPresets mount pipeline is decorated into workspace-local preset generation, placing every agent inside its own workspace-isolated view. Third, a workspace-aware MCP process manager: global lines share one process per serverName, workspace override lines spawn their own process with local cwd and env, inherited lines add zero extra processes, same-name namespaces are masked as a whole rather than mixed, and process lifecycles stay strictly aligned with workspace leases.

If you are building multi-workspace agent pipelines on DSH and need config changes to take effect within seconds, MCP server processes to start and stop in lockstep with their workspace, and clean namespace isolation between workspaces, this plugin is purpose-built for that job.

Use Cases

  • Isolate agent runtimes and tool namespaces per workspace in a multi-workspace DSH project
  • Hot-swap tools, prompts, and MCP connections instantly after saving the top-level cordis.yml without a restart
  • Start and stop MCP child processes at workspace granularity with whole-namespace masking for same-name servers

Best For

  • Developers building multi-workspace agent pipelines on DSH
  • Platform engineers coordinating MCP server lifecycles and tool visibility across workspaces
  • Application teams that need config changes to propagate instantly without half-updated state