dsh-reset-handoff
标准交接协议，确保 DSH 不会自行重启：一个主机插件，用于提交 JSON 重置请求，由外部运维代理（例如 Hermes）执行 preflight-snapshot → restart → health-check → recover，然后将结果返回给发起请求的会话。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:nicecx/dsh-reset-handoff#3a4608d58f85f557ca2b28f8a16bf2a3e954445cReset Handoff 以 dsh-reset-handoff 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
DSH never restarts itself. A host plugin that hands reset requests to an external ops agent over a versioned JSON protocol — preflight-snapshot → restart → health-check → recover — then delivers the result back to the requesting session after reboot.
A long-lived DeepSeek Harness (DSH) instance needs to restart for many reasons: reload plugins/config, apply settings, recover from a wedged state. But the agent inside DSH should not restart DSH itself:
The safe pattern is a handoff: DSH writes a request, a separate, independent ops agent (here: Hermes Agent) reads it, runs the restart with preflight/health/recovery, and writes a result that DSH reads back after it comes up.
[DSH] agent calls reset_handoff(reason)
│ writes request.json (JSON protocol)
│ (optional) triggers the external executor
▼
[ext] ops agent reads request.json
│ 1. preflight — snapshot live sessions, relay state, pending jobs
│ 2. GATE — pre-restart maturity gate (see below)
│ 3. restart — restart the dsh web service (macOS launchd)
│ 4. health — poll http://127.0.0.1:3080 until 200 (with timeout)
│ 5. recover — verify relay/auth-proxy self-heal, list interrupted sessions
│ 6. result — write result.json (status done/failed + per-stage detail)
▼
[DSH] after reboot, the plugin reads result.json and delivers a readable
summary back into the requesting session (followup), so the agent
that asked can resume its interrupted work.
The reference executor refuses to restart unless it is safe to do so. It checks:
pending.json has an empty pending list (a restart would otherwise drop the approval stack).MIN_FREE_DISK_MB (default 500 MB).RESTART_COOLDOWN_SEC (default 60 s) since the previous restart, to break crash loops.If any condition fails, the executor writes result.json with status: "failed", restart: { ok: false, gated: true }, and a gate array listing each failed condition with its detail — and does not restart. The requesting agent (or user) sees the exact reason and decides when it is safe to retry.
| Tool | Purpose |
|---|---|
reset_handoff(reason, scope?) | Submit a reset request to the external ops agent. Never restarts DSH in-process. |
reset_status() | Query the latest request and its result (read-only). |
Both tools are registered host-wide, so every session's agent can call them when a reset is needed.
The plugin and the executor are decoupled — they only share two JSON files under ~/.dsh/reset-handoff/ (override with DSH_RESET_HANDOFF_DIR):
request.json (written by DSH):
{
"schema": "dsh-reset-handoff/request",
"version": 1,
"id": "<uuid>",
"requestedAt": "2026-08-30T12:00:00+08:00",
"reason": "重新加载插件配置",
"sessionId": "<requesting session id>",
"requester": "dsh-reset-handoff",
"scope": { "restartDshWeb": true, "healthCheck": true, "recoverInterrupted": true }
}
result.json (written by the executor):
{
"schema": "dsh-reset-handoff/result",
"version": 1,
"requestId": "<uuid>",
"status": "done",
"startedAt": "...",
"finishedAt": "...",
"preflight": { "liveSessions": ["..."], "relay": { }, "hermesJobs": ["..."] },
"restart": { "ok": true },
"health": { "ok": true, "checks": [ { "name": "dsh-web http :3080", "ok": true, "detail": "200" } ] },
"recovery": { "resumed": ["..."], "report": "..." }
}
Any executor that reads/writes these two files can drive the reset — Hermes, a custom script, a cloud function. The protocol is the contract.
dsh plugin --profile <profile> add github:<owner>/dsh-reset-handoff
Optional executor trigger: configure triggerCommand so reset_handoff also wakes the external agent (default: none — the executor may poll request.json instead). See cordis.patch.yml for the config shape.
A reference executor is included under hermes/reset_agent.py (pure Python, no deps). It is meant to live inside a Hermes profile (reset-agent) and be triggered by hermes cron run <job>:
python3 reset_agent.py # run the five-step flow
python3 reset_agent.py --dry-run # print the flow, don't restart
launchctl kickstart -k com.dsh.web, or equivalent for your OS/init).MIT