dsh-agent-teams-model-override
DeepSeek Harness Agent Teams 的模型选择、模型切换，以及真正的嵌套管理者/工作者团队。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:funk80rus/dsh-agent-teams-model-override#1bbe0891710264a5bc4b517045f785204e6a652cAgent Teams Model Override 以 dsh-agent-teams-model-override 发布，当前版本为 1.6.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
A small, fail-closed extension for DeepSeek Harness Agent Teams that adds:
spawn_teammate_with_model accepts
provider, model, and reasoning_effort; the teammate keeps that route across later
turns and cold resume. The roster reports the session's real model instead of the profile
default.Session.header.parentSession = manager, share the Lead's task board, delegate work inside
its own zone, and interrupt its own workers. Nested transcripts open from the Team panel.switch_teammate_model changes the route of an
existing teammate on its next request without creating a new member or losing its history.It is a thin extension of the official Agent Teams bundle. It does not implement a second
orchestrator, copy board transitions, or replace the native continuable-subagent lifecycle.
When the official spawn_teammate learns these arguments itself, this package can go away.
Status: 1.6.0. 201 tests pass against DSH
0.2.1-rc.2. The creation/model paths are live-verified. The 1.6.0 manager-interrupt and nested-transcript paths are covered by contract tests against the installed runtime; a live UI pass is still pending, so treat those two paths as release-candidate behavior.
| Requirement | Value |
|---|---|
| DeepSeek Harness | Desktop 0.2.1-rc.2 (tested), 0.2.0-rc.2 also supported |
| Official bundle | Agent Teams installed and enabled |
| Node.js | 22+ (development only; the installed Host provides its own runtime) |
| Profile | any; the package is a normal DSH bundle |
The plugin checks private runtime seams before installing. If the installed DSH no longer matches the contracts it was written against, the affected component refuses to install and writes the reason to the Host log instead of failing in the middle of a turn.
Make sure the official Agent Teams bundle is installed and enabled.
Open Plugin Manager in Creator Mode and choose Install bundle.
Enter the GitHub spec:
github:funk80rus/dsh-agent-teams-model-override
Enable dsh-agent-teams-model-override. Three component rows appear in Components;
each row has its own toggle:
| Component | What it adds |
|---|---|
agent-teams-model-override | spawn_teammate_with_model, accurate roster model |
agent-teams-manager | spawn_team_worker, zone task delegation, manager interrupt, nested transcripts |
agent-teams-teammate-model | switch_teammate_model for a running teammate |
The committed runtime/<hash>/ graph is what the Host loads. A GitHub install does not
need a build step.
DSH_HOME="${DSH_HOME:-$HOME/.dsh}"
PROFILE="$DSH_HOME/profiles/<profile>" # e.g. desktop
cd "$PROFILE"
pnpm add github:funk80rus/dsh-agent-teams-model-override
Then enable the bundle through the Plugin Manager UI, or from a DSH session:
plugin_manager { action: "set_bundle", target: "dsh-agent-teams-model-override", enabled: true }
If pnpm refuses a fresh git dependency because of a release-age policy, install it through
the Plugin Manager instead, or pass --config.minimumReleaseAge=0 for that one command.
The package is not published to npm and is marked "private": true; GitHub is the
distribution channel.
Ask the Host which routes are eligible first:
list_subagent_models({})
list_subagent_models({ provider: "opencode-go" })
list_subagent_models({ provider: "opencode-go", model: "glm-5.3-flash" })
Then create the teammate:
spawn_teammate_with_model({
name: "reviewer",
description: "Independent review of the implementation",
prompt: "Review the implementation and report concrete defects.",
context: "fresh",
provider: "opencode-go",
model: "glm-5.3-flash"
})
provider and model must be supplied together. reasoning_effort is optional and is
validated against the efforts that model actually advertises.spawn_teammate does.// Lead: create a manager with the normal or model-aware tool
spawn_teammate({ name: "mg-1", description: "Release manager", prompt: "..." })
// mg-1, from its own scope:
spawn_team_worker({ name: "w-1", description: "Worker", prompt: "..." })
// The worker is a teammate in the same team, but its durable parent is mg-1:
// list_agents, the shared task board, send_message and cold resume all see it.
The Lead can also choose the real parent explicitly:
spawn_teammate_with_model({ name: "w-2", ..., manager: "mg-1" })
Assign and track work:
team_task_assign({ subject: "Fix the parser", description: "...", owner: "w-1" })
team_task_list({})
team_task_update({ task_id: "task-7", expected_revision: 2, action: "complete" })
team_hierarchy({})
A manager may change tasks only inside its actual descendant zone (computed from durable
parentSession headers, not from declared labels). Outside that zone the call fails with
TEAM_TASK_OUT_OF_ZONE; claim is never widened, and the Lead is not affected.
interrupt_agent({ target: "w-1" })
A manager may interrupt only its own descendants; the Lead may interrupt anyone. The native
interrupt operation is still executed as the real Lead after the zone check, so the
official semantics are preserved: the current turn stops, pending inbox/activation survive,
and the next message starts the worker again. Self-interrupt returns
TEAM_INTERRUPT_SELF; an unrelated target returns TEAM_INTERRUPT_OUT_OF_ZONE.
switch_teammate_model({
target: "w-1",
provider: "opencode-go",
model: "qwen3.8-flash"
})
The member keeps its id, name, history, journal entry, and board tasks. Only its next request
uses the new route. The official session controller appends the durable
model/selection event, so the change survives cold resume. The response says which path
was used:
via: "session-controller" — committed immediately;via: "pending" — the teammate was unloaded; the route is applied when it next starts.target: "lead" changes the Lead's own route. A manager may switch members of its own zone;
a leaf teammate without a zone does not get the tool at all.
All three rows are inserted by cordis.patch.yml and select the same immutable graph
runtime/<hash>/, so component versions can never drift apart.
- insert:
- id: agent-teams-model-override
name: './runtime/<hash>/plugin.js'
config: { force: false, rosterModel: true }
- id: agent-teams-manager
name: './runtime/<hash>/manager-component.js'
config: { nestedTeams: true }
- id: agent-teams-teammate-model
name: './runtime/<hash>/teammate-model.js'
config: { switchModel: true }
force — install even when the route seam is missing (not recommended; the component will
be unable to deliver a route).rosterModel — replace only the model field of roster rows with the session's effective
model.nestedTeams — enable real nested managers/workers and the zone task/interrupt authority.switchModel — register switch_teammate_model.Disabling a row removes its tools and shadows immediately. Disabling the manager row does not break already-created nested members while another row is still loaded; the read/recovery bridge is reference-counted.
Do not add these rows to the profile's own cordis.patch.yml. A profile-level insert
would keep the plugin alive after set_bundle(enabled: false) and make the bundle impossible
to disable cleanly. Use only the package's cordis.patch.yml, which the bundle loader
applies.
A fuller description is in docs/ARCHITECTURE.md.
AsyncLocalStorage store
created by one tool call and is consumed exactly once by the first startContinuable /
startActivation whose parent is that delegating agent. Nothing global is mutated.roster.spawn as the real Lead (name checks, member limit, journal root, provisioning),
then rewrites request.parent to the manager immediately before the native start. The
child gets a real parentSession, the manager's catalog, and the shared team journal/board.parentSession headers, not from decorative hierarchy records. A manager cannot grant
itself authority over another manager's children.parent = Lead; for a nested worker the durable parent is the manager, so the Host rejects
it as subagent/unauthorized. The component wraps only sessionController.page and
follow: if the supplied parent is a real ancestor of the actual parent, the address is
rewritten to the actual parent; otherwise the request is unchanged and the Host still
refuses.selectForNextRequest on the session
controller appends the durable selection and re-installs route listeners. If that method is
unavailable, the tool reports via: "session-append" plus a warning instead of pretending
the route changed.npm run build hashes every file in lib/ into
runtime/<hash>/; the package exports and the bundle patch always point at one complete
graph. The Host never loads editable lib/ files directly.These are known, tested limits—not guesses.
roster.spawnAdmitted, activation registry, delivery symbol, session
controller). A future DSH that changes them makes the component fail closed with a reason
in the Host log. It is not a promise of forward compatibility.failed
creation still consumes its name and slot. A Lead session has 16 teammate slots
(the Lead is separate); context: "fresh" creates a new member, it does not reuse one./compact in the GUI summarizes history; it does not erase it.
The only clean start is a new teammate with context: "fresh". There is no /clear tool
for teammates in 1.6.0.parentSession. Use an explicit send_message({ target: "lead" }) when the worker
must answer the Lead.switch_teammate_model returning via: "pending" and the teammate's next start, repeat
the switch.context: "fork" plus a changed route can prevent the provider from reusing the
inherited conversation prefix. This is the same trade-off as official subagent forking.team_hierarchy_set cannot physically reparent an existing session.| Symptom | Check |
|---|---|
| No new tools after enabling | Is the official Agent Teams bundle enabled? Is the package bundle enabled? Did the component log a runtimeSupportReport failure? |
TEAM_LEAD_REQUIRED from a manager | The agent-teams-manager row is disabled or failed to install. |
TEAM_INTERRUPT_OUT_OF_ZONE | The target is not a real descendant of the caller. Check team_hierarchy. |
subagent/unauthorized when opening a nested transcript | Confirm agent-teams-manager is enabled at 1.6.0+; this is the read-side repair. |
| Model did not change | Look at via and warning in the response. session-append means the official commit path was unavailable. |
Install fails in pnpm | Use the Plugin Manager, update Node to 22+, or retry without a release-age policy for the git dependency. |
| Tools disappeared after a DSH update | The private contracts changed; check the Host log for the fail-closed reason. |
npm test # 201 tests; installed-runtime tests skip when DSH is not found
npm run build # writes lib/ into runtime/<hash>/ and rewrites exports + patch
npm run verify # build, then the full suite
DSH_ASAR can point at a non-default app.asar; the test helpers otherwise look for
/Applications/DeepSeek Harness.app/Contents/Resources/app.asar.runtime/<hash>/ by hand. It is content-addressed. Change lib/, run
npm run build, then commit the new graph together with the updated package.json and
cordis.patch.yml..gitignore already excludes .diagnostics/, docs/evidence/, docs/rollback/, and the
author's internal notes.Contributions are welcome; see CONTRIBUTING.md.
The plugin runs inside the local DSH Host with the user's permissions. It makes no network requests of its own, has no telemetry, and does not read credentials or API keys. It reads local session headers and the official services to compute lineage, routes, and history addresses; that data stays on the machine.
It does hook private runtime seams, so treat it as privileged local code: install from a commit you trust, and read SECURITY.md before reporting a vulnerability.
MIT. See LICENSE. The upstream @deepseek-ai/dsh-* packages are also MIT; this
package does not vendor their code.