DeepSeek Harness Plugin Hub

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

探索

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

社区

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

相关链接

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

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

DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
U

dsh-update-check

Update Check

每次启动 DeepSeek Harness 检查一次更新:报告应用、插件和 CLI 的新版本,并在点击时更新配置文件插件。

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

npx -y @deepseek-ai/dsh plugin --profile web add github:1731988818/dsh-update-check#26bbac742972726e1f77c7fe5d78d1d94611a34e
README兼容性版本

兼容性与来源证明

Update Check 以 dsh-update-check 发布,当前版本为 1.5.3。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

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

版本

1.5.3stable
2026/10/22
1.5.2stable
2026/10/22
1.5.0stable
2026/10/22

相关插件

正在加载相关插件…

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

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

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

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

认领这个 Plugin →
报告问题

相关插件

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

Web App@deepseek-ai/dsh-web-appdsh 浏览器界面捆绑包:位于 dsh-base 之上的 Web 补丁层,加上运行时粘合插件(提供前端 dist、Web 界面提示符、bash 运行时变量和 URL 行)Sdk Minimal@deepseek-ai/dsh-sdk-minimal独立的最小 SDK 配置包:JSON-RPC、一个 DeepSeek 适配器、持久化 Shell 和 JSONL 会话Sdk App@deepseek-ai/dsh-sdk-appdsh SDK 配置包:基于 dsh-base 提供 stdio JSON-RPC 服务和进程生命周期管理Experimental Inspector@deepseek-ai/dsh-experimental-inspector用于 Host 调试和 Client Runtime 检查的实验性跨 realm CDP hub

README

dsh-update-check

Startup update check for DeepSeek Harness: one check per launch, one card, one click per update.

English | 中文

The update card: two plugin rows with an Update button, one market row marked manual, and a footer with update-all and check-again links.

A profile is a list of package versions, and those versions move on without you: a plugin ships a fix, a market releases a patch, the app publishes a new nightly. The running app says nothing about any of it.

This plugin fills that gap. Once per launch it compares what you are running against what is published, and when something is behind it puts one card in the corner of the window — a row per outdated package, a button per update, and nothing at all when everything is current.

It reads versions and asks before installing. It never upgrades on its own, never touches a package you did not click, and serves nothing but version numbers over its route.

What it checks

TargetCurrent version read fromNewer version read from
DeepSeek Harnessresources/app.asar/dsh/package.json of the running buildthe official nightly.yml feed
Profile pluginsdependencies in the running profile's package.jsonthe npm registry
rea-agents CLIthe global install under %APPDATA%\npm\node_modules\rea-agentsthe npm registry

Each target is checked on its own, so one unreachable registry degrades a single row to unknown instead of failing the whole check. npm lookups fall back from registry.npmjs.org to registry.npmmirror.com.

What you see

A card in the bottom-right corner, only when something is behind:

  • one row per outdated target — package 1.2.3 → 1.2.4, four rows shown, the rest collapsed into a count
  • 更新 on rows that can be installed from here, 全部更新 in the footer to do them in one go
  • 需手动 on rows that cannot — the app itself, the CLI, and plugin markets (see Limits)
  • 重新检查 to run the check again, × to dismiss. Leave it untouched and it closes itself after 15 seconds — hovering pauses that countdown, and an install in progress holds it open

Nothing renders when everything is current.

The card is offered once per application start, not once per page load. The Host hands the offer out a single time, and the first page to read it takes it — so dismissing it, switching panels or reloading the page keeps it quiet. Quit Harness and start it again to see a fresh check.

The interface text is Chinese today. The layout and the route are language-independent.

How it works

  1. The Host half registers GET /dsh-update-check/api/status and starts one check when the bundle activates.
  2. That check runs with six-way concurrency: one feed read, one npm read per plugin, one local version read for the CLI.
  3. The Client half polls the route and renders into the shell.overlay slot — the frame-wide layer above every column, so the card belongs to no session and no panel.
  4. 更新 posts { "name": "..." } to /dsh-update-check/api/install. The route accepts only names the current check marked outdated and installable, so it cannot be used as a generic install proxy.
  5. The install is two steps: installBundle, and if the manager answers already-installed, removeBundle followed by installBundle again. That is the same shape the app's own Plugins page uses, because this manager has no in-place update.
  6. When the install settles, the check runs once more and the card reflects the new versions.

Limits

  • Markets cannot update themselves. Removing the bundle unloads the code that would run the reinstall (upstream issue #900), so those rows stay manual and show the command to run instead.
  • The app itself is a desktop build behind the nightly feed; the card reports the newer version and leaves the download to you.
  • rea-agents is a global npm install, not a profile dependency: npm i -g rea-agents@latest.
  • A version is compared, never assumed. A target with no readable current version, or a registry that answers nothing, is reported unknown rather than counted as up to date.
  • Replacing a plugin reloads its Host module. That is what makes an update take effect without restarting, and it also means the update offer of this plugin resets whenever it is itself reinstalled.

Install

dsh plugin --profile <profile> add github:1731988818/dsh-update-check

That registers the bundle in the profile's dsh.profile.bundles as well, so the next launch loads it.

pnpm caches git dependencies by commit hash, so run the same command again after a push to pick up new code.

Inside a running session the same install is one tool call:

plugin_manager install_bundle github:1731988818/dsh-update-check

Requires DeepSeek Harness 0.2.1 or newer, on the desktop or the web app.

Route

MethodPathPurpose
GET/dsh-update-check/api/statusSnapshot of the last check. ?refresh=1 starts a new one.
POST/dsh-update-check/api/installBody { "name": "package-name" }. Accepts only a plugin the current check marked outdated and installable.

The route returns version numbers and package names only. It reads no files from the request and installs nothing the card did not offer.

Uninstall

dsh plugin --profile <profile> remove dsh-update-check

Nothing is left behind: the plugin writes no files, keeps no state between launches, and its route disappears with the bundle.

License

MIT