11097ed336
swarm-logs covers every host-tier unit this tool could reach, so the second, capability-gated path into host journald earns nothing and is removed outright rather than disabled behind a flag. Removed end to end: the MCP tool definition + handler, the GetHostJournal/HostJournal wire variants, hive-c0re's dispatch_host_journal handler, the ReadHostJournal capability, and the harness-side capability->--allowedTools gate. get_host_journal was the only capability that mapped to an MCP tool, so allowed_capability_tools could only ever return an empty vec; it goes too rather than linger as a function that provably does nothing. capabilities::has_cap/caps_for stay: #4624 gave ManageRootAgent's bind-mount enforcement (hive-c0re/src/lifecycle/host_config.rs) a second caller of has_cap, so they're no longer callerless once this lands on top of it. hive-sh4re's journal module (JournalPriority) had no consumer outside this tool and is deleted. An existing capabilities.json still naming read_host_journal does not error: capabilities::prune_unknown drops unrecognised names with a warn!, and an agent left with no capabilities has its entry removed. No migration step is needed. Untouched: hive-c0re/src/dashboard/journal.rs's read_host_journal_response, which matches the name but is the private helper behind the operator-only GET /api/journal-host dashboard route and carries no capability check.
2.9 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 every schedule in
the hive, whoever owns it. list_schedules shows the same set, 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 stay untouched. 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 once every target is gone).
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 every schedule in the hive (active, and cancelled but not yet
reaped) — same read scope as the rest of this group. 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 across the hive.
See also
remind(no-approval self-wake path) — documented indocs/turn-loop/.docs/agent-lifecycle/approvals.md— approval flow forrequest_schedule_prompt.