ringoage/dsh-subagent-model-picker
A GUI subagent-model selector beside the main model seat: pick a model and reasoning effort per session, applied to every in-process subagent.
A visual, manual subagent-model selector for DeepSeek Harness: a GUI control beside the main model seat, per session, that lets you pick a cheaper or faster model and its reasoning effort for every in-process subagent. The README contrasts it with tool-based, auto-routing and command-based approaches — all of which decide for you — and positions this as the only visual manual selector in the category, with the choice explicit, visible at a glance and deterministic, inherited by default until you opt in. The host half recognises a child by agent.options.subagentDepth >= 1, walks the parent chain to the root session and overrides { provider, model, reasoningEffort? } only for subagents.
Install
dsh plugin --profile web add github:ringoage/dsh-subagent-model-pickerREADME Install block quoted verbatim; the README notes this is the same github: install path the DSH plugin market uses, so it can be installed straight from the repository. No npm package version is asserted.
Compatibility
README: a host + browser plugin for DeepSeek Harness that registers one agent/request waterfall listener; the README says it works without touching the apiProxy settings whitelist, covers subagent, subagent_fork and workflow fan-out children at any depth, and keeps its selection per-session and durable across restart. UI copy is localised (zh / en).
Details
- Repo: ringoage/dsh-subagent-model-picker
- Category: Models & Providers
- Stars: 0
- Version: Source/git install (repo verified 2026-09-16; last push 2026-08-16)
- Last push: 2026-08-16
- First seen: 2026-08-16
Recent updates
The README documents the mechanism and the comparison with other routing approaches rather than a release-by-release table.
FAQ
- How do I install it?
- The README's command is dsh plugin --profile web add github:ringoage/dsh-subagent-model-picker — the same github: path the DSH plugin market uses.
- How is it different from auto-routing plugins?
- Per the README, those answer "pick for me" while this one answers "let me pick": you choose visually beside the model seat, so the selection is deterministic and always visible; the README says the two compose.
- Does it apply to nested subagents?
- Yes — the README says one host-root agent/request listener covers subagent, subagent_fork and workflow fan-out children at any depth.