DeepSeek Harness Plugin Hub

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

探索

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

社区

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

相关链接

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

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

Goal Auto — DeepSeek Harness 插件（DSH Plugin）
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
G

@huanlin/dsh-goal-auto

Goal Auto

适用于长时间运行目标会话的按会话自动恢复开关：标记会话后，harness 重启时会自动恢复代理，其活动目标会继续运行。

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

npx -y @deepseek-ai/dsh plugin --profile web add github:FuWenLianggit/dsh-goal-auto#77332403d8288ceb2822b3ff7b42f50b778cea08
README兼容性版本

兼容性与来源证明

Goal Auto 以 @huanlin/dsh-goal-auto 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。

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

版本

0.1.0stable
2026/9/6

相关插件

正在加载相关插件…

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

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

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

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

认领这个 Plugin →
报告问题

相关插件

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

Headless@deepseek-ai/dsh-headlessdsh one-shot bundle：基于 dsh-base 的直接核心 Agent/Session 运行器，不包含 Host、HTTP 或浏览器层Experimental Agent Team Web Profile@deepseek-ai/dsh-experimental-agent-team-web-profile用于 Agent Teams Remote 和 UI 插件的实验性 Web 配置层Subagent Codex@deepseek-ai/dsh-subagent-codex基于官方 app-server 协议的一次性 Codex 子代理提供程序Subagent Claude Code@deepseek-ai/dsh-subagent-claude-code基于官方 Agent SDK 的一次性 Claude Code 子代理提供方

README

dsh-goal-auto

Per-session auto-resume toggle for long-running goal sessions in DeepSeek Harness (DSH).

What it does

  • Adds a 🔁 toggle to the session header action bar.
  • Marked sessions are resumed automatically after the harness restarts: the agent is reloaded, its agent preset is mounted, the goal is re-armed, and the goal-round-driver keeps driving rounds without any manual click.

Why resume is not enough (the three layers)

A plain agents.resume() after a restart leaves the session dead. Three things must happen before a goal session runs again:

LayerProblemFix
Model variablesempty options -> {{model}}/{{provider}} unset, prompt assembly crashespass explicit agentOptions.provider/model/maxTokens
Tool setresumed agent has no tools (preset not applied)mount the agent preset in the resume setup
Goal driverafter restart goal.activation resets to disarmedcall goals.resume() to re-arm; driver auto-injects next round

Adaptive preset

The preset is read from the session header (header.agentPreset) and mounted per session, falling back to the configured default when the header has none.

Install

dsh plugin --profile web add file://<this repo path>

Or, as used here: keep the plugin in <DSH_HOME>/plugins/dsh-goal-auto and add a file:/link: dependency in the profile's package.json + a junction under profiles/<name>/node_modules/@huanlin/dsh-goal-auto.

HTTP surface

  • GET /__goal-auto/state -> enabled map
  • POST /__goal-auto/toggle -> flip a session flag (+ start now if enabled)
  • POST /__goal-auto/resume-now -> force resume of one session (diagnostics)

State lives in <DSH_HOME>/goal-auto-state.json (per-instance; safe to edit by hand while the harness is stopped). Logs go to <DSH_HOME>/goal-auto.log.

Layout

  • src/index.js — cordis bundle (host): state, HTTP, boot auto-resume
  • src/client.js — client bundle: header 🔁 toggle
  • cordis.patch.yml — loader insert for the profile

Watchdog requirement (IMPORTANT)

The plugin resumes sessions when the harness starts. It does not keep the harness process alive. If dsh web crashes, hangs (TCP alive but HTTP dead), or is killed, nothing inside the process can restart it — you must run a process watchdog outside the harness.

Without a watchdog:

  • the service dies and nobody brings it back;
  • after a machine reboot nothing auto-starts;
  • goal sessions only resume on the next manual start.

A reference watchdog system is included in this repository under watchdog/. It is the same system used by the author:

watchdog/
  watchdog-instance.ps1   per-instance resident watchdog
                          health = TCP listening AND HTTP 200
                          sliding window catches hard hangs AND intermittent
                          "slow death" (5+ HTTP failures in last 10 probes)
                          boot grace 120s so fresh starts are never killed
  start-instance.ps1      auto-init + start one instance (seeds settings,
                          credentials, agent presets, plugin environment)
  control.ps1             unified control: start|stop|restart|status [instance]
  instances.txt           instance registry: name|home_dir|port

Design notes (all learned the hard way):

  • Watchdogs are per instance (one process per instances.txt row), all sharing one script. A single mutex per instance prevents duplicates.
  • Auto-start at logon via the Windows Startup folder (a small .vbs per instance calling watchdog-instance.ps1 -Name <instance>).
  • instances.txt and every .ps1 must stay pure ASCII — Windows PowerShell 5.1 mis-parses UTF-8 without BOM, and the harness rejects JSON files that carry a BOM.
  • Health probes use .NET HttpWebRequest, not curl.exe (curl in 5.1 intermittently returns 000 against a healthy instance).
  • Add a crash circuit breaker: if an instance dies N times within a short window, stop relaunching and alert — otherwise a plugin bug turns the watchdog into an infinite restart loop.

Configure instances.txt for your own homes/ports before use. The watchdog is generic; the paths under watchdog/ reference the author's layout only as an example.