Raised on LibreChat-AI#16246: LibreChat-AI#16246 (comment)
The Chats section now lists only chats outside any project (projectId: 'unassigned'). useUnseenConversations builds the tab badge and the reply alerts from the cached conversation lists plus the pinned list, so on a fresh or restored session a reply in an unpinned chat inside a collapsed project is missing from the aggregate until the project is expanded or the first focused refresh runs the unfiltered reply-discovery fetch (interface.replyNotifications.focusedRefreshMs, 5 minutes by default). The away poll is unaffected.
Tried in LibreChat-AI#16246: seeding the reply-discovery page once when useReplyWatcher mounts. It closes the gap but changes the unseen-replies read ordering at load (17 of 70 useReplyWatcher.spec.tsx cases fail, including the successor-reply and completion-stamp cases), so it needs a decision on the reply subsystem rather than a patch from the chat list.
Options: seed the discovery page at load and rework the ordering tests; or expose per-project unseen counts on the projects list so a collapsed project carries its own dot and the aggregate reads it.
Raised on LibreChat-AI#16246: LibreChat-AI#16246 (comment)
The Chats section now lists only chats outside any project (
projectId: 'unassigned').useUnseenConversationsbuilds the tab badge and the reply alerts from the cached conversation lists plus the pinned list, so on a fresh or restored session a reply in an unpinned chat inside a collapsed project is missing from the aggregate until the project is expanded or the first focused refresh runs the unfiltered reply-discovery fetch (interface.replyNotifications.focusedRefreshMs, 5 minutes by default). The away poll is unaffected.Tried in LibreChat-AI#16246: seeding the reply-discovery page once when
useReplyWatchermounts. It closes the gap but changes the unseen-replies read ordering at load (17 of 70useReplyWatcher.spec.tsxcases fail, including the successor-reply and completion-stamp cases), so it needs a decision on the reply subsystem rather than a patch from the chat list.Options: seed the discovery page at load and rework the ordering tests; or expose per-project unseen counts on the projects list so a collapsed project carries its own dot and the aggregate reads it.