@tanstack/ai 0.8.0 → 0.8.1

package/README.md

@@ -87,18 +87,18 @@ Available adapters: `openaiText`, `openaiEmbed`, `openaiSummarize`, `anthropicTe
     <td>
       <a href="https://www.coderabbit.ai/?via=tanstack&dub_id=aCcEEdAOqqutX6OS" >
         <picture>
-          <source media="(prefers-color-scheme: dark)" srcset="https://tanstack.com/assets/coderabbit-dark-CMcuvjEy.svg" height="40" />
-          <source media="(prefers-color-scheme: light)" srcset="https://tanstack.com/assets/coderabbit-light-DVMJ2jHi.svg" height="40" />
-          <img src="https://tanstack.com/assets/coderabbit-light-DVMJ2jHi.svg" height="40" alt="CodeRabbit" />
+          <source media="(prefers-color-scheme: dark)" srcset="https://tanstack.com/assets/coderabbit-dark-D643Zkrv.svg" height="40" />
+          <source media="(prefers-color-scheme: light)" srcset="https://tanstack.com/assets/coderabbit-light-CIzGLYU_.svg" height="40" />
+          <img src="https://tanstack.com/assets/coderabbit-light-CIzGLYU_.svg" height="40" alt="CodeRabbit" />
         </picture>
       </a>
     </td>
     <td>
       <a href="https://www.cloudflare.com?utm_source=tanstack">
         <picture>
-          <source media="(prefers-color-scheme: dark)" srcset="https://tanstack.com/assets/cloudflare-white-DQDB7UaL.svg" height="60" />
-          <source media="(prefers-color-scheme: light)" srcset="https://tanstack.com/assets/cloudflare-black-CPufaW0B.svg" height="60" />
-          <img src="https://tanstack.com/assets/cloudflare-black-CPufaW0B.svg" height="60" alt="Cloudflare" />
+          <source media="(prefers-color-scheme: dark)" srcset="https://tanstack.com/assets/cloudflare-white-Co-Tyjbl.svg" height="60" />
+          <source media="(prefers-color-scheme: light)" srcset="https://tanstack.com/assets/cloudflare-black-6Ojsn8yh.svg" height="60" />
+          <img src="https://tanstack.com/assets/cloudflare-black-6Ojsn8yh.svg" height="60" alt="Cloudflare" />
         </picture>
       </a>
     </td>

package/dist/esm/activities/chat/stream/processor.d.ts

@@ -50,9 +50,8 @@ export interface StreamProcessorOptions {
  *
  * State tracking:
  * - Full message array
- * - Current assistant message being streamed
- * - Text content accumulation (reset on TEXT_MESSAGE_START)
- * - Multiple parallel tool calls
+ * - Per-message stream state (text, tool calls, thinking)
+ * - Multiple concurrent message streams
  * - Tool call completion via TOOL_CALL_END events
  *
  * @see docs/chat-architecture.md#streamprocessor-internal-state — State field reference
@@ -64,13 +63,11 @@ export declare class StreamProcessor {
     private jsonParser;
     private recordingEnabled;
     private messages;
-    private currentAssistantMessageId;
-    private totalTextContent;
-    private currentSegmentText;
-    private lastEmittedText;
-    private thinkingContent;
-    private toolCalls;
-    private toolCallOrder;
+    private messageStates;
+    private activeMessageIds;
+    private toolCallToMessage;
+    private pendingManualMessageId;
+    private activeRuns;
     private finishReason;
     private hasError;
     private isDone;
@@ -117,24 +114,13 @@ export declare class StreamProcessor {
      * @deprecated Use prepareAssistantMessage() instead. This eagerly creates
      * an assistant message which can cause empty message flicker.
      */
-    startAssistantMessage(): string;
+    startAssistantMessage(messageId?: string): string;
     /**
      * Get the current assistant message ID (if one has been created).
      * Returns null if prepareAssistantMessage() was called but no content
      * has arrived yet.
      */
     getCurrentAssistantMessageId(): string | null;
-    /**
-     * Lazily create the assistant message if it hasn't been created yet.
-     * Called by content handlers on the first content-bearing chunk.
-     * Returns the message ID.
-     *
-     * Content-bearing chunks that trigger this:
-     * TEXT_MESSAGE_CONTENT, TOOL_CALL_START, STEP_FINISHED, RUN_ERROR.
-     *
-     * @see docs/chat-architecture.md#streamprocessor-internal-state — Lazy creation pattern
-     */
-    private ensureAssistantMessage;
     /**
      * Add a tool result (called by client after handling onToolCall)
      */
@@ -173,23 +159,46 @@ export declare class StreamProcessor {
      *
      * Central dispatch for all AG-UI events. Each event type maps to a specific
      * handler. Events not listed in the switch are intentionally ignored
-     * (RUN_STARTED, TEXT_MESSAGE_END, STEP_STARTED, STATE_SNAPSHOT, STATE_DELTA).
+     * (RUN_STARTED, STEP_STARTED, STATE_DELTA).
      *
      * @see docs/chat-architecture.md#adapter-contract — Expected event types and ordering
      */
     processChunk(chunk: StreamChunk): void;
     /**
-     * Handle TEXT_MESSAGE_START event — marks the beginning of a new text segment.
-     * Resets segment accumulation so text after tool calls starts fresh.
-     *
-     * This is the key mechanism for multi-segment text (text before and after tool
-     * calls becoming separate TextParts). Without this reset, all text would merge
-     * into a single TextPart and tool-call interleaving would be lost.
+     * Create a new MessageStreamState for a message
+     */
+    private createMessageState;
+    /**
+     * Get the MessageStreamState for a message
+     */
+    private getMessageState;
+    /**
+     * Get the most recent active assistant message ID.
+     * Used as fallback for events that don't include a messageId.
+     */
+    private getActiveAssistantMessageId;
+    /**
+     * Ensure an active assistant message exists, creating one if needed.
+     * Used for backward compat when events arrive without prior TEXT_MESSAGE_START.
      *
-     * @see docs/chat-architecture.md#single-shot-text-response — Step-by-step text processing
-     * @see docs/chat-architecture.md#text-then-tool-interleaving-single-shot — Multi-segment text
+     * On reconnect/resume, a TEXT_MESSAGE_CONTENT may arrive for a message that
+     * already exists in this.messages (e.g. from initialMessages or a prior
+     * MESSAGES_SNAPSHOT) but whose transient state was cleared. In that case we
+     * hydrate state from the existing message rather than creating a duplicate.
+     */
+    private ensureAssistantMessage;
+    /**
+     * Handle TEXT_MESSAGE_START event
      */
     private handleTextMessageStartEvent;
+    /**
+     * Handle TEXT_MESSAGE_END event
+     */
+    private handleTextMessageEndEvent;
+    /**
+     * Handle MESSAGES_SNAPSHOT event
+     */
+    private handleMessagesSnapshotEvent;
     /**
      * Handle TEXT_MESSAGE_CONTENT event.
      *
@@ -244,12 +253,19 @@ export declare class StreamProcessor {
      * @see docs/chat-architecture.md#single-shot-tool-call-response — End-to-end flow
      */
     private handleToolCallEndEvent;
+    /**
+     * Handle RUN_STARTED event.
+     *
+     * Registers the run so that RUN_FINISHED can determine whether other
+     * runs are still active before finalizing.
+     */
+    private handleRunStartedEvent;
     /**
      * Handle RUN_FINISHED event.
      *
-     * Records the finishReason and calls completeAllToolCalls() as a safety net
-     * to force-complete any tool calls that didn't receive an explicit TOOL_CALL_END.
-     * This handles cases like aborted streams or adapter bugs.
+     * Records the finishReason and removes the run from activeRuns.
+     * Only finalizes when no more runs are active, so that concurrent
+     * runs don't interfere with each other.
      *
      * @see docs/chat-architecture.md#single-shot-tool-call-response — finishReason semantics
      * @see docs/chat-architecture.md#adapter-contract — Why RUN_FINISHED is mandatory
@@ -280,7 +296,11 @@ export declare class StreamProcessor {
      */
     private handleCustomEvent;
     /**
-     * Complete all tool calls — safety net for stream termination.
+     * Detect if an incoming content chunk represents a NEW text segment
+     */
+    private isNewTextSegment;
+    /**
+     * Complete all tool calls across all active messages — safety net for stream termination.
      *
      * Called by RUN_FINISHED and finalizeStream(). Force-transitions any tool call
      * not yet in input-complete state. Handles cases where TOOL_CALL_END was
@@ -289,12 +309,16 @@ export declare class StreamProcessor {
      * @see docs/chat-architecture.md#single-shot-tool-call-response — Safety net behavior
      */
     private completeAllToolCalls;
+    /**
+     * Complete all tool calls for a specific message
+     */
+    private completeAllToolCallsForMessage;
     /**
      * Mark a tool call as complete and emit event
      */
     private completeToolCall;
     /**
-     * Emit pending text update.
+     * Emit pending text update for a specific message.
      *
      * Calls updateTextPart() which has critical append-vs-replace logic:
      * - If last UIMessage part is TextPart → replaces its content (same segment).
@@ -302,7 +326,7 @@ export declare class StreamProcessor {
      *
      * @see docs/chat-architecture.md#uimessage-part-ordering-invariants — Replace vs. push logic
      */
-    private emitTextUpdate;
+    private emitTextUpdateForMessage;
     /**
      * Emit messages change event
      */
@@ -318,15 +342,15 @@ export declare class StreamProcessor {
      */
     finalizeStream(): void;
     /**
-     * Get completed tool calls in API format
+     * Get completed tool calls in API format (aggregated across all messages)
      */
     private getCompletedToolCalls;
     /**
-     * Get current result
+     * Get current result (aggregated across all messages)
      */
     private getResult;
     /**
-     * Get current processor state
+     * Get current processor state (aggregated across all messages)
      */
     getState(): ProcessorState;
     /**