Model visibility manager for DeepSeek Harness: hide or show any model in the conversation model selector from a dedicated settings page. Per-model switches, search, provider-level batch actions, reset-all. Zero intrusion - writes only its own hidden list, never the provider config; hiding a model in use never interrupts a running session.
Install
# from npm (prebuilt)
dsh plugin --profile web add dsh-model-visibility
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:Lzh3070/dsh-model-visibility
Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).
README
English · 中文
Model visibility for DeepSeek Harness: control which models appear in the conversation model selector.
Installs a dedicated Model visibility settings section (right after 模型 / Models in the left nav):
- 🔍 Search — live filter by model name / id / provider
- 🎚️ Per-model switches — hide a model and it disappears from the selector instantly; flip back to restore
- 📦 Provider-level batch — hide or show every model of one provider in one click
- ♻️ Reset all — clear the hidden list
- 🛡️ Zero intrusion — writes only the plugin's own hidden list, never your provider config; hiding a model a session already uses never interrupts that session
- 🆕 New models visible by default — the plugin remembers what to hide, not what to show
Preview
Requirements
- DeepSeek Harness ≥ 0.1.1-rc.2 (earlier versions untested)
- Node.js 22+
Install
dsh plugin --profile web add dsh-model-visibility
Restart dsh web to activate.
How it works
- Host half (
lib/index.js): owns themodel-visibilitysettings section (the hidden list) and wrapsctx.llm.listModelsat its source, so bothsession.models(the conversation selector) andllm.models(the settings page) receive the filtered catalog. Catalog membership is advisory in the harness, so hiding a model a session already uses never breaks that session's dispatch. - Browser half (
lib/client.js): registers asettings.sectionpage; page state is the union of the filtered catalog and the hidden entries, each hidden entry labeled by the display-name snapshot captured when it was hidden.
Uninstall
dsh plugin --profile web remove dsh-model-visibility
Uninstalling restores everything: the plugin never writes provider config, and the hidden list dies with the package.
License
MIT
Links
More in this category
bowenliang123/dsh-context★ 1192
DSH context insight panel: Context dashboard + /context command + Context browser — one-stop context lifecycle management with categorized composition, content details, evolution trends, compaction/injection events, and stats.
Han-1413141/dsh-cost-meter★ 232
Per-session and daily API cost, budget with usage %, official balance, history dashboard, and one-click official price sync with peak/off-peak pricing.
zh667/TokenLedger★ 190
Sidebar usage panel that attributes tokens to the relay site that served each request, read from your existing provider config: today/month/all-time totals, per-site and per-model breakdowns, a year activity heatmap, and New API / Sub2API / DeepSeek balances.
wssfk12138/dsh-damage-pulse★ 145
Tracks DeepSeek token usage, per-call and session costs, and account balance with cache-aware charge animations in the DSH Web UI.
Ychris12138/dsh-usage-stats★ 132
Multi-provider usage dashboard with provider/model token breakdowns, calendar drill-downs, account balances, and OpenCode Go / Z.ai subscription quota tracking.
feibi-mochi/deepseek-harness-control-center★ 66
DeepSeek Harness control center for official balance monitoring, per-session costs and tokens, third-party token totals, completion alerts, official recharge, flexible layouts, and agent-assisted session controls.
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.