Repository navigation
Conversation
The sidebar avatar now shows a green dot while the bot has a run in progress, using the isRunning state the live conversation list already carries. The orange unread dot is unchanged; green takes precedence. iOS is not touched.
The dot only watched the bot's main conversation, so a bot answering another bot in a private side conversation, or waiting on a message it sent, showed as idle. Conversation summaries now carry isWorking: any foreground task in any of the bot's conversations, or a pending bot-to-bot delivery. Sleeping routines, computers and background compaction do not count.
|
Nice one, the per-bot flag and counting bot-to-bot deliveries work well. One case reads wrong: when a bot is waiting on the owner (a tool approval or a question), its foreground task stays live, so the dot turns green and says "Working" even though the bot is blocked on the owner. Could the dot leave out tasks that are waiting on the owner, or show them as a separate state? That's the moment the owner most needs to notice the bot. |
Good catch, thanks for pointing this out! I agree that a bot waiting for owner input shouldn't be shown as "Working", since it's effectively blocked. I'll look into how we can distinguish these states reliably and update the indicator accordingly. |
A bot blocked on a tool approval or a question kept its foreground task live, so the dot said Working. The sidebar now checks the pending approvals and questions the client already streams and shows a red "Waiting for you" dot, which takes precedence over working and unread.
|
Hey Vasco, pushed a fix on top (
Check and lint pass. I didn't look at it in the app, so give it a quick spin if you can. |
With 32px rows the orb fills its circle, so the dots' old spot six pixels in from the corner landed on the orb's face.
What
The sidebar avatar (web and desktop) now shows a status dot:
Red takes precedence over green, and green over orange; red and green also show on the open chat. It does not animate, following DESIGN.md's reduced-motion guidance. Screen readers announce "Waiting for you" or "Working" (new
rooms_waitingandrooms_workingkeys). The waiting state comes from the pending approvals and questions the client already streams, so it needs no server change.What counts as working
Conversation summaries carry a new per-bot
isWorkingflag, computed from the bot's live task graph:Sleeping routines, computers and background compaction do not count.
isRunning(main conversation only) is unchanged, since the chat view relies on it.Placement
Since #30, rows use a 32px avatar slot and the orb fills its circle, so the dots' old spot six pixels in from the corner landed on the orb's face. The dots now sit on the avatar's top-right rim, at 8px with a 2px ring in the sidebar colour. This branch merges main to pick up #30.
Names and previews in the screenshot are demo text.
Not included
iOS was not touched; the mobile home list is unchanged.
Checks
bun run checkandbun run lintpass (17/17, Fallow clean). Tested against a live daemon: a bot delegating to two other bots showed green on all three while they worked.