release: member profile visibility + avatar image upload#99
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>
feat(chat): member profile hovercard — bio/status visible in channel (+ docs fix)
Add avatar image upload backed by object storage:
- POST /api/v1/users/me/avatar (self) and POST /api/v1/bots/:bot_id/avatar
(owner/admin) accept raw image bytes, store to avatars/{kind}/{id}/{uuid}.{ext},
and write the serving URL into the existing avatar_url column.
- Public GET /api/v1/{users,bots}/:id/avatar/:file serves the bytes with an
inline content-disposition and 1-day cache (an <img src> can't send a Bearer
token, and the path is validated to stay inside the avatars/ prefix).
- Only raster images (png/jpeg/webp/gif) up to 5 MiB; SVG is rejected because
file_response forces it to download.
Frontend: AvatarUpload component (hover camera + file picker + optimistic
preview) wired into the profile editor and the bot status editor.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
feat(avatars): image upload for users and bots
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.
Promote
develop→main. Two user-profile features, both already merged to develop and CI-green.#97 — Member profile visibility
ProfileHovercard(bio, status emoji/text).AGENT_BRIDGE_RESOURCE.mddoc was corrected).list_channel_membersnow returnsbio/status_text/status_emoji(COALESCE user → bot fallback).#98 — Avatar image upload (users + bots)
POST /api/v1/users/me/avatar(self) andPOST /api/v1/bots/:bot_id/avatar(owner/admin) accept raw image bytes → object storage →avatar_url.GET /api/v1/{users,bots}/:id/avatar/:fileserves bytesinlinewith a 1-day cache; path validated to stay inside theavatars/prefix.AvatarUploadUI (hover camera → picker → optimistic preview) in the profile editor and bot status editor.Verification
Both merged into develop via green CI (Frontend Build, Gateway Check, Gateway Integration). Avatar flow additionally verified end-to-end against the local kind stack (upload → byte-perfect serve → persisted → renders after fresh reload; validation returns 400/401 as expected).
🤖 Generated with Claude Code