# 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?)`

<!-- vale write-good.Passive = NO -->

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.

<!-- vale write-good.Passive = YES -->

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?)`

<!-- vale write-good.Passive = NO -->

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).

<!-- vale write-good.Passive = YES -->

### `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 in
  [`docs/turn-loop/`](../turn-loop/README.md).
- [`docs/agent-lifecycle/approvals.md`](../agent-lifecycle/approvals.md) — approval flow for
  `request_schedule_prompt`.