feat(chat): member profile hovercard — bio/status visible in channel (+ docs fix)#97
Merged
Merged
Conversation
#2a — a channel member's bio/status was in the DB but never surfaced to people. Now clicking a member's avatar/name (in a message or the Members list) opens a profile card with avatar, name, @handle, status (emoji+text), bio, and role. - server: list_channel_members now returns bio (COALESCE(users.bio, bot_accounts.description)) + status_text/status_emoji, mirroring the bot-facing resource handler (server/src/resource/members.rs). - frontend: new ProfileHovercard (context provider + body-portaled card, outside-click/Esc close, viewport-clamped, flips above near the bottom). MemberItem gains bio/status; ChannelView holds the member map and provides it; MessageItem avatar/name and MembersPopover rows open the card. #2b — bots can ALREADY read member bios via the list_members / channel.members resource (returns `info` = the same bio). Only the docs were stale: fixed AGENT_BRIDGE_RESOURCE.md to document `info`/status_* and drop the never-returned avatar_url/role. Verified: cargo build + frontend typecheck/build; redeployed the gateway and confirmed end-to-end via headless Chrome — set a bio/status on a member, then the card renders it from both the member list and a message avatar. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Covers optimization #2 (a member's bio in a channel: visible to people, readable by bots).
#2a — bio/status now visible to people
A member's bio/status lived in the DB but was never surfaced. Now clicking a member's avatar or name (in a message, or the Members list) opens a profile card: avatar · name · @handle · status (emoji+text) · bio · role.
channels.rs:list_channel_membersnow returnsbio(COALESCE(users.bio, bot_accounts.description)) +status_text/status_emoji, mirroring the bot-facingserver/src/resource/members.rs.ProfileHovercard(context provider + body-portaled card; outside-click/Esc close; viewport-clamped; flips above near the bottom).MemberItemgainsbio/status_*;ChannelViewholds the member map;MessageItemavatar/name andMembersPopoverrows open the card.#2b — bots could ALREADY read member bios
The
list_members/channel.membersresource already returns the bio asinfo. This was only a stale doc:AGENT_BRIDGE_RESOURCE.mdnow documentsinfo/status_*and drops the never-returnedavatar_url/role.Verification
cargo build+ frontendtsc/vite buildpass.PATCH /users/me, confirmed the members API returns them, and the card renders🛠️ heads-down on infra+ bio from both the member list and a message avatar.Not in this PR
Avatar image upload (optimization #1) — follow-up PR
feat/avatar-upload.🤖 Generated with Claude Code