Repository navigation
[Feature] Extend Bot Social for human↔bot and bot↔bot coordination #872
Description
Bot Social (@flybot/social) already provides identity, approvals, friend messaging, and rooms. Build on it:
Human
- Merge confirmation requests that reuse the existing approval flow.
- Proactive progress notifications: PR opened, tests failed, needs a human.
- Fix delivery of messages that arrive while the bot is working, so it reads them at its next step (Follow-up message typed while a Bot is working is postponed instead of being delivered at its next step #707, A burst of messages opens one turn per message; there is no receive buffer #642).
- External channels such as Slack or WeChat, to be decided.
bot (agent-CI-Infra/bot)
bot has no Social support, so this goes through GitHub:
- Receive task assignments via label, comment, or webhook.
- Use bot's review comments as an input to merge-gate.
- Report FlyBot's status back to bot's dashboard.
Related: #871, #644 (all bots share one GitHub identity), #853, #51, #57.
Activity
Birfy commentedon Oct 23, 2026
Triaged as a bundle, not a spec —
enhancement|area:social|area:automation|needs-human. Five of its bullets are already tracked elsewhere or need a decision, so it cannot beagent-readyas written. Split proposal:Verdict: PASSplus the queue gates, and mechanical release PRs run under a standing approval — so what exactly would a second confirmation confirm? Decide that and it becomes one issue.agent-CI-Infra/botreceiving assignments and reporting status over GitHubSo #872 stays open as the index, and the two "New" rows above are the only ones I can turn into
agent-readyspecs — after the merge-confirmation question and the notification triggers are answered. #51/hold_reasonand #853/#866 are only referenced by this issue; they are not part of it.