DeepSeek Harness Plugin Hub

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

探索

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

社区

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

相关链接

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

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

Run Watchdog — DeepSeek Harness 插件(DSH Plugin)
← Plugins
R

dsh-run-watchdog

Run Watchdog

面向用途的 DeepSeek Harness 长时间运行命令监控

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

npx -y @deepseek-ai/dsh plugin --profile web add github:Hirate99/dsh-run-watchdog#7ab0db2c063d20f0af1627bfd02d169922cea1b0
README兼容性版本

兼容性与来源证明

Run Watchdog 以 dsh-run-watchdog 发布,当前版本为 0.1.1。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

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

版本

0.1.1stable
2026/10/15

相关插件

正在加载相关插件…

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

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

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

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

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

相关插件

继续浏览 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-run-watchdog

English | 简体中文

Monitor long-running DeepSeek Harness jobs using their purpose and live output. Alert the main agent when training, builds, tests, or data processing need attention.

Supports DeepSeek and Jev. Version 0.1.1.

Demo

Training alert in DSH Desktop

The watchdog catches NaN during training and alerts the agent.

Installation

Desktop: install from GitHub

Open Plugins → Add plugin, paste the repository URL, then select Install → Enable now:

https://github.com/Hirate99/dsh-run-watchdog

Configure it under Plugins → dsh-run-watchdog.

The v0.1.1 release package is also available. Release assets are fixed snapshots; the repository URL follows the default branch.

Build from source

Requires Node.js ≥ 22.19 and DSH native bash / pwsh tools with background job support.

npm ci
npm run check
npm pack

Install the generated dsh-run-watchdog-0.1.1.tgz through Desktop's plugin page. Alternatively, fully quit Desktop and use its bundled CLI on Windows:

& "$env:LOCALAPPDATA/Programs/DeepSeek Harness/resources/runtime/cli/bin/dsh.cmd" plugin --profile desktop add "<absolute-package-path>/dsh-run-watchdog-0.1.1.tgz"

Reopen Desktop and configure the plugin. This package has not been published to npm.

Development dependencies are pinned to DSH 0.2.1-alpha.3 and Cordis 4.0.5-alpha.2. Desktop 0.2.0-rc.2's bundled runtime was also tested previously. Rerun integration tests when upgrading the host.

Configuration

  • DeepSeek reuses your signed-in DSH account by default, or the API key in DSH model settings when signed out. Select the monitoring model on the plugin page. Custom endpoints or credential references continue to use API keys.
  • Jev shows a dedicated API key field. The key is saved in DSH's credential store.
  • Shadow mode is the default: evaluate without notifying or stopping jobs. Set recordPath to save decisions.
  • Enforce mode delivers alerts to the original conversation and wakes an idle agent.

Save changes before selecting Test connection. Changes apply to newly attached monitors.

SettingDefaultDescription
firstCheckMs10000Delay before the first check
judgeTimeoutMs8000Model request timeout
stopThreshold0.8Jev probability threshold for automatic stopping
allowAutoStopfalseAllow individual jobs to request automatic stopping
recordPathUnsetLocal JSONL decision log
recordAfterMs3600000Observation time after an alert, when recording is enabled

Requests include the task purpose, command, and up to 16000 characters of recent output. Local records contain the same evidence. Credentials are resolved from DSH first, then from the environment variable named by apiKeyEnv.

How it works

The plugin supplies instructions to the main agent. The agent starts a native background job and attaches watch_job; users do not need to name tools or provide tool parameters.

Attachment returns immediately. Jobs are monitored concurrently with independent log cursors. Monitoring does not consume the agent's output, start commands, or restart jobs. The agent can read further output with job_output.

The judge can choose another check in 10, 30, 60, 120, 300, or 600 seconds, request attention, recommend stopping, or report uncertainty:

  • Jev can stop a job only when its stop probability reaches the threshold and both deployment settings and the individual job authorize automatic stopping. Otherwise, the decision becomes an alert.
  • A preferred stop/notify choice, or combined stop and notify probability of at least 0.4, triggers an alert.
  • Continue probabilities are combined before comparison with uncertainty; the most likely interval is then selected.
  • DeepSeek does not return probabilities, so stop recommendations only notify.

Each monitor alerts at most once. Normal completion uses native DSH notifications. An alert cancels job_output(wait=true) waits in the same session, including waits started while the alert is pending delivery. This does not cancel the agent or stop background jobs. Other blocking tools are not interrupted.

Monitoring ends when the job finishes or the plugin unloads. Unloading does not stop jobs; restarting the plugin does not restore monitors. Failed model requests retry using fallback intervals.

Development

npm run check

Runs the build, type checks, and offline regression tests without API keys. Coverage includes decision thresholds, chunked and truncated logs, immutable state, scheduling boundaries, background recording, concurrent jobs, wait interruption races, DSH tools, and real child processes.

Online connection tests call the selected provider:

npm run smoke -- jev
npm run smoke -- deepseek

Set WATCHDOG_MODEL to override the test model. Offline tests do not establish model quality across real tasks, and the demo does not guarantee consistent autonomous tool selection.

FileResponsibility
src/output.tsPure log accumulation and evidence statistics
src/decision.tsModel input, action selection, and comparison rules
src/monitor-state.tsPure check snapshots and scheduling
src/monitor.tsLog reads, model requests, and the monitoring loop
src/jobs.tsDSH job access and independent cursors
src/interrupt-wait.tsRelease output waits when alerts arrive
src/index.tsTool registration, alert delivery, and Cordis lifecycle
src/providers.tsDeepSeek / Jev request adapters
src/settings.ts, src/client.tsxCredentials, connection tests, and settings UI

docs/ and .integration/ contain local verification artifacts and are excluded from version control. README demo assets live in assets/.

CI and releases

GitHub Actions runs the full checks on Windows and Linux with Node.js 24 for pushes to main and pull requests. Each job uploads an installable .tgz artifact. Tests use local fixtures and do not need API keys.

To publish a release, push a tag matching package.json (currently v0.1.1). Both platforms must pass before the workflow creates the GitHub Release and uploads the package. Publishing uses the built-in GitHub token; no npm token is needed. Existing releases are not overwritten automatically.