dsh-model-guard

DSH（DeepSeek Harness）插件：禁用模型 / 服务商，并自定义模型选择器的显示顺序。

简体中文 | English

本开源项目已链接并认可 LINUX DO 社区。

---

中文

被禁用的模型或服务商不会出现在对话的模型选择器里，也无法被选中或提交；排序决定选择器里服务商的先后，以及每个服务商内部模型的先后。

功能

• 禁用单个模型：勾掉后它从模型选择器消失，且 Host 侧拒绝选中/提交该模型。
• 禁用整个服务商：该 provider 的全部模型一并隐藏，连分组都不再出现。
• 两级排序：
  • 手工顺序：每个服务商、每个模型都有「置顶 / 上移 / 下移」。
  • 自动顺序：可选「按名称」排列未被手工调整过的项。
  • 规则恒为 显式顺序 > 回退策略 > 原顺序，未列出的新模型自动排在后面，模型增减无需重写配置。
• 全部设置改完即时生效，不需要重启 DSH。

使用位置

安装后，在 DSH 的 设置 → 模型禁用与排序 中使用。

安装

要求 DSH 0.2.x（@deepseek-ai/dsh），Node >=22。

# 从本仓库目录安装到 web profile
dsh plugin --profile web add /path/to/dsh-model-guard

dsh plugin add 会把包写进 profile 的 dependencies 与 dsh.profile.bundles，随后 HMR 自动组合。

若用 link: 方式安装，profile 的 package.json 需要同时出现在两处：

{
  "dependencies": { "@local/dsh-model-guard": "link:/path/to/dsh-model-guard" },
  "dsh": { "profile": { "bundles": [ /* … */, "@local/dsh-model-guard" ] } }
}

link: 安装必须声明 peerDependencies（本包已声明 @deepseek-ai/cordis、@deepseek-ai/schemastery）。 DSH 的 ResolutionRouter.routeLinked() 只对「在祖先 node_modules 里被声明为 peer」的裸包名走 interception 路由， 否则退回 Node 原生解析、从插件目录向上找不到 DSH 安装目录里的包，直接 ERR_MODULE_NOT_FOUND。

生效时机

dsh-hmr 监视 profile 的 cordis.patch.yml、$DSH_HOME/cordis.patch.yml 与 profile package.json 的 bundles。 前两者按内容比较，所以只 touch 不触发重组合——改内容才会。

配置

全部字段可在设置页编辑，也可直接写进 profile 的 cordis.patch.yml：

- id: model-guard
  config:
    disabledModels: []      # "provider/model"，禁用单个模型
    disabledProviders: []   # provider id，禁用整个服务商
    providerOrder: []       # 服务商显示顺序（id 列表）
    modelOrder: []          # 模型显示顺序（"provider/model" 列表）
    providerSort: natural   # natural | name
    modelSort: natural      # natural | name

这些字段都是 volatile()，改动即时生效。

实现要点

不改动 DSH 已发布的包，而是作为 profile 层 bundle，在 internal/get waterfall 上拦截对 llm 服务的属性读取， 返回一个缓存的 Proxy，覆盖 listModels() 与 listProviders() 做过滤与重排；其余成员原样透传并 bind 回真实实例。

选这两个方法是因为 GUI 目录（buildModelCatalog）与提交校验（modelAvailable → selectModel / requireModel） 都只经它们取目录——过滤一处即可同时挡住「显示」与「选择/提交」，重排一处即可决定选择器顺序。 核心路由不复用该目录，所以本插件是纯减法 + 重排：不新增模型、不改路由，resolveCallConfig() / stream() 仍走原始实例。

已知限制

• deepseek-account 与 deepseek-official 的顺序无法调整：客户端 orderModelProviders() 无条件把这两个排在最前， Host 侧怎么排都压不过。页面的排序说明里已写明。
• 已在会话中选中的模型被禁用后不会自动回退：菜单里消失、显示 fallback 标签，发消息时才报 session/model-unavailable，需要手动另选一个。
• 只收窄人的选择面，不阻断内部调用：已被 subagent、compaction 等组件显式指定的模型仍能运行。
• 依赖 internal/get 这个带 internal 前缀的 waterfall，它不是公开契约。DSH 大版本升级后若菜单不再隐藏/顺序不再跟随设置， 说明该事件签名变了。
• 排序是纯显示层重排，不影响默认模型（默认模型由 profile 的 agent-default-model 行决定）。

