@trigger.dev/sdk 0.0.0-chat-prerelease-20260505140031 → 0.0.0-chat-prerelease-20260507122230

package/dist/commonjs/v3/ai.d.ts

@@ -263,6 +263,28 @@ export type ChatTurnUsage = LanguageModelUsage;
  * and converts to `ModelMessage[]` internally.
  */
 declare function setChatMessages<TUIM extends UIMessage = UIMessage>(uiMessages: TUIM[]): void;
+/**
+ * A tool call surfaced by `chat.history.getPendingToolCalls()` /
+ * `getResolvedToolCalls()`. Identifies the call by its `toolCallId` plus
+ * the `messageId` of the assistant message that hosts it, so callers can
+ * locate the part precisely without re-walking the chain.
+ */
+export type ChatToolCallRef = {
+    toolCallId: string;
+    toolName: string;
+    messageId: string;
+};
+/**
+ * A new tool result surfaced by `chat.history.extractNewToolResults()`.
+ * `errorText` is set iff the part is in `output-error` state; otherwise
+ * `output` carries the resolved value.
+ */
+export type ChatNewToolResult = {
+    toolCallId: string;
+    toolName: string;
+    output: unknown;
+    errorText?: string;
+};
 /** State stored in locals during prepareStep compaction. */
 interface CompactionState {
     summary: string;
@@ -1188,13 +1210,18 @@ export type ChatAgentOptions<TIdentifier extends string, TClientDataSchema exten
     /**
      * Called when the frontend sends a custom action via `transport.sendAction()`.
      *
-     * Fires after message hydration (if set) but before `onTurnStart` and `run()`.
-     * Use `chat.history.*` to modify the conversation state — the LLM will respond
-     * to the modified state.
+     * Actions are not turns. They fire `hydrateMessages` (if configured) and
+     * `onAction` only — no `onTurnStart` / `prepareMessages` /
+     * `onBeforeTurnComplete` / `onTurnComplete`, no `run()`. Use
+     * `chat.history.*` inside `onAction` to mutate state.
+     *
+     * To produce a model response from an action, return a
+     * `StreamTextResult` (auto-piped), `string`, or `UIMessage`. Returning
+     * `void` or nothing is the side-effect-only default.
      */
     onAction?: (event: ActionEvent<[
         TActionSchema
-    ] extends [TaskSchema] ? inferSchemaOut<TActionSchema> : unknown, inferSchemaOut<TClientDataSchema>, TUIMessage>) => Promise<void> | void;
+    ] extends [TaskSchema] ? inferSchemaOut<TActionSchema> : unknown, inferSchemaOut<TClientDataSchema>, TUIMessage>) => Promise<unknown> | unknown;
     /**
      * The run function for the chat task.
      *
@@ -2488,6 +2515,40 @@ export declare const chat: {
     history: {
         /** Read the current accumulated UI messages (copy). */
         all(): UIMessage[];
+        /**
+         * Read the current chain as an ordered `UIMessage[]`. Alias for `all()` —
+         * use this when working alongside parent-aware APIs (TRI-9120) where
+         * "chain" disambiguates from "graph".
+         */
+        getChain(): UIMessage[];
+        /**
+         * Find a message by id. Returns `undefined` if no message with that id
+         * is present in the current chain.
+         */
+        findMessage(messageId: string): UIMessage | undefined;
+        /**
+         * Tool calls on the leaf assistant message still waiting on an answer
+         * (`input-available` state). Use this to gate fresh user turns during
+         * HITL flows: if `getPendingToolCalls().length > 0`, an `addToolOutput`
+         * is expected before any new user message.
+         *
+         * Returns `[]` if there is no assistant message yet, or if the leaf
+         * assistant has no pending tool calls.
+         */
+        getPendingToolCalls(): ChatToolCallRef[];
+        /**
+         * Tool calls across the chain with a final result (`output-available`
+         * or `output-error`). Use this to dedup re-saves when the AI SDK
+         * resends an assistant message with progressively more answered parts.
+         */
+        getResolvedToolCalls(): ChatToolCallRef[];
+        /**
+         * Pure helper: returns the tool parts in `message` whose results are
+         * not already represented in the current chain. Use this when
+         * persisting tool results to your own store: each call surfaces only
+         * the *new* answers, so writes stay idempotent across re-streams.
+         */
+        extractNewToolResults(message: UIMessage): ChatNewToolResult[];
         /** Replace all accumulated messages. Same as `chat.setMessages()`. */
         set(messages: UIMessage[]): void;
         /** Remove a specific message by ID. */