Per-workspace Skill and MCP enablement for DeepSeek Harness: control which skills and MCP servers new sessions load, per project.
Install
# from npm (prebuilt)
dsh plugin --profile web add dsh-workspace-scope
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:Ri0n72Y/dsh-workspace-scope
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
Enable or disable the current Agent's existing Skills and inherited Host-global MCP servers per DeepSeek Harness workspace.
This plugin only controls capability scope. It does not install, discover, or provide Skills or MCP servers. Each workspace can expose a different capability set through its own .dsh-scope.json.
中文版:README.md
[!IMPORTANT] Currently verified DSH version:
0.2.1-rc.5(Web).dsh-workspace-scope v0.5.4has passed dependency installation, typecheck, build, tests, and coverage against this version.engines.dsh >=0.2.1-rc.2is the permitted loading range; it does not mean every version in that range has been verified. Packaged-Desktop installation, UI, and policy smoke tests on0.2.1-rc.5are still pending.After validating a new DSH version, update the verified version here, the badge above, and the release notes together. Do not claim support for untested versions.
Install
Requires the dsh CLI:
dsh plugin --profile web add dsh-workspace-scope
Remove it with:
dsh plugin --profile web remove dsh-workspace-scope
For Desktop 0.2.1-rc.5, install dsh-workspace-scope from the sidebar Plugins page. Desktop owns the reserved desktop profile, so the public CLI does not manage that profile directly; the Plugin Manager uses Desktop's own profile and pnpm installation path.
Usage
In a blank new-session Session, click "Workspace scope" on the right side of the input card.
The dialog shows model-invocable Skills from the current Agent and Host-global MCP servers. Switching Agent Presets refreshes the list for the current Agent. Toggles, search, enable-all, and disable-all save immediately to .dsh-scope.json in the workspace root.
The configuration locks when the conversation starts its first real model request. Changes made before that point apply to the conversation; later changes apply only to new conversations.
By default, restrictions apply to root conversations only. Select Subagents to apply the same root-workspace Skill and Host-global MCP policy to subagents. Subagents still discover Skills from their own effective working directory. This plugin does not search for nested .dsh-scope.json files. The management UI only lists Skills visible to the root Agent. Skills unique to a subagent's directory are not listed there, but the same whitelist still applies to them; to allow one, add its name to default.skills in the root .dsh-scope.json manually.
Configuration
Normally the UI is enough. You can also edit .dsh-scope.json manually:
{
"default": {
"mode": "whitelist",
"skills": ["<skill-name>"],
"mcps": ["<server-name>"],
"subagents": false
}
}
default: enable everything.whitelist: enable only listed capabilities.blacklist: disable listed capabilities.skills: Skill names.mcps: Host-global MCP server names.subagents: whether the workspace restriction also applies to subagents; defaults tofalsefor existing files.
Scope
- Skills come from the current Agent's existing model-invocable Skill view; this plugin does not install or add Skills.
- Disabling a Skill controls model invocation. Whether
/skill-nameremains available is determined by that Skill's native DSHuserInvocablepolicy. - MCP management covers only Host-global MCP servers inherited by the Agent. Tool / MCP registrations inside Agent or Preset scope are not managed.
- In 0.5.x, MCP
serverNamevalues containing__are unsupported; ordinary tool names may contain__.
Implementation details, data flow, and C4 diagrams live in docs/architecture.md. Release history lives in CHANGELOG.md.
Contributing
Open an issue for bugs or ideas. Read CONTRIBUTING.md before submitting a pull request.
License
MIT
Links
More in this category
zhu1090093659/dsh-web#packages/dsh-task-board★ 10461
Task board for the dsh web GUI: a sidebar multi-column kanban whose cards run in real DSH agent sessions and can also be scheduled with cron expressions, executed host-side even with the browser closed.
zhu1090093659/dsh-web#packages/dsh-web-all★ 10461
Plugin and skin collection for the DSH Web UI: task board, Git graph, right-side panel, remote mobile UI, pet, live token stats, and a skin center.
ccch1mneyyy/dsh-TUI★ 7811
Claude Code-style full-screen terminal UI: pixel-whale header, live status line, and streaming thought expansion.
MeteorNOX/DeepSeek-Balance-Whale-Widget★ 7275
A fixed-corner whale widget for the DSH web GUI — balance, today's usage and per-turn cost with peak/off-peak pricing, editable balance-alert and daily-budget bubbles, a module-based custom bubble queue with A/B weighted choices and random lines or images, 30+ vendor templates (OpenAI, OpenRouter, Kimi, SiliconFlow, Ark, Zhipu, MiniMax and more) with per-model balance and subscription quota, plus task-end sound, imported audio, custom roles and a resource manager. Local-only, no telemetry.
omdsh-dev/DSH-better-sidebar★ 5195
Full sidebar workbench with file rendering and editing, terminal, Git, and subagents; third-party plugins can register new tabs.
omdsh-dev/dsh-genui★ 1008
Interactive UI components rendered inline in replies: layout, charts, forms, quizzes, mermaid, 3D scenes, and an action event loop back to the model.
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.