Add a resume_on_boot policy for recovered sessions #167

Closed
opened 2026-09-03 23:05:34 +01:00 by naps62-yolo · 0 comments
Collaborator

Once sessions can be resumed, the daemon needs a stated policy for what happens on its own startup. Resuming six agents that run with --dangerously-skip-permissions unattended, seconds after a reboot, with nobody watching, is not a safe default.

Add [daemon].resume_on_boot:

  • "dormant" (default) — recovered-but-dead sessions are listed dormant and wait for the operator.
  • "auto" — the daemon resumes each one itself during recovery.
  • "never" — the sidecars are pruned instead; a reboot is a clean slate.

auto exists for hosts where the sessions are known to be safe to restart unattended, and the operator opts in per host. Log the chosen policy and the count it acted on at startup.

Once sessions can be resumed, the daemon needs a stated policy for what happens on its own startup. Resuming six agents that run with `--dangerously-skip-permissions` unattended, seconds after a reboot, with nobody watching, is not a safe default. Add `[daemon].resume_on_boot`: - `"dormant"` (default) — recovered-but-dead sessions are listed dormant and wait for the operator. - `"auto"` — the daemon resumes each one itself during recovery. - `"never"` — the sidecars are pruned instead; a reboot is a clean slate. `auto` exists for hosts where the sessions are known to be safe to restart unattended, and the operator opts in per host. Log the chosen policy and the count it acted on at startup.
naps62-yolo added this to the Reboot resilience milestone 2026-09-03 23:05:34 +01:00
naps62-yolo added the area/daemondifficulty/mediumarea/configtype/feat labels 2026-09-03 23:05:34 +01:00
naps62-yolo added a new dependency 2026-09-03 23:06:14 +01:00
naps62-yolo added a new dependency 2026-09-03 23:06:21 +01:00
This repo is archived. You cannot comment on issues.
1 Participants
Due Date
No due date set.
Reference: naps62/maestro#167