dsh-provider-toggle
DSH 模型提供商一键开关：在「设置 → 模型」每个提供商行（「编辑」左侧）放一个开关，关掉后该提供商从主界面模型选择栏里消失，重新打开即恢复。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:DeepseekDays/dsh-provider-toggle#08fb351a26c3ed309e048b8ae4f9d1e7bed7c3fcProvider Toggle 以 dsh-provider-toggle 发布，当前版本为 1.0.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
English | 中文
One-click enable/disable switch for every model provider in DeepSeek Harness, sitting in Settings → Models right next to Edit. Turn a provider off and it leaves the composer's model picker; turn it back on and it returns.
The switch to the left of Edit on every provider row The switch lands to the left of the Edit button on each row (screenshot from the offline geometry harness — all 3 rows pass).
Settings → Models
┌──────────────────────────────────────────────────────┐
│ opencode-go ● ( ) Edit Delete │ ← switch, left of Edit
│ ↑ │
└──────────────────────────────────────────────────────┘
One line from GitHub:
dsh plugin --profile desktop add github:DeepseekDays/dsh-provider-toggle
(use your own profile name instead of desktop if different).
From a checkout — same three steps, but without running pnpm:
node install.mjs # install or repair
node install.mjs --dry # show what would change
node install.mjs --uninstall # uninstall (keeps the folder)
install.mjs does exactly three things (it never runs pnpm, so it will not rebuild
node_modules and cannot interrupt a live session): create a directory junction, add a
link: dependency to the profile's package.json, and append the package name to
dsh.profile.bundles. It writes a .bak-provider-toggle-* backup before touching the
manifest. The profile defaults to ~/.dsh/profiles/desktop; set DSH_PROFILE_DIR to
target another one.
Then fully quit DSH, tray included, and start it again — bundle lists and the browser module table are read at startup, so HMR will not pick up a new package.
There is exactly one load-bearing fact: DSH's model picker only renders provider groups that have at least one model.
@deepseek-ai/dsh-api-session-controller's buildModelCatalog() contains
groups.filter(group => group.models.length > 0)
So the plugin hooks in as lightly as possible — by wrapping ctx.llm.listModels():
| Half | File | What it does |
|---|---|---|
| host | index.js | A disabled provider route makes listModels() return [] → the group is dropped → it disappears from the picker |
| client | client.js | Renders @deepseek-ai/dsh-client-ui-primitives' <Switch> into the settings.models.provider-card keyed slot; reads and writes through the existing ctx.remote.settings |
It only affects the catalog and the picker, never routing. dsh-llm says so itself:
"Core routing accepts unlisted model ids; catalog-driven entry points such as the GUI may
require membership." Sessions already using one of these models keep working; the model
simply stops being offered in the picker.
In the plugin's own settings namespace (Config.disabled, marked .volatile()):
cordis.patch.yml (the id: dsh-provider-toggle entry).ctx.remote.settings.describe() / mutate() directly — no custom
remote endpoint.cordis.patch.yml, but it
rewrites from in-memory state and our value is already in memory, so it is not clobbered..volatile() makes changes take effect hot: the loader emits
loader/volatile-update, the plugin broadcasts llm/adapters-updated, and the browser
reloads the model catalog on the spot. Toggling never needs a DSH restart.settings.models.provider-card is a keyed slot: rendering matches a registration's
key against renderSlot(name, props, { entryKey: row.entry.settingsNs }). All of pi-ai's
routes (DeepSeek / openai / opencode-go / custom relays…) share the same settingsNs —
they differ only by settingsPath: ["providers", <route>]. So one keyed registration
renders once per row, with that row's provider in props. Namespaces of their own (such
as deepseek-account) get a second registration.
Slot content renders below rowHead by default (inside the same card). To sit left of
Edit, the component measures li / [class*="rowHead"] / [class*="rowActions"] with
getBoundingClientRect() after mount and absolutely positions itself there (class names are
CSS Module hashes, hence the [class*=...] substring selectors). If it cannot measure, it
falls back to inline layout — the feature keeps working.
settings.models.provider-card keyed slot and
@deepseek-ai/dsh-client-ui-primitives (tested against DSH Desktop 2.0.17 /
dsh-base 0.2.0-rc.2).dsh.bundle in package.json, so it installs with plain dsh plugin add.ctx.llm.listModels() at runtime and
restores it on unload (reference-counted, so repeated apply/unload does not stack wrappers).dsh-ofm-model-manager (per-model enable/disable and renaming). Both
wrap the same listModels, both are reference-counted, and their preference keys are
independent.node test-filter.mjs # host logic: 16 assertions
node test-client.mjs # client logic: 13 assertions
node preview/placement-check.mjs # layout geometry + screenshot
Three offline harnesses — no DSH session, no network required for the first two:
| File | Covers |
|---|---|
test-filter.mjs | host logic: does a disabled provider really leave the catalog, does re-enabling restore it, does unload revert, does a repeated apply stack, the fallback path when the config is not a ref |
test-client.mjs | loads client.js with a minimal fake React: slot registration shape, Switch state, the exact mutate arguments, silent no-render when the namespace is unavailable |
preview/placement-check.mjs | geometry: extracts the real CSS and the real placeSwitch() from a DSH installation, rebuilds the DOM, measures through local Edge + CDP and screenshots |
The suites re-implement the expected behaviour (they replicate DSH's
groups.filter(group => group.models.length > 0) rather than calling the code under test)
so they cannot pass by agreeing with themselves. The placement harness needs DSH_APP_DIR
(default F:/DSH/DSH Desktop/resources/app) and EDGE_PATH.
| Symptom | Cause / fix |
|---|---|
| No switch appears at all | The bundle was not read: fully quit DSH (tray included) and start again. Confirm the package name is in dsh.profile.bundles. |
| The switch renders inline instead of left of Edit | Measurement failed — DSH probably changed the Settings row structure (no more rowHead / rowActions class substrings). The feature still works. |
| Flipping the switch does nothing | The settings namespace is not exposed (check the console for settings namespace "dsh-provider-toggle" is not exposed), or the write was rejected because the field is not volatile. |
| A provider you disabled vanished | That is the intended behaviour. To recover: Settings → Models → flip it back, or clear config.disabled in the id: dsh-provider-toggle entry of the profile's cordis.patch.yml. |
deepseek-account. @deepseek-ai/dsh-client-ui-settings-models calls
remote.session.modelCatalog() once while building the row list and then runs
rows.filter(row => row.entry.provider !== "deepseek-account" || row.accountAvailable === true)
— so once this provider is dropped from the catalog, its own row disappears too and
there is no UI left to turn it back on (you would have to edit the profile's
cordis.patch.yml by hand).config.disabled in the
id: dsh-provider-toggle entry of the profile's cordis.patch.yml.rowHead / rowActions in the class names) the switch falls back to inline display:
still functional, just no longer left of Edit.index.js host half: filters listModels() per provider
client.js browser half: the switch in the Settings row
cordis.patch.yml bundle declaration
install.mjs install / uninstall / dry run
preview/placement-check.mjs offline geometry harness
preview/placement.html DOM replica used by the harness
preview/*.png harness screenshots
test-filter.mjs host suite
test-client.mjs client suite
test-resolve-hook.mjs module resolution smoke test
assets/ screenshots used by this README
MIT — see LICENSE.