vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

docs: add fire_schedule_now tool and /api/schedules/{id}/fire-now endpoint (follow-up to #472)

Browse source
This commit is contained in:
lexis 2026-05-26 16:02:22 +02:00 • committed by Mara
commit 4589a61853
2 changed files with 10 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/turn-loop.md
View file

@ -347,6 +347,11 @@ meta's.
to cancel just those recipients (auto-cancels when every target to cancel just those recipients (auto-cancels when every target
is removed). Authorization: manager can cancel schedules it owns is removed). Authorization: manager can cancel schedules it owns
or any owned by a sub-agent in its topology subtree. or any owned by a sub-agent in its topology subtree.
- `fire_schedule_now(id)` — fire a scheduled prompt out of band.
Runs the per-target fan-out once immediately. Recurring schedules
keep their cadence (the manual fire is additive); one-shot
schedules are consumed by the fire and cancelled afterwards. Same
authorization rules as `cancel_schedule`.
- `list_schedules()` — snapshot every schedule (active + - `list_schedules()` — snapshot every schedule (active +
cancelled-but-not-reaped): id, owner, body, per-target cancelled-but-not-reaped): id, owner, body, per-target
`last_fired_at` + `last_result`, `next_fire_at_unix`, `last_fired_at` + `last_result`, `next_fire_at_unix`,

5
docs/web-ui.md
View file

@ -500,6 +500,11 @@ not ours.
is sent as `null`). Targets stay immutable — cancel + new is sent as `null`). Targets stay immutable — cancel + new
schedule is the retarget workaround. Refuses cancelled rows; schedule is the retarget workaround. Refuses cancelled rows;
returns the updated `WireSchedule` on success. returns the updated `WireSchedule` on success.
- `POST /api/schedules/{id}/fire-now` — operator-initiated manual
fire (#467). Runs the per-target fan-out once immediately.
Recurring schedules keep their cadence (manual fire is additive);
one-shot schedules are consumed (cancelled afterwards). Manager
surface: `fire_schedule_now(id)` MCP tool.
- `POST /api/schedules/{id}/cancel` — cancel a schedule. Body - `POST /api/schedules/{id}/cancel` — cancel a schedule. Body
`{ targets?: ["name", …] }` cancels just those recipients; `{ targets?: ["name", …] }` cancels just those recipients;
absent or empty body cancels the whole schedule. absent or empty body cancels the whole schedule.