@snnh/dsh-role-config
dsh 的角色预设和模型池：基于角色路由的委派，支持能力条件和优先级回退
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add @snnh/dsh-role-config@0.1.1Role Config 以 @snnh/dsh-role-config 发布，当前版本为 0.1.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
English | 中文
A dsh bundle that gives delegation two ways in and one decision layer:
role: "premium") and never
learns which model serves it. Each role carries a description the model
reads, a priority chain, and the operator's own routing rules.dsh plugin --profile <profile> add @snnh/dsh-role-config
The package is published to npm, so the line above needs no build step. A git
install (github:snnh/dsh-role-config) works too: the built halves
(lib/index.js, lib/client.js, and their declarations) are committed, so it
needs no build script and no allowBuilds permission. Rebuild them with
npm run build after changing src/.
A fresh mount registers no tool and changes no agent: exposure.delegateTool
and exposure.listTool both default to false, so the official delegation
tool keeps serving until an operator asks for the routed one. Turning both on
is the whole opt-in:
- id: role-config
config:
exposure:
delegateTool: true
listTool: true
pool:
- provider: deepseek-official
model: deepseek-chat
With exposure.delegateTool: true this plugin registers its delegation tool under the official subagent name.
While the plugin is enabled that routed tool is what the agent sees; disable
the plugin and the official tool serves again. Shadowing needs the official
tool one scope further out than the agent, so the official tool-subagent row
must carry modelSelectionSettings: false:
- id: tool-subagent
config:
provider: spawn
toolName: subagent
modelSelectionSettings: false
Leave that row ENABLED. Disabling it to free the name is a one-way trade: with
this plugin switched off afterwards, the deployment has no delegation tool at
all. Nothing needs it: the routed registration is nearer than the preset scope,
so it wins the name while the official tool stays mounted and serves.
Switching the takeover off (delegateTool: false, or the settings page's
Restore the official delegation tool button, which stages that switch and
saves in one click) hands the name back, and the plugin removes a leftover
disabled: true from the official row while it is at it.
A profile patch reaches the rows the profile declares. The shipped presets
declare their own, nested inside a cordis:group, and a patch replaces a
row's whole config — so restate the preset row with that one field flipped,
the way the harness's own overlays do. packages/bundle/web-app/presets/standard.patch.yml
lists the shipped plugins; refresh your copy when it changes:
- id: preset-standard
config:
id: standard
order: 1
plugins:
# …the shipped plugin list, unchanged…
- id: delegation
name: cordis:group
group: true
isolate: { workflowEngine: true }
config:
- id: tool-subagent
name: '@deepseek-ai/dsh-tool-subagent'
config:
provider: spawn
toolName: subagent
modelSelectionSettings: false
With model selection on, the official tool registers inside every agent's own
scope, where a same-named tool cannot exist. The plugin then names the row to
fix and leaves the official tool in place, so the session still opens;
delegate.toolName renames this plugin's tool instead, if you would rather
keep the official configuration.
Settings documents are confined to a loopback page by default, so a deployment reached at http://<lan-ip>:<port> shows the model pages and every plugin page as unavailable. To configure this plugin from the address you actually use, restate the client-connection row with its operator surface opened:
- id: connection
config:
trustedHosts: !!js ctx.webRuntime.trustedHosts
operatorSurface: trusted
A patch replaces a row's whole config, so keep trustedHosts in the row. The page is served only after the access token is validated and every request it makes still passes the Host/Origin fence and the session check; what changes is that the settings and plugin pages render at all.
Open Plugins in the Web sidebar and select Role Config. The page edits
one role-config settings section: the pool with its descriptions, the role
presets with their chains and rules, the switches (which surfaces exist,
failover, AI routing), the function bindings, and the delegation wiring.
| Surface | Content | When |
|---|---|---|
list_model_roles | Role ids with descriptions, and pool routes with descriptions | Only when the model calls it |
| System prompt | The same catalog, compact | Only with exposure.sessionStart |
subagent (role) | Nothing about the chosen model | Always |
A role's members, rules, and the router's answer never reach the model.