DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

Model Auto Hot Switch — DeepSeek Harness 插件(DSH Plugin)
← Plugins
M

dsh-model-auto-hot-switch

Model Auto Hot Switch

DeepSeek Harness (dsh) 按任务自动切换模型:包含图像的任务自动路由至视觉模型,其他任务继续使用默认模型。不增加额外 token,不干扰上下文。

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add github:SHUJILAI/dsh-model-auto-hot-switch#2a3a3ff90046fcd45ac3b0add6d90bf7cfca5bd1
README兼容性版本

兼容性与来源证明

Model Auto Hot Switch 以 dsh-model-auto-hot-switch 发布,当前版本为 0.1.0。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
web
发布来源
github
Registry 更新时间
2026/8/28

版本

0.1.0stable
2026/8/28

相关插件

正在加载相关插件…

最新版
0.1.0
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
未提供
文件数
未提供
Surface
web
许可证
MIT
发布源
github
GitHub
★ 0
周下载
0
最近提交
2026/8/28
查看源码 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录

相关插件

继续浏览 models-usage 分类下经过校验的插件。

Usage@linxin666/dsh-usagedsh Web GUI 的使用统计插件:检测各提供商余额和编码计划配额,并提供实时令牌使用记录,以及当前提供商的专属宠物气泡Whale Widgetdsh-whale-widgetDSH Web 界面右下角的 DeepSeek 余额小鲸鱼挂件:余额/今日已用/峰谷定价、自定义泡泡点击序列(文本/余额/今日/峰谷/图片/随机语句与并列加权选择)、逐行样式与字体、悬浮快捷编辑、音效与每轮消耗、自定义角色/动图/音效、吸附与翻转自定义Usage Stats@ychris12138/dsh-usage-statsdsh Web GUI 的令牌使用热力图、提供商余额和订阅配额Codex Connectdsh-codex-connect用于 DeepSeek Harness 的 ChatGPT OAuth 和 Codex 模型。

README

⚡ dsh-model-auto-hot-switch

Automatic per-task model hot-switching for DeepSeek Harness (dsh). Image-aware tasks route to the vision model automatically; every other task keeps the default model you chose. Zero extra tokens, zero context disturbance, one click to enable.

中文说明


What it does

DeepSeek Harness models do not all accept images. When you ask the agent to read a screenshot, an OCR job, or any image file, the request should go to a vision-capable model — while plain chat and coding keep the fast default model. This plugin makes that switch automatic and per-task, inside the same session:

  • Vision task (the step's messages carry an image) → routed to the discovered vision model, e.g. deepseek-v4-flash-vision-exp
  • Everything else → the exact default model you selected, configuration returned untouched

Why it costs nothing

  • Zero extra tokens. Task classification is pure local code (does the step contain an image block?). No classifier model call, no prompt rewrite, no duplicated requests.
  • No context disturbance. Only the provider/model fields of the frozen per-step call configuration are replaced, through the harness's own agent/request extension point. Messages, system prompt, tools, and session state are never rewritten.
  • No overhead on normal tasks. Non-image steps restore the session's default route in one field swap when a previous step left the vision model in the held request header (and return the configuration untouched otherwise) — no classifier call, no extra request.

Installation

Requires DeepSeek Harness (dsh) with a Web profile.

# from npm
dsh plugin --profile web add dsh-model-auto-hot-switch

# or straight from GitHub
dsh plugin --profile web add github:SHUJILAI/dsh-model-auto-hot-switch

Restart dsh web, then click the floating ⚡ button (bottom-right) to switch automatic hot-switching on. The readout shows:

  • the routing target for vision tasks (the first discovered model whose capability declares image input),
  • the default model all other tasks keep using,
  • the most recent hot-switch event.

The toggle persists in config.json beside the package and survives restarts.

Prerequisites

  • A vision-capable model in your provider catalog. The plugin auto-discovers it through llm.listModels / llm.resolveModelInfo — no configuration needed. For the official DeepSeek provider this is deepseek-v4-flash-vision-exp (available on the DeepSeek API). Without any vision model, the toggle still works but vision routing stays idle and the readout says so.
  • The read_image tool's own gate must also see the vision model, which requires the dsh build whose DeepSeek adapter declares image input for it.

How it works

user sends an image task
   │
   ▼
agent/pre-step ──► contains image? ── yes ──► mark this step as vision
   │                    │
   │                    no
   ▼                    ▼
agent/request ──► return the default config   return config with provider/model
                 (untouched, zero overhead)   swapped to the vision model

The classification runs per (session, turn, step) and is consumed by the matching agent/request call, so a later step of the same turn re-classifies independently. Subagents get the same treatment under their own sessions.

Configuration

None. The single toggle is the whole surface:

FieldMeaning
enabled (in config.json)true routes image tasks to the vision model; false leaves every request on the default model

The preferred vision model id is deepseek-v4-flash-vision-exp; if absent, the first discovered image-capable model wins.

Compatibility

  • Works with dsh Web profiles (routes under /plugins/dsh-model-auto-hot-switch/state).
  • Headless profiles: routes are skipped, the hot-switch logic still runs from the persisted toggle.
  • Does not depend on any official @deepseek-ai/* runtime package; no peerDependencies.

Development

npm test          # package-shape + syntax smoke checks

License

MIT — see LICENSE.