fix(sdk,ai-chat): auto chat:{chatId} tag on server-mediated start; atomic persist in reference onTurnComplete

- chat.createStartSessionAction now adds 'chat:{chatId}' as the first tag on the triggered run, matching the browser-mediated transport.doStart path. Customer-provided tags merge after, capped at 5. Without this, runs created via server actions were untagged, breaking the dashboard chat-id filter.

- references/ai-chat onTurnComplete persists Chat.messages and ChatSession.lastEventId in a single prisma.$transaction. Two parallel reads on the next page load (Promise.all([getChatMessages, getSessionForChat])) can otherwise observe messages post-write but lastEventId pre-write. The transport then resumes from the stale cursor and replays this turn's chunks on top of the already-persisted assistant message, duplicating the render. Applies to both the main chat.agent and the hydrated variant.

Author: ericallam

packages/trigger-sdk/src/v3/ai.ts

@@ -6942,6 +6942,12 @@ function createChatStartSessionAction(
     // `metadata` is the customer's transport-level `clientData`,
     // threaded through so the agent's `clientDataSchema` validates on
     // the very first turn (the typical schema requires `userId` etc.).
+    // Auto-tag every chat.agent run with `chat:{chatId}` so the dashboard /
+    // run-list filter by chat works without the customer having to wire it
+    // up. Mirrors the browser-mediated `TriggerChatTransport.doStart` path.
+    const userTags = params.triggerConfig?.tags ?? options?.triggerConfig?.tags ?? [];
+    const tags = [`chat:${params.chatId}`, ...userTags].slice(0, 5);
+
     const triggerConfig: SessionTriggerConfig = {
       basePayload: {
         messages: [],
@@ -6956,12 +6962,7 @@ function createChatStartSessionAction(
       ...(options?.triggerConfig?.queue || params.triggerConfig?.queue
         ? { queue: params.triggerConfig?.queue ?? options?.triggerConfig?.queue }
         : {}),
-      ...(options?.triggerConfig?.tags || params.triggerConfig?.tags
-        ? {
-            tags:
-              params.triggerConfig?.tags ?? options?.triggerConfig?.tags ?? [],
-          }
-        : {}),
+      tags,
       ...(options?.triggerConfig?.maxAttempts !== undefined ||
       params.triggerConfig?.maxAttempts !== undefined
         ? {

references/ai-chat/src/trigger/chat.ts

@@ -411,15 +411,21 @@ export const aiChat = chat
         toolPartsCount: toolParts.length,
         toolParts: toolParts.map((p: any) => ({ type: p.type, state: p.state, toolCallId: p.toolCallId })),
       });
-      await prisma.chat.update({
-        where: { id: chatId },
-        data: { messages: uiMessages as unknown as ChatMessagesForWrite },
-      });
-      await prisma.chatSession.upsert({
-        where: { id: chatId },
-        create: { id: chatId, publicAccessToken: chatAccessToken, lastEventId },
-        update: { publicAccessToken: chatAccessToken, lastEventId },
-      });
+      // Atomic so the page-load `Promise.all([getChatMessages, getSessionForChat])`
+      // can't observe a state where messages are post-write but lastEventId is
+      // still pre-write — that race causes resume to replay this turn's chunks
+      // on top of the persisted assistant message and duplicates the render.
+      await prisma.$transaction([
+        prisma.chat.update({
+          where: { id: chatId },
+          data: { messages: uiMessages as unknown as ChatMessagesForWrite },
+        }),
+        prisma.chatSession.upsert({
+          where: { id: chatId },
+          create: { id: chatId, publicAccessToken: chatAccessToken, lastEventId },
+          update: { publicAccessToken: chatAccessToken, lastEventId },
+        }),
+      ]);
 
       // Background self-review — a cheap model critiques the response and
       // injects coaching into the conversation before the next user message.
@@ -920,15 +926,18 @@ export const aiChatHydrated = chat
     },
 
     onTurnComplete: async ({ chatId, uiMessages, runId, chatAccessToken, lastEventId }) => {
-      await prisma.chat.update({
-        where: { id: chatId },
-        data: { messages: uiMessages as unknown as ChatMessagesForWrite },
-      });
-      await prisma.chatSession.upsert({
-        where: { id: chatId },
-        create: { id: chatId, publicAccessToken: chatAccessToken, lastEventId },
-        update: { publicAccessToken: chatAccessToken, lastEventId },
-      });
+      // See aiChat.onTurnComplete — atomic to avoid the resume-replay race.
+      await prisma.$transaction([
+        prisma.chat.update({
+          where: { id: chatId },
+          data: { messages: uiMessages as unknown as ChatMessagesForWrite },
+        }),
+        prisma.chatSession.upsert({
+          where: { id: chatId },
+          create: { id: chatId, publicAccessToken: chatAccessToken, lastEventId },
+          update: { publicAccessToken: chatAccessToken, lastEventId },
+        }),
+      ]);
     },
 
     run: async ({ messages, clientData, stopSignal }) => {