dsh-goal-restart
在 dsh 服务启动或重新启动时自动重新启用活动目标，使 goal-round driver 无需人工干预即可恢复回合。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-goal-restart@0.1.0Goal Restart 以 dsh-goal-restart 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
English | 中文
Re-arm persisted same-session goals automatically when the dsh service (re)starts, so the goal-round driver resumes rounds without human intervention.
Why? When an agent is doing long-running work — like developing its own plugins — and the service it lives in gets restarted (crash, launchd respawn, a deliberate bounce), the in-flight goal used to stay stuck until somebody ran
/goal resume. This plugin removes that step.
A dsh goal's durable state (objective, phase, revision, roundsStarted)
lives in the session log and survives restarts. Its activation ("armed")
is deliberately process-local: it is never persisted, and every
agent/session-start edge disarms it. So after the dsh service restarts, an
in-flight goal is replayed as active but stays stopped until someone issues
an explicit resume.
On agent/session-start where payload.source === 'resume' (the session was
just loaded from persistence), it calls ctx.goals.resume(agent, ref) for a
durable-active goal that still has round budget. The stock
goal-round-driver (mounted by dsh-base) then reserves and queues the next
round exactly as it would after a normal human resume — but nobody had to
click anything.
| Situation | Action |
|---|---|
Session rehydrated after a service restart, goal active, budget left | re-arm (ctx.goals.resume) |
Session started fresh (source: 'startup') | skip (no goal) |
| Forked session (inherited goal) | skip (in-process lineage) |
Subagent session (origin: subagent) | skip (in-process lineage) |
Goal paused / blocked / complete | skip (durable phase wins) |
Goal active but already armed | skip (idempotent) |
Goal at roundsStarted >= maxGoalRounds | skip (no budget — raise the cap, then resume) |
dsh plugin --profile <profile> add dsh-goal-restart
Then restart the dsh service so the new bundle is loaded.
In the profile's cordis.patch.yml:
- id: goal-restart
disabled: true
resume mutation (revision +1) into the
session log — the domain's documented reactivation edge, and the same
write a human /goal resume performs.npm test) and a smoke
script (npm run smoke) that need no network and no live process.