ai 3.3.39 → 3.3.41

package/CHANGELOG.md

@@ -1,5 +1,18 @@
 # ai
 
+## 3.3.41
+
+### Patch Changes
+
+- Updated dependencies [692e265]
+  - @ai-sdk/vue@0.0.50
+
+## 3.3.40
+
+### Patch Changes
+
+- a91c308: feat (ai/core): add responseMessages to streamText
+
 ## 3.3.39
 
 ### Patch Changes

package/README.md

@@ -1,10 +1,10 @@
 ![hero illustration](./assets/hero.gif)
 
-# Vercel AI SDK
+# AI SDK
 
-The [Vercel AI SDK](https://sdk.vercel.ai/docs) is a TypeScript toolkit designed to help you build AI-powered applications using popular frameworks like Next.js, React, Svelte, Vue and runtimes like Node.js.
+The [AI SDK](https://sdk.vercel.ai/docs) is a TypeScript toolkit designed to help you build AI-powered applications using popular frameworks like Next.js, React, Svelte, Vue and runtimes like Node.js.
 
-To learn more about how to use the Vercel AI SDK, check out our [API Reference](https://sdk.vercel.ai/docs/reference) and [Documentation](https://sdk.vercel.ai/docs).
+To learn more about how to use the AI SDK, check out our [API Reference](https://sdk.vercel.ai/docs/reference) and [Documentation](https://sdk.vercel.ai/docs).
 
 ## Installation
 
@@ -148,6 +148,13 @@ async function submitMessage() {
     ui: stream.value,
   };
 }
+```
+
+###### @/app/ai.ts (Next.js App Router)
+
+```tsx
+import { createAI } from 'ai/rsc';
+import { submitMessage } from '@/app/actions';
 
 export const AI = createAI({
   initialAIState: {},
@@ -162,7 +169,7 @@ export const AI = createAI({
 
 ```tsx
 import { ReactNode } from 'react';
-import { AI } from '@/app/actions';
+import { AI } from '@/app/ai';
 
 export default function Layout({ children }: { children: ReactNode }) {
   <AI>{children}</AI>;
@@ -209,11 +216,11 @@ We've built [templates](https://vercel.com/templates?type=ai) that include AI SD
 
 ## Community
 
-The Vercel AI SDK community can be found on [GitHub Discussions](https://github.com/vercel/ai/discussions) where you can ask questions, voice ideas, and share your projects with other people.
+The AI SDK community can be found on [GitHub Discussions](https://github.com/vercel/ai/discussions) where you can ask questions, voice ideas, and share your projects with other people.
 
 ## Contributing
 
-Contributions to the Vercel AI SDK are welcome and highly appreciated. However, before you jump right into it, we would like you to review our [Contribution Guidelines](https://github.com/vercel/ai/blob/main/CONTRIBUTING.md) to make sure you have smooth experience contributing to Vercel AI SDK.
+Contributions to the AI SDK are welcome and highly appreciated. However, before you jump right into it, we would like you to review our [Contribution Guidelines](https://github.com/vercel/ai/blob/main/CONTRIBUTING.md) to make sure you have smooth experience contributing to AI SDK.
 
 ## Authors
 

package/dist/index.d.mts

@@ -1394,11 +1394,12 @@ interface GenerateTextResult<TOOLS extends Record<string, CoreTool>> {
      */
     readonly warnings: CallWarning[] | undefined;
     /**
-    The response messages that were generated during the call. It consists of an assistant message,
-    potentially containing tool calls.
-    When there are tool results, there is an additional tool message with the tool results that are available.
-    If there are tools that do not have execute functions, they are not included in the tool results and
-    need to be added separately.
+  The response messages that were generated during the call. It consists of an assistant message,
+  potentially containing tool calls.
+  
+  When there are tool results, there is an additional tool message with the tool results that are available.
+  If there are tools that do not have execute functions, they are not included in the tool results and
+  need to be added separately.
        */
     readonly responseMessages: Array<CoreAssistantMessage | CoreToolMessage>;
     /**
@@ -1614,6 +1615,17 @@ interface StreamTextResult<TOOLS extends Record<string, CoreTool>> {
         headers?: Record<string, string>;
     };
     /**
+  The response messages that were generated during the call. It consists of an assistant message,
+  potentially containing tool calls.
+  
+  When there are tool results, there is an additional tool message with the tool results that are available.
+  If there are tools that do not have execute functions, they are not included in the tool results and
+  need to be added separately.
+  
+  Resolved when the response is finished.
+       */
+    readonly responseMessages: Promise<Array<CoreAssistantMessage | CoreToolMessage>>;
+    /**
   Details for all steps.
   You can use this to get information about intermediate steps,
   such as the tool calls or the response headers.
@@ -1887,7 +1899,16 @@ The usage is the combined usage of all steps.
         /**
 Details for all steps.
        */
-        steps: StepResult<TOOLS>[];
+        readonly steps: StepResult<TOOLS>[];
+        /**
+The response messages that were generated during the call. It consists of an assistant message,
+potentially containing tool calls.
+
+When there are tool results, there is an additional tool message with the tool results that are available.
+If there are tools that do not have execute functions, they are not included in the tool results and
+need to be added separately.
+     */
+        readonly responseMessages: Array<CoreAssistantMessage | CoreToolMessage>;
     }) => Promise<void> | void;
     /**
     Callback that is called when each step (LLM call) is finished, including intermediate steps.

package/dist/index.d.ts

@@ -1394,11 +1394,12 @@ interface GenerateTextResult<TOOLS extends Record<string, CoreTool>> {
      */
     readonly warnings: CallWarning[] | undefined;
     /**
-    The response messages that were generated during the call. It consists of an assistant message,
-    potentially containing tool calls.
-    When there are tool results, there is an additional tool message with the tool results that are available.
-    If there are tools that do not have execute functions, they are not included in the tool results and
-    need to be added separately.
+  The response messages that were generated during the call. It consists of an assistant message,
+  potentially containing tool calls.
+  
+  When there are tool results, there is an additional tool message with the tool results that are available.
+  If there are tools that do not have execute functions, they are not included in the tool results and
+  need to be added separately.
        */
     readonly responseMessages: Array<CoreAssistantMessage | CoreToolMessage>;
     /**
@@ -1614,6 +1615,17 @@ interface StreamTextResult<TOOLS extends Record<string, CoreTool>> {
         headers?: Record<string, string>;
     };
     /**
+  The response messages that were generated during the call. It consists of an assistant message,
+  potentially containing tool calls.
+  
+  When there are tool results, there is an additional tool message with the tool results that are available.
+  If there are tools that do not have execute functions, they are not included in the tool results and
+  need to be added separately.
+  
+  Resolved when the response is finished.
+       */
+    readonly responseMessages: Promise<Array<CoreAssistantMessage | CoreToolMessage>>;
+    /**
   Details for all steps.
   You can use this to get information about intermediate steps,
   such as the tool calls or the response headers.
@@ -1887,7 +1899,16 @@ The usage is the combined usage of all steps.
         /**
 Details for all steps.
        */
-        steps: StepResult<TOOLS>[];
+        readonly steps: StepResult<TOOLS>[];
+        /**
+The response messages that were generated during the call. It consists of an assistant message,
+potentially containing tool calls.
+
+When there are tool results, there is an additional tool message with the tool results that are available.
+If there are tools that do not have execute functions, they are not included in the tool results and
+need to be added separately.
+     */
+        readonly responseMessages: Array<CoreAssistantMessage | CoreToolMessage>;
     }) => Promise<void> | void;
     /**
     Callback that is called when each step (LLM call) is finished, including intermediate steps.

package/dist/index.js

@@ -3931,6 +3931,11 @@ var DefaultStreamTextResult = class {
     this.experimental_providerMetadata = providerMetadataPromise;
     const { resolve: resolveResponse, promise: responsePromise } = createResolvablePromise();
     this.response = responsePromise;
+    const {
+      resolve: resolveResponseMessages,
+      promise: responseMessagesPromise
+    } = createResolvablePromise();
+    this.responseMessages = responseMessagesPromise;
     const {
       stream: stitchableStream,
       addStream,
@@ -4177,6 +4182,17 @@ var DefaultStreamTextResult = class {
                     }
                   })
                 );
+                const responseMessages = stepResults.reduce(
+                  (responseMessages2, step) => [
+                    ...responseMessages2,
+                    ...toResponseMessages({
+                      text: step.text,
+                      toolCalls: step.toolCalls,
+                      toolResults: step.toolResults
+                    })
+                  ],
+                  []
+                );
                 resolveUsage(combinedUsage);
                 resolveFinishReason(stepFinishReason);
                 resolveText(stepText);
@@ -4188,6 +4204,7 @@ var DefaultStreamTextResult = class {
                   headers: rawResponse == null ? void 0 : rawResponse.headers
                 });
                 resolveSteps(stepResults);
+                resolveResponseMessages(responseMessages);
                 await (onFinish == null ? void 0 : onFinish({
                   finishReason: stepFinishReason,
                   logprobs: stepLogProbs,
@@ -4206,8 +4223,8 @@ var DefaultStreamTextResult = class {
                   },
                   warnings,
                   experimental_providerMetadata: stepProviderMetadata,
-                  steps: stepResults
-                  // see tool results comment above
+                  steps: stepResults,
+                  responseMessages
                 }));
               } catch (error) {
                 controller.error(error);