← Back to list

dsh-model-visibility

DeepSeek Harness Other Low risk

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.

DSH 模型可见性管理:在独立的设置分区页里按渠道/模型隐藏或显示模型选择菜单中的条目。逐模型开关、实时搜索、渠道级批量隐藏/显示、一键恢复全部。零侵入——只写插件自己的隐藏列表,不改 Provider 配置,隐藏正在使用的模型不会中断会话。

How to install

DeepSeek Harness dsh plugin add dsh-model-visibility

About

dsh-model-visibility **English · 中文** DeepSeek Harness 的模型可见性插件:控制哪些模型出现在对话界面的模型选择菜单里。 安装后在设置左侧导航提供一个独立的「**模型可见性**」分区页(紧跟「模型」): 🔍 **搜索** —— 按模型名/ID/渠道名实时过滤 🎚️ **逐模型开关** —— 隐藏的模型立即从选择器消失,显示即恢复 📦 **渠道级批量** —— 一键隐藏/显示某个 Provider 的全部模型 ♻️ **一键恢复全部** —— 清空隐藏列表 🛡️ **零侵入** —— 只写插件自己的隐藏列表,不改你的 Provider 配置;隐藏正在使用的模型不会中断该会话 🆕 **新模型自动可见** —— 插件只记录"要隐藏什么",Provider 新广告的模型默认出现 预览 要求 DeepSeek Harness ≥ 0.1.1-rc.2(更早版本未测试) Node.js 22+(构建与运行) 安装 sh dsh plugin --profile web add dsh-model-visibility 重启 dsh web 后生效。 工作原理 **宿主半**(lib/index.js):持有 model-visibility 设置段(隐藏列表),并在源头包装 ctx.llm.listModels——会话选择器(ses…

Recommendation signals

48 Tool quality · Based on stars, downloads, maintenance, security and docs
– User interest · Adjusted by in-site views, install copies and download clicks
48 Overall
0views
0unique visitors
0install copies
0download clicks
0outbound clicks

Meta

License
MIT
Language
TypeScript
GitHub stars
1
mo. downloads
786
Last push
2026-09-11
Created
2026-08-27

Links

Basic safety check

Findings
None
Sources
curated:awesome-dsh-plugin.com, curated:awesome-dsh-plugin/awesome-dsh-plugin
Topics
deepseek-harness, dsh, dsh-plugin, model-management, model-selector, model-visibility, typescript

Related plugins

DeepSeek Harness
Score73

TokenLedger

zh667/TokenLedger

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.

☆ 202 ↓ 1.4K Other ↗
DeepSeek Harness
Score71

dsh-context

bowenliang123/dsh-context

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.

☆ 1.5K ↓ 79.7K Other ↗
DeepSeek Harness
Score69

dsh-usage-statistics-panel

HaoyueQin/dsh-usage-statistics-panel

Usage statistics settings panel: 26-week activity heatmap, daily token trend with a cache hit-rate curve, per-model donut and breakdown, time-range filters, summary cards, one-time historical backfill and lossless rebuild.

☆ 9 ↓ 3.3K Other ↗
DeepSeek Harness
Score68

dsh-all-usage

ParticleLight/dsh-all-usage

Analyze usage across models, providers, workspaces, and time ranges — including custom start/end dates over the full retained history — with live cache-hit visibility and separate model and provider breakdowns. Includes hourly single-day trends, daily cross-day trends, a 53-week GitHub-style heatmap, usage streaks, model and workspace Token-share donut charts with Token, cost, and percentage details, independent combinable filters, cache-efficiency trends, DeepSeek account balance, workspace aliases, CSV export, and a durable ledger that preserves successfully flushed usage after session deletion — and after a workspace is deleted, where its recorded usage is summed into one Deleted row — and rebuilds incrementally — on restart, unchanged sessions are applied from the ledger without re-reading their logs (a per-session log revision is the change signal), and only changed/new events are folded. The workspace registry is kept fresh automatically through the DSH domain/changed probe: only added/removed workspaces are reprocessed incrementally, unchanged workspaces reuse their computed aggregates and ledger with zero rescan, and usage is strictly limited to DSH-registered workspaces (unregistered cwds are ignored). After a scan, lightweight revision status fetches full history only when the Host/data state changes and exposes non-sensitive sync health (revision reuse, rereads, ledger recovery, and failures). Token accounting is explicit: input is fresh (cache read/write and reasoning are separate buckets) and zero-usage replays never overwrite recorded usage. Chinese uses local time, English uses UTC; API access is loopback-only.

☆ 8 ↓ 2.8K Other ↗