Configuring dsh-model-router
DeepSeek Harness supplies model definitions through its Models page. dsh-model-router reads exact provider/model routes and can use user-supplied quality ratings, USD prices, specialties, CLI model names, execution preferences and billing preferences. Routing profiles and preferences are configured in the plugin settings. The supported persistent state file is $DSH_HOME/model-router/state.json; when DSH_HOME is unset, the documented default is ~/.dsh/model-router/state.json. Provider CLIs retain their own login and configuration. API keys are not copied into model profiles or terminal logs.
Running dsh-model-router work
The workbench performs local task classification and complexity analysis, then recommends a single route, dependent team packages or an explicitly configured model. Presets include economy, balanced and quality-first routing. A run can be previewed and confirmed from the workbench or invoked in an official DeepSeek Harness session. Read-only execution sends the selected task and context to a model-directory API or supported headless CLI and records the result. Editable CLI execution runs packages sequentially with dependency context, using approved isolated Git worktrees and conditional patch integration. Official tools can be detected, installed or updated, checked for launch readiness, and inspected for login status; installation jobs provide logs and cancellation.
dsh-model-router requirements
DeepSeek Harness Desktop must be one of 0.2.0-rc.1, 0.2.0-rc.2 or 0.2.1-rc.2. Compatibility beyond these versions is not claimed. Declared support includes Hermes/Pi installation and terminal support, but neither has a verified managed runner. Node.js >=22.19 and pnpm 10.34.6 are source development and build requirements, not runtime prerequisites.
dsh-model-router limits and permissions
Planning is local, but execution may incur provider charges. Manual mixed execution is read-only; configured tools retain their default model unless explicitly mapped. An editable cli-native team runs outside the DeepSeek Harness process sandbox with the current OS user's permissions. Git worktrees collect edits but do not restrict OS access. The 0.22.2 release has no verified end-to-end vendor run; the README's real vendor evidence is tied to 0.20.0.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub