Back to directory

dsh-submodel

In a curated listMaintenance: Active

angel291592/dsh-submodel

Sets up when the main agent works itself vs. delegates, and to which provider/model, via system-prompt policy plus delegate_task.

View on GitHub
$ dsh plugin --profile <your profile> add dsh-submodel

22

stars

2

forks

JavaScript

Language

MIT

License

2026-10-30

Created

2026-11-19

Last push

MIT policy pack for the official DSH subagent: route-based Flash / boss delegation written into the system prompt, a `delegate_task` tool with the same parameters as `subagent`, a child-session guard against recursive delegation, and a first-run wizard that writes both the host allow list and the plugin config.

DSH integration

Native runtime

Author-claimed

Safety audit

Unaudited

Last verified

2026-11-18

License

MIT

01What can it help you accomplish?

  • Make the main agent delegate verifiable execution blocks instead of doing everything itself

    A delegation policy in the system prompt: boss mode hands verifiable execution blocks to the configured `executor` route, Flash mode does ordinary work itself and escalates only when a task is complex or exceeds the executor

    DeepSeek Harness users who run several provider/model routes in one profile and want delegation decided by route instead of by model-name convention

  • Choose which provider/model a subagent runs on, without building a new provider setup

    A `delegate_task` tool that takes the same parameters as the native `subagent` and runs a real native call through `ctx.tools.execute`

    Operators who want a cheap executor route for routine work and a short list of expert routes for escalation

  • Configure both layers — host authorization and plugin config — in one guided first run

    A `configure_submodel` wizard that asks three questions and writes the host authorization row first, then the plugin config

    New users who would otherwise have to hand-write two YAML blocks before any delegation works

02How to install into DeepSeek Harness

Prerequisites

  • DSH `0.2.2-rc.1` — `engines.dsh` declares `>=0.2.2-rc.1 <0.3.0` and the installer blocks versions outside that range; `0.2.1-rc.5` and earlier are incompatible
  • A profile with existing provider/model channels — the plugin reads them and never creates new ones
  • Host authorization: the DSH subagent model-selection setting enabled, with the executor and expert routes added to the allow list

Installation steps

  1. 01

    Install into your profile: `dsh plugin --profile <your profile> add dsh-submodel`

    $ dsh plugin --profile <your profile> add dsh-submodel

  2. 02

    Restart the profile: `dsh --profile <your profile>` — plugin changes only apply on the next boot

    $ dsh --profile <your profile>

  3. 03

    In the first session call `configure_submodel` (three questions: executor route, expert routes, whether to write the host allow list too) — it writes the host authorization row and the plugin config via the official `configEditor`

  4. 04

    Or configure by hand: replace `[]` in `~/.dsh/profiles/<your profile>/cordis.patch.yml` with an entry `- id: submodel` and a `config` block containing `executor: {provider, model}`

  5. 05

    Start a new session — host authorization only applies to new sessions

Verify the integration

  • On the first session the `configure_submodel` tool is visible; after a successful write the plugin reloads and the tool disappears — the README says that is expected, not an error
  • A missing `executor` shows up as the startup log line `config.executor.provider/model 未配置,自动委派不可用…`

Rollback

  • `dsh plugin --profile <your profile> remove dsh-submodel`
  • The host authorization row stays in the profile patch after removal — delete the `subagent-model-selection-settings` entry by hand if you want to undo that too

03DSH integration and capability boundaries

DSH integrationNative runtime

DSH host plugin: it does not add a provider layer of its own — it reads the channels and models already configured in your profile, writes a delegation policy segment into the system prompt, and adds one unified `delegate_task` entry point on top of the official `subagent`.

  • Route-based delegation policy

    The provider + model route of the current request→Flash (`economize`) mode when the route equals the configured `executor` or matches an entry in `economyRoutes`; boss mode for every other route

    writes one policy segment into the system prompt at `order` 2850 by default
  • `delegate_task` tool

    `description`, `prompt`, and optional `provider` / `model` / `reasoning_effort` — provider and model must be passed as a pair→Returns the child session id immediately; the runtime notifies you when it finishes

    starts a real native subagent through `ctx.tools.execute`, so the host allowlist, pre-checks and permissions still apply
  • `configure_submodel` first-run wizard

    Three answers: executor route, expert routes, whether to write the host allow list as well→The host authorization row plus the plugin config (`executor`, `experts`, `economyRoutes`) written through the official `configEditor`

    writes two places only — the plugin config row and the `subagent-model-selection-settings` row; no channels or keys are created
  • Child-session guard

    Any child session spawned by delegation→`delegate_task`, `subagent`, `subagent_fork`, `workflow` and `spawn_teammate` are all unavailable there

  • `list_subagent_models` capability gate

    No arguments→The routes already authorized for subagents, so `delegate_task` is not called blind

04Who is it for? When not to use it?

Good for

  • DeepSeek Harness users who run several provider/model routes in one profile and want delegation decided by route instead of by model-name convention
  • Operators who want a cheap executor route for routine work and a short list of expert routes for escalation
  • New users who would otherwise have to hand-write two YAML blocks before any delegation works

Not for

  • Targets DSH `0.2.2-rc.1`; `engines.dsh` is `>=0.2.2-rc.1 <0.3.0` and the installer rejects anything outside that range. `0.2.1-rc.5` and earlier lack both the batched `ctx.tools.execute` and the 0.2.2 subagent routing semantics.
  • Two layers must both be configured or nothing can be delegated: host authorization (which routes a subagent may switch to) and the plugin config (`executor` / `experts`). With no `executor` the plugin only logs an error and delegates nothing.
  • The policy text defaults to Chinese and can be replaced wholesale via `texts.*`; the plugin only applies to the composition named by `preset` (default `standard`), and it ships no budget guard, cost collection or watchdog re-dispatch.
  • GUI end-to-end behaviour (wizard cards, both writes, delegation, economize mode) is left for the user to accept on a real GUI session and is marked unverified; on headless / pure-CLI clients no question card is available, so only the manual YAML path works.

05Compatibility, maintenance and safety notes

  • Targets DSH `0.2.2-rc.1`; `engines.dsh` is `>=0.2.2-rc.1 <0.3.0` and the installer rejects anything outside that range. `0.2.1-rc.5` and earlier lack both the batched `ctx.tools.execute` and the 0.2.2 subagent routing semantics.
  • Two layers must both be configured or nothing can be delegated: host authorization (which routes a subagent may switch to) and the plugin config (`executor` / `experts`). With no `executor` the plugin only logs an error and delegates nothing.
  • The policy text defaults to Chinese and can be replaced wholesale via `texts.*`; the plugin only applies to the composition named by `preset` (default `standard`), and it ships no budget guard, cost collection or watchdog re-dispatch.
  • GUI end-to-end behaviour (wizard cards, both writes, delegation, economize mode) is left for the user to accept on a real GUI session and is marked unverified; on headless / pure-CLI clients no question card is available, so only the manual YAML path works.
  • Model metadata has no price field, so which routes count as "cheap" is entirely your decision — the wizard only pre-fills candidates.
2026-10-302026-11-14Not specified by the author

MIT · README on branch main · no release (last push 2026-11-14)

06Frequently asked questions

What does dsh-submodel actually change inside DeepSeek Harness?

Three things: a delegation policy segment in the system prompt, a `delegate_task` tool layered over the official `subagent`, and a guard that blocks `delegate_task` / `subagent` / `subagent_fork` / `workflow` / `spawn_teammate` inside child sessions. It does not create a provider layer — it only reads the channels and models already in your profile.

Why does delegation fail with "child LLM route is not allowed for this Session"?

That is missing host authorization. Open Settings → subagent model selection, turn it on and add the executor and expert routes to the allow list one by one, or write the `subagent-model-selection-settings` entry into `cordis.patch.yml`. Host authorization only applies to new sessions, so open a new one (or restart the profile) afterwards.

Why can I not see the `configure_submodel` tool?

Four documented reasons: `executor` is already configured (the wizard only appears once), `autoConfigure` was set to `false`, the current session's native `subagent` has no model-selection parameters, or you are not in a top-level main agent session.

Which DSH versions work?

0.2.2-rc.1 is the target and the only version verified by loading it in an isolated profile. `engines.dsh` declares `>=0.2.2-rc.1 <0.3.0` and the installer blocks anything outside that range; 0.2.1-rc.5 and earlier are incompatible because they have neither the batched `ctx.tools.execute` nor the 0.2.2 subagent routing semantics.

How do I remove it, and what is left behind?

Run `dsh plugin --profile <your profile> remove dsh-submodel`. The host authorization row stays in the profile patch afterwards; delete the `subagent-model-selection-settings` entry by hand if you want to undo that as well.

08Data and sources

  • Author-claimedgithub.com6dd633368b2d…

    它**不新建 provider 体系**——只读你 profile 里已有的渠道与模型配置,把委派策略写进系统提示词,

  • Author-claimedgithub.com6dd633368b2d…

    并给官方 `subagent` 补一个统一的委派入口 `delegate_task`。0.2.0 起模式按**路由**判定(不再依赖

This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-11-18. Found an error? Submit a correction.

🏆

Best DeepSeek Harness Plugins

Twelve plugins worth installing first — picked from the whole catalog, across every category.

DSH Plugins is an independent community directory of DeepSeek Harness plugins. Not affiliated with or endorsed by DeepSeek. Third-party plugins are not security-audited — review the source before installing.

New DeepSeek Harness plugins, weekly. No spam.