Message reads read-receipt avatars from useReadPositions(), but the only provider is inside RoomTimeline. ThreadPanel/ThreadTimeline are rendered as siblings of RoomView in Room.tsx, so every message in a thread falls back to the context default (new Map()). Consequences: read receipts never render in a thread, and because the DeliveryStatus branch is gated on readReceiptUsers.length === 0, your own thread messages permanently display the "Sent" tick instead of graduating to read avatars. ThreadTimeline even threads hideReadReceipts={hideActivity} down to Message, showing the feature was intended to work there.
How to trigger
Send a message in a thread; have another user read it. No read avatar ever appears in the thread panel.
Suggested fix
Wrap ThreadTimeline (or ThreadPanel) in a ReadPositionsContext.Provider fed by useRoomReadPositions(room), or hoist the provider to Room.
Filed from the September 2026 client audit (branch lotus @ 4bea4895).
**Severity:** medium · **Type:** bug · **Confidence:** high
**Location:** `src/app/features/room/RoomTimeline.tsx:2131` (`ReadPositionsContext.Provider`), `src/app/features/room/message/Message.tsx:875-879`, `src/app/features/room/Room.tsx:196-207`
### Problem
`Message` reads read-receipt avatars from `useReadPositions()`, but the only provider is inside `RoomTimeline`. `ThreadPanel`/`ThreadTimeline` are rendered as **siblings** of `RoomView` in `Room.tsx`, so every message in a thread falls back to the context default (`new Map()`). Consequences: read receipts never render in a thread, and because the `DeliveryStatus` branch is gated on `readReceiptUsers.length === 0`, your own thread messages permanently display the "Sent" tick instead of graduating to read avatars. `ThreadTimeline` even threads `hideReadReceipts={hideActivity}` down to `Message`, showing the feature was intended to work there.
### How to trigger
Send a message in a thread; have another user read it. No read avatar ever appears in the thread panel.
### Suggested fix
Wrap `ThreadTimeline` (or `ThreadPanel`) in a `ReadPositionsContext.Provider` fed by `useRoomReadPositions(room)`, or hoist the provider to `Room`.
---
_Filed from the September 2026 client audit (branch `lotus` @ 4bea4895)._
jared
added this to the Audit 2026-09 · Medium & Low milestone 2026-09-12 01:51:07 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Severity: medium · Type: bug · Confidence: high
Location:
src/app/features/room/RoomTimeline.tsx:2131(ReadPositionsContext.Provider),src/app/features/room/message/Message.tsx:875-879,src/app/features/room/Room.tsx:196-207Problem
Messagereads read-receipt avatars fromuseReadPositions(), but the only provider is insideRoomTimeline.ThreadPanel/ThreadTimelineare rendered as siblings ofRoomViewinRoom.tsx, so every message in a thread falls back to the context default (new Map()). Consequences: read receipts never render in a thread, and because theDeliveryStatusbranch is gated onreadReceiptUsers.length === 0, your own thread messages permanently display the "Sent" tick instead of graduating to read avatars.ThreadTimelineeven threadshideReadReceipts={hideActivity}down toMessage, showing the feature was intended to work there.How to trigger
Send a message in a thread; have another user read it. No read avatar ever appears in the thread panel.
Suggested fix
Wrap
ThreadTimeline(orThreadPanel) in aReadPositionsContext.Providerfed byuseRoomReadPositions(room), or hoist the provider toRoom.Filed from the September 2026 client audit (branch
lotus@4bea4895).