Per-workspace activation control: a dialog opened from the workspace row menu switches individual plugins, MCP servers, and skills on or off, and the host applies the choice in that workspace's own agent scope — a disabled skill leaves the model catalog, an MCP server has its mcp__<server>__ tools denied, and a plugin has the tool names its entry declares denied.
Install
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:liaoyuqing/dsh_workspace_switch
Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).
README
Per-workspace activation control for DeepSeek Harness: each workspace decides which plugins, MCP servers, and skills its sessions may use, and a dialog on the workspace row edits that decision.
English | 中文
What it does
Two halves, one plugin:
- Host half (
index.js, built tolib/index.js) reads the per-workspace configuration when an Agent is created and applies it to that Agent's own Cordis scope, so two Agents in two workspaces inside one harness process see different capabilities:- a disabled skill is shadowed in that scope by a same-name non-invocable registration, which removes it from the model's skill catalog;
- a disabled MCP server has every
mcp__<serverName>__*tool denied in that scope; - a disabled plugin has the tool names its entry declares denied in that scope. The same half serves the configuration routes the dialog uses.
- Browser half (
src/client/, built tolib/client.js) adds one row to a workspace's...menu. It opens a dialog listing what the running composition offers under each category, with a switch per capability.
A workspace with no entry inherits the deployment's composition unchanged, so the plugin changes nothing until a workspace is configured.
Configuration
Two sources describe one workspace, in increasing precedence:
<DSH_HOME>/workspace-switch.json, whoseworkspacesmap is keyed by workspace directory;<workspace>/.dsh/workspace-switch.json, which replaces the shared entry for that workspace when it exists.
{
"workspaces": {
"E:\\my_project\\godot-game": {
"plugins": { "mcp-godot-ai": { "enabled": false, "tools": ["mcp__godot-ai__run"] } },
"mcp": { "godot-ai": { "enabled": false } },
"skills": { "godot-scene-authoring": { "enabled": false } }
}
}
}
enabled: false switches a capability off for that workspace; an absent entry
means enabled. A plugin entry also declares the tool names the plugin
registers — the gate denies tools by name, so a plugin without tools has
nothing to deny.
The dialog writes the document that currently answers for the workspace: the project file while one exists, the shared store otherwise. Output is published through a temp-file rename, so a reader never sees a half-written document.
Install
The plugin is a DSH bundle: add it to a profile and select it.
dsh plugin add link:/path/to/dsh_workspace_switch
then add dsh-workspace-switch to the profile's dsh.profile.bundles. A new
bundle row loads at the next harness start.
Build
The browser half is a DSH client bundle and must be built; the repository
toolchain is required (the plugin vendors its copy of the client build preset at
scripts/tsdown.client.ts, which resolves the harness sources from the checkout
it sits in).
# from a deepseek-harness checkout
pnpm exec tsdown --config dsh_workspace_switch/tsdown.config.ts # or, inside the plugin: pnpm build
pnpm exec tsc -p dsh_workspace_switch/tsconfig.typecheck.json # typecheck the browser half
node --test "tests/**/*.test.js" # unit tests
lib/ is committed. The package's main and ./client both point into it,
and a clone has neither the harness sources nor a build toolchain, so a
build-from-source install (dsh plugin add github:…) would otherwise install a
package with no entry points. Commit the rebuilt files with any change that
alters them.
A standalone clone cannot run the build: the vendored preset imports the harness
sources (../../packages/…, ../../scripts/…) that only exist inside a
checkout. Build inside the checkout, then commit lib/ here.
Known limitations
- Skills are gated, not unloaded — a disabled skill keeps its files on disk; only its catalog entry and loading are removed for that workspace.
- A plugin needs declared tools — the gate denies tools by name, so
switching a plugin off only removes what its entry names in
tools. - The dialog lists what the Host can address — plugin rows come from the profile's plugin manager (or the read-only inventory); a capability the composition does not expose cannot be configured.
Licence
MIT.
Links
More in this category
Tencent/WeKnora#dsh-weknora★ 37918
Four read-only tools over a WeKnora knowledge base: list knowledge bases, hybrid passage search, reassemble one document's chunks in order, and WeKnora's own cited RAG or ReAct-agent answer with a resumable session id.
DayuanJiang/next-ai-draw-io#dsh-plugin★ 37097
Draws draw.io diagrams in DeepSeek Harness through the next-ai-drawio MCP server: the link in the reply opens a live preview in the right sidebar, you can edit the diagram by hand, and each AI change is a version you can restore. Node.js 18+; npx downloads the MCP server on first use.
superdesigndev/treg★ 8650
Tool catalog for agents: search ~2,600 external endpoints (SEO and SERP, backlinks, social, people and company enrichment, ad libraries, scraping) by the task you want done, read each one's parameters and per-call price, then call it with the credential injected server-side. Ships the skill plus an MCP row that stays disabled until TREG_TOKEN is set.
T-Auto/dsh-ops★ 5964
Provides bash, PowerShell 7, and high-performance Rust tools for DSH on Windows to reduce token usage.
sixtysevenlf/dsh-blender-plugin★ 2216
Lets a DSH agent drive a local Blender over a direct TCP channel with 15 tools: viewport frames, custom-angle renders, Python execution, headless and job offload, transaction rollback, and a planning layer of 228 ops across 34 families.
helloHub1212/dsh-windows-mcp★ 2002
Bridges the CursorTouch/Windows-MCP desktop automation server into DSH through the official MCP client bridge, registering its screenshot, UI tree snapshot, mouse and keyboard input, clipboard, process and registry tools as mcp__windows__* tools for the model, and adds a windows_mcp_doctor diagnostic tool. Computer Use is off by default and is switched on from the plugin panel.
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.