You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Show a group's open question card in the sidebar and Agent inbox #552
Since #551, a question card a Bot asks about work handed out from a group sits in that group's composer dock (state.questions[<room id>]). The asking Bot's sidebar row no longer turns to the alert state (sidebar.jsBotRow reads roster.questions[part], which is now empty), and the group's RoomRow does not read roster.questions[room.id] at all. The only signal is the group's own unread state, which comes from the reply the admin posts.
Expected: a group with an open question card shows it in the sidebar the way a Bot row does for its own card (alert or waiting state), and the Agent inbox (inbox.js) lists it next to approvals (" asks in ").
Scope: client only (sidebar.js RoomRow, possibly inbox.js); client.js rebuild; tests in core/test/.
Triage (Birfy, 2026-10-20 22:06 Asia/Shanghai). No design conflict: it only surfaces an existing question card, and answering still happens on the card's own buttons. Proposed details: the group's sidebar row uses the same alert/waiting state a Bot row uses for its own card; the Agent inbox lists ' asks in ' next to approvals and opens that group. Client only (sidebar.js RoomRow, inbox.js, client.js rebuild, tests). Best done after #551 lands. Waiting for the owner's go-ahead (needs-human).
Owner decision (2026-10-20 22:07 Asia/Shanghai): option a — group row shows the same attention state as a Bot with an open question card; Agent inbox lists " asked in " and opens that group. Frontend only; start after #551 merges.
Claimed by the maintenance round. Branch: fix/552-group-question-card (client only: sidebar.jsRoomRow reads roster.questions[room.id], inbox.jsinboxModel adds the group card as Needs your answer, plus a rebuilt client.js, tests and the subsystem doc). One PR follows with Fixes #552.
Activity
Birfy commentedon Oct 20, 2026
Triage (Birfy, 2026-10-20 22:06 Asia/Shanghai). No design conflict: it only surfaces an existing question card, and answering still happens on the card's own buttons. Proposed details: the group's sidebar row uses the same alert/waiting state a Bot row uses for its own card; the Agent inbox lists ' asks in ' next to approvals and opens that group. Client only (
sidebar.jsRoomRow,inbox.js,client.jsrebuild, tests). Best done after #551 lands. Waiting for the owner's go-ahead (needs-human).Birfy commentedon Oct 20, 2026
Owner decision (2026-10-20 22:07 Asia/Shanghai): option a — group row shows the same attention state as a Bot with an open question card; Agent inbox lists " asked in " and opens that group. Frontend only; start after #551 merges.
Birfy commentedon Oct 20, 2026
Claimed by the maintenance round. Branch:
fix/552-group-question-card(client only:sidebar.jsRoomRowreadsroster.questions[room.id],inbox.jsinboxModeladds the group card as Needs your answer, plus a rebuiltclient.js, tests and the subsystem doc). One PR follows withFixes #552.Show a group's open question card in the sidebar and the Agent inbox (T…