dsh-plugin-model-dispatch

Usage

Chat bar

Two chips sit at the right of the composer, next to the permission and preset controls:

Chip	What it does
Main (model glyph)	Switches the current session's model through the native API. The chip shows the effective route and its effort in the tooltip.
Subagent (branch glyph)	Picks the model for subagents started later in this session, stored as a session override. Reads Follows main while nothing is overridden.

Opening either chip gives the same menu: search, provider groups, favorites (★, hover-revealed, remembered per browser), recents, the effort slider, and — for the subagent route — a restore to settings default row.

Settings

Web settings → 模型切换 / Model switch holds three rows, each with a one-line scope hint:

Row	Meaning
New-session default model	Written to the native agent-default-model entry. Changing the model inside a chat does not change it.
Subagent default model	Used by subagents of any session that has no override.
Planning model	Used while plan mode is active.

Plan mode

1. Entering plan mode saves the session's current provider / model / reasoningEffort atomically and switches to the planning model.
2. Approving the plan (or /plan off) restores that saved route before the first execution request is assembled.
3. If a restore fails it is retryable and never strands the session on the planning model; the approval panel names the model that will come back.

Subagents

• A delegation started with explicit model options keeps them — the plugin only fills in a route where the native call left it open.
• The subagent chip and the settings default apply to newly started subagents; running ones keep their model.
• Subagent sessions themselves do not participate in plan switching or subagent overrides.