feat(web): room mail carries a participant roster so agents can hand off (CL-8530) - #917
Merged
Merged
Conversation
The hub only delivers mail to run addresses, which only the client knows (a room's Participants panel already reads them off the deployment/run listing). Append them as a trailing Participants block on every room send, and strip that block back off before showing a person their own sent message.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Participants:block (name + run address for every live agent), using the same data the room's Participants panel already reads from the query cache — no new hub call.appendRoster/stripRosterpair inapps/web/src/chat/room-roster.ts.Test plan
bun run check