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

remove operator as target for scheduled prompts

Browse source
This commit is contained in:
damocles 2026-09-11 22:36:40 +02:00 • committed by mara
commit b4dc09ff93
7 changed files with 130 additions and 86 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/agent-lifecycle/approvals.md
View file

@ -216,15 +216,15 @@ target drives `push_todo`'s own upsert-by-key dedup: a re-fire of the
*same schedule* against a target that hasn't reviewed the last one
collapses into that one todo instead of stacking up.
**`operator` is the one exception** — it's a valid schedule target but
has no in-container todo inbox, so it keeps the original broker
`Message` path (the dashboard mirrors `to == operator` into its own
pane, same as before).
`operator` is not a valid schedule target — she isn't a container with
a todo inbox to push a wake into, and this mechanism is for fanning a
prompt out to agents, not scheduling something at her. Rejected at
submit/edit time (`ScheduledPrompts::submit`/`update`).
### Missing-target failure
When a target name doesn't resolve to a known agent (container
destroyed, operator typo, etc.) the worker:
destroyed, typo, etc.) the worker:
1. Records `last_result = "no such agent: <name>"` on the
per-target row.