87970a8c93
Container lifecycle from inside an agent goes away: an agent no longer starts, stops, restarts or rebuilds a container in its subtree, and no longer reads another container's journal. Those are operator actions — the dashboard and hivectl keep their own paths to the same job-queue and hive-priv plumbing, which is why none of that machinery is removed here, only the five MCP verbs and what they alone reached. What went with them: the `Request` variants and `Response::Logs` on the agent socket, the five tool definitions and their arg structs, the four lifecycle handlers plus `handle_get_logs`, and `require_descendant` — the topology guard those five were the only remaining callers of. `ToolGroup::Diagnostics` goes too: `get_logs` was its only tool, so it would otherwise be a grantable group that grants nothing. `lifecycle` stays, now carrying `list_containers` alone. An agent that gets a `needs_update` or `container_crash` helper event has no remedy of its own left, so the system prompt and the docs now send it to the operator instead of to a tool that no longer exists. Refs #4480
4.1 KiB
Scheduling and diagnostics tools
scheduling tool group
Scheduled prompts fan a message body out to one or more agent inboxes at a future time, optionally recurring.
Creating one goes through the operator approval queue, even when it
targets only yourself — use remind for an unapproved self-wake. The
other four verbs need no approval: holding the scheduling tool group
is the whole gate.
Authorization is one rule for all four verbs: you reach schedules you own
and any owned by an agent in your topology subtree. list_schedules
applies it too, so the snapshot only ever shows schedules you could also
cancel.
request_schedule_prompt(targets, body, first_fire_at_unix, interval_seconds?, description?)
Queue an operator-approval for a scheduled prompt. On approve,
hive-c0re fans body out to each agent in targets at
first_fire_at_unix (Unix timestamp). Recurring when interval_seconds
is set, one-shot otherwise.
Catch-up clamp: if hive-c0re is down across multiple intervals, only
ONE delayed fire happens on resume (per recurring schedule). The
skipped-cycle count surfaces in the per-target last_result for
audit.
edit_schedule(id, body?, description?, interval_seconds?, next_fire_at_unix?, targets_add?, targets_remove?)
Partial-update a schedule. Pass only the fields to change; absent
fields are left alone. targets_add / targets_remove mutate the
recipient list in the same transaction — re-adding a previously
cancelled target drops its tombstone and starts fresh.
interval_seconds accepts positive values only via this tool (omit
to keep the existing cadence; pass a new positive value to change
it). Toggling recurring → one-shot (clearing the interval) is
operator-only via the dashboard PATCH endpoint. Refuses cancelled
rows (terminal state).
cancel_schedule(id, targets?)
Cancel a schedule. Omit targets / pass empty to cancel the whole
schedule; pass a list to cancel just those recipients (the schedule
autocancels when every target is removed).
fire_schedule_now(id)
Fire a scheduled prompt out of band immediately. Recurring schedules keep their cadence — the manual fire is additive. The manual fire consumes one-shot schedules and cancels them afterwards.
list_schedules()
Snapshot the schedules you're authorized to see (active, and cancelled
but not yet reaped) — same read scope as the rest of this group: your
own, plus any owned by a sub-agent in your subtree (everything, for
the operator). Returns id, owner, body, per-target last_fired_at
and last_result, next_fire_at_unix, interval_seconds. Use to
look up an id before cancelling, or to audit upcoming wake-ups in
your subtree.
read_host_journal capability
Capability-gated (not a tool group) — the operator enables it in the
P3RM1SS10NS C4P4B1L1T13S section. Unlike tool groups this isn't
configurable from agent.nix.
get_host_journal(unit?, container?, lines?, priority?, grep?, since?, until?)
Fetch recent lines from the host journal (requires
read_host_journal capability). Useful when you need visibility
outside your own container — infrastructure services, hive-c0re
lifecycle events, or another container's boot log.
unit— filter to a systemd unit (for examplehive-c0re.service).container— nspawn machine name verbatim. Agent containers use theh-<name>prefix (for exampleh-iris); infrastructure containers use their full name (for examplehive-ci,hive-forge,hive-matrix). Omit for the host journal. The gateway has no machine — its nginx runs on the host, so read it withunit: nginx.serviceand nocontainer.lines— how many lines to return (default 30, max 100).priority— minimum syslog level (emerg…debug).grep— regex matched against log message fields (journalctl --grep).since/until— time bounds (for example-1h,2024-01-01 12:00:00).
See also
remind(no-approval self-wake path) — documented indocs/turn-loop/.docs/agent-lifecycle/approvals.md— approval flow forrequest_schedule_prompt.