dsh-subagent-models
设置 DSH 子代理运行时使用的提供商、模型和推理力度：在“设置”中配置整个配置文件的默认值，也可以通过编辑器旁的标签按会话覆盖。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-subagent-models@0.1.3
Subagent Models 以 dsh-subagent-models 发布，当前版本为 0.1.3。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Set the provider, model and reasoning effort that DeepSeek Harness subagents run with — from one entry, the chip beside the composer. The card it opens has two scopes over the same two DSH-style pickers: a searchable, provider-grouped model menu and that model's own effort menu.
为 DeepSeek Harness 的子代理统一指定用哪个模型、思考强度多深：只有一个入口——输入框旁的「子代理」 胶囊；点开的卡片里用「本对话 / 全局默认」两个范围切换，两处都是同一组 DSH 风格的「模型 + 思考强度」 浮层菜单（可搜索、按提供方分组、行内勾选）。
agent/request override (index.js)client.js)@deepseek-ai/dsh-client-ui-primitives when present (a frozen platform module — nothing to
install), with hand-drawn .dsm-* fallbacks on hosts that do not ship it.| 本对话 | 全局默认 |
|---|---|
| 本对话 | 全局默认 |
# npm
dsh plugin --profile <profile> add dsh-subagent-models
# or straight from this repository
dsh plugin --profile <profile> add github:Garybot126/dsh-subagent-models
Then restart dsh once if the plugin row was not hot-loaded.
| Where | What |
|---|---|
| Composer → 「子代理 …」 chip | The only entry. Opens the card |
| Card → 「本对话」 scope | This conversation's override; the model menu's first row is 「跟随全局」 |
| Card → 「全局默认」 scope | The profile-wide default for every conversation without an override |
The chip's label is the effective route for the conversation (e.g. 子代理 DeepSeek-V4.1-Flash · high), so the composer always says what a delegation will actually use. The card's footer repeats
it with its source: 下一次委派将使用 …（来源：本对话 / 全局默认）.
The card's two rows are DSH-style cells — click one to open a menu anchored above it. The model menu matches the built-in composer model picker: a search box for catalogs above four models, provider groups with sticky headings, rounded hover rows and an inline check mark on the current choice. The effort menu lists 「模型默认」 plus only the levels that model advertises.
Both menus are driven by the live LLM catalog (ctx.llm): models are grouped by provider, and the
effort list is the one that model advertises (resolveModelInfo().reasoning.efforts), so an
unsupported level is never offered.
No settings page is registered by this plugin. The built-in 设置 → 插件 → 子智能体 page belongs to dsh itself (recursion depth, concurrency, model whitelist) and is unrelated; see below.
本对话 override → 全局默认 → no route (child inherits the parent session)
The delegation tool (subagent) is composed in the agent-plane preset, not in the Profile
patch, and it carries its own static agentOptions. A plugin cannot rewrite that composition, so
the route is applied one level lower:
agent/request (waterfall: "replace the frozen call configuration")
The listener is registered once and only rewrites an Agent that another live Agent owns — a delegated child. A top-level Session is never touched. Consequences:
subagent tool, without editing the preset and without adding
model-selection parameters to the tool schema;subagent, subagent_fork and Agent Teams members all count as delegated agents.$DSH_HOME/plugin-data/subagent-models.json (falls back to ~/.dsh/plugin-data/), hot-reloaded on
mtime, so editing it by hand also works:
{
"version": 1,
"global": {
"default": { "provider": "deepseek-official", "model": "deepseek-flash", "effort": "high" },
"presets": {}
},
"sessions": {
"<sessionId>": { "default": { "provider": "...", "model": "...", "effort": null }, "presets": {} }
}
}
global.default: null means no profile default; an absent sessions[sessionId] means the
conversation follows it.
Capability disclosure: reads and writes this one JSON file; binds no network port beyond the loopback
HTTP prefix /plugin/subagent-models used by the Web UI; never reads conversation content,
credentials, or any other file.
subagent_fork children are overridden too. A fork shares the parent's prefix, so a different
model costs its KV cache; clear the route (or keep the preset's own agentOptions) if that
matters to you.Several plugins in the market move subagent routing: dsh-subagent-custom (task-class routing),
dsh-subagent-model-picker (a per-session picker), dsh-subagent-default-model (settings.yaml
default), dsh-model-settings (a settings panel), dsh-orquestrator (a fixed forced route). This
one keeps the surface at one composer chip: two scopes, one pair of DSH-style pickers, and a label
that always shows the effective value.
On dsh 0.2.1-rc.2 (desktop profile):
deepseek-v4-pro + max → it succeeded;GET /plugin/subagent-models/state?sessionId=… → 200 with global, session and the catalog;POST /plugin/subagent-models/route with scope: "session" / "global" → 200 and the JSON file
updates on disk;MIT © Gary Gai