dsh-model-gate
单模型禁用门控：从所有发现路径中隐藏被拒绝的模型，使用协议内错误块阻止调度，并为拒绝列表提供设置区段界面
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-model-gate@0.1.2
Model Gate 以 dsh-model-gate 发布，当前版本为 0.1.2。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
English | 中文
Single-model disable gate for DSH. Deny whole provider routes or exact
provider/model pairs - denied models disappear from every discovery path and
any dispatch that still reaches them terminates with an in-protocol
MODEL_DISABLED error chunk.
Non-destructive by design: nothing in your provider configuration or credentials is touched. The denylist is an independent overlay; removing an entry (or the plugin) restores everything exactly as it was.
Settings panel — the「模型门禁」section reads the UNFILTERED catalog through the plugin's own typert service: one collapsible group per provider, one switch per model row, enabled-count badge on the group header.
Discovery hiding — deny a model and it disappears from the web selector and every other discovery path; the current selection clears with it.
| enabled | denied |
|---|---|
| Picker with the model enabled | Picker with the model denied |
Dispatch backstop — a turn that still reaches a denied model (subagents,
session titles, stale references) ends with the in-protocol MODEL_DISABLED
error chunk; no network request is issued.
Dispatch blocked with MODEL_DISABLED
From npm - one command:
dsh plugin --profile web add dsh-model-gate
Or from a Release tarball -
download dsh-model-gate-<version>.tgz, unpack it, and point the official
installer at the unpacked directory (the tgz ships prebuilt lib/, so no build
step and no pnpm allowBuilds prompt):
tar -xzf dsh-model-gate-0.1.2.tgz # -> ./package/
dsh plugin --profile web add ./package
Then restart DSH once so the bundle layer picks up the new entry. Every denylist edit afterwards hot-applies through settings - no further restarts. Verified against DSH 0.1.x-rc.
Edit the denylist section in ~/.dsh/settings.yaml - changes hot-apply, no
restart:
llm-model-gate:
disabledProviders:
- openrouter
disabledModels:
- "*/kimi-k2.7-code" # deny this model id on every provider
- "token-rhythm/glm-5" # deny one exact provider/model pair
Matching is exact and case-sensitive. A disabled provider route hides all of
its models. Model ids listed with a * + slash prefix are denied on every
provider, including dedicated routes (e.g. DeepSeek direct) that accept
explicit directory-external ids.
The web settings page has a dedicated「模型门禁」section (one collapsible group per provider, one switch per model row). The panel reads the UNFILTERED catalog through the plugin's own typert service, so currently denied models render as off and can be turned back on; toggling writes the denylist through the same hot-apply settings chain as manual YAML editing.
Row-state notes:
*/model star rule, or the whole
provider route denies it; the reason is tagged on the row.session.models / llm.models
catalogs, task_models, and API request validation all read the filtered
view - a disabled model behaves as if it had never been configured.
Re-enable and it reappears on the next refresh.llm/stream waterfall with a single terminal
finish{kind:"error", code:"MODEL_DISABLED"} chunk. The turn ends with a
normal model error; no network request is issued.agent/request-error compose naturally.openrouter does
not disable openrouter-vision - list both if you want both.listProviders/listModels methods on unload with zero residue. A
leftover denylist section in settings.yaml is harmless.MIT. An independently distributed plugin: DSH itself is untouched and keeps its own license.
bash scripts/build.sh # requires DSH_CHECKOUT or ~/dsh-harness; also shims node_modules/.bin/tsdown
npm run build:client # bundle src/client/main.tsx -> lib/client.js (ModuleLoader wrapper)
npm test # unit tests (node:test) against lib/ - run the build first on a fresh clone
Tests import the compiled lib/ outputs (relative ESM imports in source need
tsc's .js rewriting, which node's type stripping does not perform), which
resolves the host packages through the symlinks that scripts/build.sh
creates - run the build first on a fresh clone.
Inside a super-injector environment: dev_inject_plugin <this dir> then
dev_reload_package to iterate without restarting.