fix(mothership): keep reconnect resync off locally streaming chats

The resync invalidated every chat detail, including one whose stream this client is rendering optimistically. Refetching there replaces the local transcript with a server copy that does not yet hold the in-flight message, which is exactly what status events avoid via shouldSkipDetailInvalidationForStreamEvent.

Filter the detail invalidation with the same isLocalOptimisticActiveStream check. Those chats reconcile when their own stream finishes.

Author: waleedlatif1

apps/sim/hooks/use-mothership-chat-events.test.ts

@@ -432,15 +432,41 @@ describe('resyncMothershipChatCaches', () => {
     vi.clearAllMocks()
   })
 
-  it('invalidates the workspace lists and every chat detail', () => {
+  function detailPredicate() {
+    resyncMothershipChatCaches(queryClient, 'ws-1')
+    const predicate = queryClient.invalidateQueries.mock.calls
+      .map(([arg]: [{ predicate?: (query: unknown) => boolean }]) => arg.predicate)
+      .find(Boolean)
+    if (!predicate) throw new Error('detail invalidation did not pass a predicate')
+    return (data: unknown) => predicate({ state: { data } })
+  }
+
+  it('invalidates the workspace lists and the chat details', () => {
     resyncMothershipChatCaches(queryClient, 'ws-1')
 
     expect(queryClient.invalidateQueries).toHaveBeenCalledTimes(2)
     expect(queryClient.invalidateQueries).toHaveBeenCalledWith({
       queryKey: mothershipChatKeys.workspaceLists('ws-1'),
     })
-    expect(queryClient.invalidateQueries).toHaveBeenCalledWith({
-      queryKey: mothershipChatKeys.details(),
-    })
+    expect(queryClient.invalidateQueries).toHaveBeenCalledWith(
+      expect.objectContaining({ queryKey: mothershipChatKeys.details() })
+    )
+  })
+
+  it('skips the detail of a chat whose stream this client is rendering locally', () => {
+    expect(
+      detailPredicate()({
+        messages: [{ id: 'new-stream' }, { id: 'live-assistant:new-stream' }],
+        activeStreamId: 'new-stream',
+      })
+    ).toBe(false)
+  })
+
+  it('invalidates details with no active stream, and streams not rendered locally', () => {
+    const predicate = detailPredicate()
+
+    expect(predicate(undefined)).toBe(true)
+    expect(predicate({ messages: [{ id: 'stream-1' }] })).toBe(true)
+    expect(predicate({ messages: [{ id: 'stream-1' }], activeStreamId: 'stream-1' })).toBe(true)
   })
 })

apps/sim/hooks/use-mothership-chat-events.ts

@@ -138,13 +138,22 @@ export function handleMothershipChatStatusEvent(
  * no connection was open — so any reconnect may have missed a create, rename,
  * delete, or completion. Invalidating the workspace lists and every chat detail
  * reconciles from the server; only queries that are currently mounted refetch.
+ *
+ * A chat whose stream this client is rendering locally is left alone, for the
+ * same reason status events skip it: refetching mid-stream would replace the
+ * optimistic transcript with a server copy that does not yet hold the in-flight
+ * message. That chat reconciles when its own stream finishes.
  */
 export function resyncMothershipChatCaches(
   queryClient: Pick<QueryClient, 'invalidateQueries'>,
   workspaceId: string
 ): void {
   queryClient.invalidateQueries({ queryKey: mothershipChatKeys.workspaceLists(workspaceId) })
-  queryClient.invalidateQueries({ queryKey: mothershipChatKeys.details() })
+  queryClient.invalidateQueries({
+    queryKey: mothershipChatKeys.details(),
+    predicate: (query) =>
+      !isLocalOptimisticActiveStream(query.state.data as MothershipChatHistory | undefined),
+  })
 }
 
 /**