@goodandready/dsh-smart-restart
已验证 DeepSeek Harness 的重启：无需特权即可重启，检查 Harness 是否确实恢复运行，将结果报告给发起请求的会话，并交接剩余待办事项。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add @goodandready/dsh-smart-restart@0.1.9Smart Restart 以 @goodandready/dsh-smart-restart 发布，当前版本为 0.1.9。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
npm · MIT · DSH plugin
|
⭐ If you like this plugin, please star it on GitHub — it shows that the plugin is useful and supports continued development.
🐛 If you find a bug or want to request a feature, open a GitHub issue in any language. |
A restart that is verified, not announced. The agent restarts DeepSeek Harness, and when the process comes back this plugin checks that everything is really up, reports the verdict into the session that asked for the restart, and hands back what that session was doing.
A restart is the only operation that destroys the thing performing it. The existing answer to
that is a notice: "the service restarted at …". It leaves the two questions that matter open —
is the harness actually healthy now, and what was I in the middle of — and on a system unit
it needs either root or a polkit rule, because it calls systemctl restart from a detached shell
whose errors go to /dev/null: a refused restart looks exactly like a successful one.
This plugin closes both gaps and needs no privileges.
graph LR
A[DSH web profile] --> B[Host plugin]
B --> C[Restart intent and guard]
C --> D[Service manager restarts DSH]
D --> E[Next-process health checks]
E --> F[Report to requesting session]
A --> G[Client module loader]
G --> H[Settings card]
H --> B
The browser half is registered as a lazy CommonJS factory with the DSH client loader. The factory returns its apply and inject exports; the host half owns restart tools, health checks, and the report.
Restart=always). Nothing is called, nothing is spawned detached, no sudo, no
polkit. systemctl restart <unit> remains as an alternative mode for deployments that already
grant the right.ActiveState/MainPID/NRestarts, whether the listening port is
owned by a process inside the unit's cgroup, and the versions of the plugin and the core. The
outcome is a verdict — ok, or degraded with the list of checks that failed.dsh-russian-lang).dsh plugin --profile <profile> add @goodandready/dsh-smart-restart
Requires a systemd-managed harness (dsh-web.service or any unit with Restart=always) for the
default mode; the unit is detected from the process cgroup, and can be set explicitly.
| Setting | Type | Default | Meaning |
|---|---|---|---|
enabled | boolean | true | Whether the plugin registers its tools and checks a boot at all. |
restartMode | string | kill | kill ends the process and lets systemd restart it (no privileges); systemctl runs systemctl restart <unit>. |
unit | string | empty (auto) | The systemd unit to inspect and restart. Empty detects it from /proc/self/cgroup. |
delayMs | number | 3000 | How long to wait before the process ends, so the tool's answer reaches the caller. |
target | string | requester | Where the report goes: requester (the session that asked), primary, or a session id. |
stateDir | string | .restart-guard | State directory under $DSH_HOME: boot marker, intent, last report, and history. |
maxRestarts | number | 3 | Refuse a restart after this many inside the window. |
windowMs | number | 600000 | The loop-guard window in milliseconds. |
timeoutMs | number | 5000 | Timeout for each individual health probe. |
expectTools | string[] | [] | Tool names that must be registered after a boot, otherwise the verdict is degraded. |
toolEnabled | boolean | true | Register dsh_restart / dsh_restart_status. |
dsh_restart — parameters reason, resume, confirm, delayMs. Records the intent, checks
the loop guard, schedules the restart and returns a receipt. The session that called it is the
one that receives the verdict afterwards.dsh_restart_status — last boot and downtime, the last health report, the pending intent, and
how many restarts happened inside the window.smart-restart: the harness restarted and the boot check passed.
- boot: <boot timestamp> (was down 6.2s, pid 12345)
- ok services: webServer, tools, agents, settings
- ok tools: 61 registered
- ok unit: active/running, NRestarts 0
- ok port: 127.0.0.1:<port> owned by pid in system.slice/dsh-web.service
- ok versions: plugin 0.1.0, core <core-version>
verdict: ok
resume: continue the recorded task and report the result
Restart=always); on a
bare process started by hand there is nothing to bring it back, and the plugin says so instead
of pretending.npm test
MIT © GooDAnDReaDY