fix(chat): keep the zone wait countdown running under a steered message

The clock read the last message, which is the steered one while it trails the
running response, so the countdown froze. It now reads the live response.

Author: waleedlatif1

apps/sim/platform/lib/data/chat-model.test.ts

@@ -7,7 +7,7 @@
  */
 import { describe, expect, it } from 'vitest'
 import type { ChatMessage } from '@/app/workspace/[workspaceId]/home/types'
-import { toPlatformTurns } from '@/platform/lib/data/chat-model'
+import { isRunningWait, toPlatformTurns } from '@/platform/lib/data/chat-model'
 
 const options = {
   streaming: true,
@@ -53,3 +53,29 @@ describe('toPlatformTurns', () => {
     )
   })
 })
+
+describe('isRunningWait', () => {
+  const pausing: ChatMessage = {
+    id: 'pausing',
+    role: 'assistant',
+    content: '',
+    contentBlocks: [
+      { type: 'tool_call', toolCall: { id: 'wait-1', name: 'wait', status: 'executing' } },
+    ],
+  }
+
+  it('keeps counting down while a steered message trails the running response', () => {
+    const steered: ChatMessage = {
+      id: 'steered',
+      role: 'user',
+      content: 'Also this',
+      steering: { streamId: 'turn' },
+    }
+    expect(isRunningWait([pausing, steered])).toBe(true)
+  })
+
+  it('stops at the next turn: a wait left in an earlier response is not running', () => {
+    const next: ChatMessage = { id: 'next', role: 'user', content: 'Next' }
+    expect(isRunningWait([pausing, next])).toBe(false)
+  })
+})

apps/sim/platform/lib/data/chat-model.ts

@@ -526,6 +526,13 @@ function liveResponseIndex(messages: readonly ChatMessage[]): number {
   return -1
 }
 
+/** Whether the running response is paused in a `wait`, which counts down. */
+export function isRunningWait(messages: readonly ChatMessage[]): boolean {
+  return (messages[liveResponseIndex(messages)]?.contentBlocks ?? []).some(
+    (block) => block.toolCall?.name === 'wait' && block.toolCall.status === 'executing'
+  )
+}
+
 /**
  * The hook's transcript as Platform turns. A pure read of `messages`, so a replay, a reconnect or a
  * reload lands on the same turns, and it keeps the legacy parsers as the only readers of the wire.

apps/sim/platform/lib/data/chat.ts

@@ -27,7 +27,7 @@ import {
 import type { ChatRuntime, ToolDecision } from '@/platform/app/(shell)/_components/chat/model'
 import { platformUrl } from '@/platform/lib/data/base-path'
 import { draftToSend } from '@/platform/lib/data/chat-draft'
-import { toPlatformTurns } from '@/platform/lib/data/chat-model'
+import { isRunningWait, toPlatformTurns } from '@/platform/lib/data/chat-model'
 import { useAssistantReview } from '@/platform/lib/data/chat-review'
 import { useOrganization } from '@/platform/lib/data/organization'
 import { type SummaryRequest, useSendSummary } from '@/platform/lib/data/search-summary'
@@ -38,11 +38,7 @@ import { useToolPermissionStore } from '@/stores/tool-permission/store'
 /** A running `wait` counts down, and nothing else re-renders during the pause. */
 function useWaitClock(messages: readonly ChatMessage[], streaming: boolean): number {
   const [now, setNow] = useState(() => Date.now())
-  const waiting =
-    streaming &&
-    (messages.at(-1)?.contentBlocks ?? []).some(
-      (block) => block.toolCall?.name === 'wait' && block.toolCall.status === 'executing'
-    )
+  const waiting = streaming && isRunningWait(messages)
   useEffect(() => {
     if (!waiting) return
     const interval = setInterval(() => setNow(Date.now()), 1_000)