dsh-role-config
dsh 的角色预设和模型池：基于角色路由的委派，支持能力条件和优先级回退
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:snnh/dsh-role-config#e6aa08c817d2a474f2578e9fa22de075616985dfRole Config 以 dsh-role-config 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
点击下方 Badge 复制 Markdown，粘贴到 README 即可。
验证 package.json 声明的 GitHub 仓库，即可管理这个公开页面。认领后，Hub 会优先安排当前版本的安全扫描，并在通过后公开展示结果。
认领这个 Plugin →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 github:snnh/dsh-role-config
The built halves (lib/index.js, lib/client.js, and their declarations) are
committed, so a git install needs no build script and no allowBuilds
permission; install it and enable the bundle. Rebuild them with
npm run build after changing src/.
This plugin registers its delegation tool under the official subagent name,
which shadows the official tool only while that tool lives in an outer scope.
Set modelSelectionSettings: false on the official tool-subagent row (both
in the shipped presets and in any preset you added):
- id: 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 logs which row to fix
and leaves the official tool in place. 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.