@neptune810/dsh-model-router

LIMITATIONS

Known limitations

- **No config schema.** Settings are read from the profile patch layer shown above and do not render as a form in the settings UI. This is deliberate: a schema would require importing `@deepseek-ai/*` packages, which a plugin installed beside the profile cannot resolve. - The router only touches the `deepseek-official` provider and models matching `familyPattern`. - **The router control takes over the official model cell by registration, not by patching the component.** It registers into `conversation.input.model` at priority -1 (below the shipped `ModelSelect` at 0), keeping the official model + effort sections inside its own panel. The old `conversation.input.right` chip (`model-router:composer-control`, order 20) self-retracts and is only a fallback for a host that rejects the seat. 0.10.0's first attempt shipped a blank cell and was rolled back in 0.10.1 because it had not declared `sessions` / `remote` / `remote.session` on the plugin root. - **The per-call route line is a separate small row** anchored after the tool call, not a badge inside the harness's own tool row or inside the thinking chain: a keyed slot replaces whatever it targets, and the thinking chain exposes no child slot. A call the host has not folded yet shows nothing rather than guessing. Plugin source changes only appear after you restart `dsh web`.