dsh-autotier

dsh plugin --profile web add dsh-autotier

dsh-autotier

🧊 FROZEN — 2026-10-31. Maintenance mode. No new features; security and dependency fixes only.

Maintenance status: 🧊 FROZEN

Frozen on 2026-10-31 in maintenance mode. The package stays installable; only security and dependency fixes are planned.

dsh plugin --profile <name> add dsh-autotier

English | [简体中文](README-zh.md) | [Español](README-es.md) | [Português](README-pt.md) | [हिन्दी](README-hi.md)

Automatic model-tier routing for DeepSeek Harness: one user instruction enters,

one tier decision comes out — no manual model switching.











Complex intent (architecture, planning, debugging, multi-step engineering) is

planned on the strong tier and then implemented on the cheap tier.

Simple intent (questions, retrieval, batch chores, daily work) is designed and

implemented on the cheap tier directly. While the cheap tier executes,

high-risk tool calls are denied by a deterministic guard, and repeated failures

escalate to the strong tier with a TTL fallback.

• Official repository: <https://github.com/PerryLink/dsh-autotier>
• npm: dsh-autotier (bare, unscoped)

📖 Ecosystem knowledge base — measured data, not marketing: plugin development guide · plugin-selection data · maintenance criteria.

<!-- star-cta -->

Install & uninstall

npm channel

dsh plugin --profile web add dsh-autotier
npm i -g dsh1024
dsh1024 plugin --profile web add dsh-autotier

git channel

dsh plugin --profile web add github:PerryLink/dsh-autotier
git clone https://github.com/PerryLink/dsh-autotier.git
cd dsh-autotier && pnpm install && pnpm run build
dsh plugin --profile web add .

Optional preset prompt section. The router works without it. To let the

model know which tier it is running on, add one row to your agent preset

(docs/preset-row.md has the exact block):

- insert:
    - id: autotier-prompt
      name: '@deepseek-ai/dsh-system-prompt'
      # sections: [...]  — see docs/preset-row.md

Uninstall

dsh plugin --profile web remove dsh-autotier

The row, its command, its tools and its listeners are all removed with the

plugin. Configuration a user saved through the Plugins page lives in the active

profile patch and belongs to that profile, not to this plugin; removing the row

leaves it there untouched.

⭐ 如果它帮到了你

这个插件是 DSH 插件家族的一员（95 个，全部 Apache-2.0）。如果你在用，给个 star —— 它不会解锁任何功能，但会让下一个人在搜索里更容易找到它。

English: part of a 95 plugin family for DeepSeek Harness. If it is useful, a star helps the next person find it — nothing is gated behind it.

What is dsh-autotier?

npm channel

git channel

Workflow overview: call → plugin → result. The examples below use the real command surface.

Compatibility

Harness · Status

@deepseek-ai/dsh 0.1.2-rc.1 · no longer supported; that line predates the SettingsForms contract this plugin now targets

@deepseek-ai/dsh 0.1.5-rc.2 · no longer supported; the settings.register / settings/updated contract it exposes was removed upstream

@deepseek-ai/dsh 0.1.6-alpha.2 · no longer supported; same removal, first line to ship SettingsForms

@deepseek-ai/dsh 0.1.7-rc.2 · compatible; verified on the 0.1.7 line

@deepseek-ai/dsh 0.2.2-rc.1 · required; verified against the published packages (typecheck:ci, 214 tests) and a real Loader composition

@deepseek-ai/dsh 0.2.1-rc.2 · compatible; routing uses the agent/request waterfall, which that line still allows to change the route

@deepseek-ai/cordis ^4.0.3, @deepseek-ai/cosmokit ^1.8.4, @deepseek-ai/schemastery ^3.18.3 · peer baseline

Peer ranges name all published lines explicitly (>=0.1.6-0 <0.2.0 || >=0.2.0-0 <0.3.0 || >=0.2.1-0 <0.3.0), because a semver range whose only prerelease

comparator sits on an earlier version tuple does not admit a later alpha.

They are refreshed per published wave. The declared range is deliberately wider

than the verified one: it documents what the manifest accepts, not what has been

tested.

This release is a breaking adaptation. The 0.1.6-generation harness

removed the settings provider seam this plugin was built on: the

@deepseek-ai/dsh-settings-file package is gone, ctx.settings is now

SettingsForms (a schema→form projector, with no register), and

settings/updated no longer exists. There is no shared surface that lets one

plugin observe another plugin'

…(truncated)