许可

本项目采用 MIT License 开源。

---

English

A DSH (DeepSeek Harness) plugin that disables models / providers and customizes the order in which they appear in the model picker.

A disabled model or provider is hidden from the conversation model picker and can neither be selected nor submitted. Ordering decides the sequence of providers in that picker, and of the models inside each provider.

This open-source project is linked to and endorses the LINUX DO community.

Features

• Disable a single model: once unchecked, it disappears from the picker and the Host rejects selecting or submitting it.
• Disable a whole provider: every model of that provider is hidden, and its group no longer appears at all.
• Two-level ordering:
  • Manual order: every provider and every model has "move to top / move up / move down".
  • Automatic order: optionally sort items you have not moved manually "by name".
  • The rule is always explicit order > fallback strategy > original order, so newly added models land at the end automatically — no need to rewrite the config when models come and go.
• All settings take effect immediately, with no DSH restart.

Where to find it

After installation, open Settings → Models & ordering in DSH.

Installation

Requires DSH 0.2.x (@deepseek-ai/dsh) and Node >=22.

# Install from this repository's directory into the web profile
dsh plugin --profile web add /path/to/dsh-model-guard

dsh plugin add writes the package into the profile's dependencies and dsh.profile.bundles, after which HMR composes it automatically.

If you install it as a link: dependency, the profile's package.json must list it in both places:

{
  "dependencies": { "@local/dsh-model-guard": "link:/path/to/dsh-model-guard" },
  "dsh": { "profile": { "bundles": [ /* … */, "@local/dsh-model-guard" ] } }
}

A link: install must declare peerDependencies (this package declares @deepseek-ai/cordis and @deepseek-ai/schemastery). DSH's ResolutionRouter.routeLinked() only routes bare package names through interception when the ancestor node_modules declares them as a peer; otherwise resolution falls back to native Node lookup, which cannot find the packages inside the DSH installation directory when walking up from the plugin directory, resulting in ERR_MODULE_NOT_FOUND.

When changes take effect

dsh-hmr watches the profile's cordis.patch.yml, $DSH_HOME/cordis.patch.yml, and the bundles field of the profile's package.json. The first two are compared by content, so a bare touch does not trigger recomposition — the content must change.

Configuration

Every field is editable in the settings page, or directly in the profile's cordis.patch.yml:

- id: model-guard
  config:
    disabledModels: []      # "provider/model" — disable a single model
    disabledProviders: []   # provider id — disable a whole provider
    providerOrder: []       # provider display order (list of ids)
    modelOrder: []          # model display order (list of "provider/model")
    providerSort: natural   # natural | name
    modelSort: natural      # natural | name

All of these fields are volatile(), so changes apply immediately.

Implementation notes

Rather than modifying the published DSH packages, this plugin ships as a profile-layer bundle that intercepts property reads of the llm service on the internal/get waterfall. It returns a cached Proxy overriding listModels() and listProviders() to filter and reorder; every other member is passed through and bound back to the real instance.

These two methods are the interception points because both the GUI catalog (buildModelCatalog) and the submission check (modelAvailable → selectModel / requireModel) read the catalog only through them — filtering in one place covers both "display" and "select/submit", and reordering in one place decides the picker's order. Core routing does not reuse that catalog, so this plugin is a pure subtraction + reordering: it adds no models, changes no routes, and resolveCallConfig() / stream() still go through the original instance.

Known limitations

• The order of deepseek-account and deepseek-official cannot be changed: the client's orderModelProviders() unconditionally puts those two first, and no Host-side ordering can override it. The settings page states this as well.
• A model already selected in a session does not fall back automatically when disabled: it disappears from the menu and shows a fallback label; session/model-unavailable is only raised when you send a message, so you need to pick another model manually.
• It narrows the human's choices without blocking internal calls: models explicitly requested by subagents, compaction, and other components still run.
• It relies on the internal/get waterfall (note the internal prefix), which is not a public contract. If a major DSH upgrade leaves the menu unfiltered or the order no longer following the settings, that event's signature has changed.
• Ordering is a display-layer rearrangement only and does not affect the default model (the default is set by the profile's agent-default-model row).

License

Released under the MIT License.