Repository navigation
list_bots marks a Bot whose send waits for approval #587
Description
What
A Bot whose outbound message is held for the owner's approval looks idle to a coordinator: list_bots shows no sign that the Bot is blocked on a decision.
Expected behavior
list_botsmarks such a Bot with a count (for exampleChief (Boss, 1 to approve, Main Bot, you)), so a Main Bot can see who is waiting on the owner.- The tag is a count only: never the held message text.
Change scope
core/src/host/tools.js (the list_bots tag), a case in core/test/flybot.test.js, docs/subsystems/{core-host,plugin-runtime}.md. Core only; no new state.
Why
Coordination (#52 follow-up): a blocked-on-approval Bot is no longer invisible to the team.
Activity
Birfy commentedon Oct 21, 2026
Triaged by the maintenance round (2026-10-21):
needs-human, parked.The implementation attempt is PR #588 (closed by the routine): a coordinator-facing tag on
list_bots, useful but not a fix for a reproducible defect and not something the routines need — under the 2026-10-21 admission line it does not get a PR or a slot in the approval list. It is also a corelist_botsshape, so it should wait for the owner's word rather than ride in with routine work.Changed behavior to decide on:
list_botswould show a count (never the held text) for a Bot whose send waits for approval. The tag is small; the question is whether the owner wants that count in the roster view at all. Nothing here is obsolete — the branch and the review are kept.fix(core): list_bots marks a Bot whose send waits on the owner (#646)