ai 7.0.145 → 7.0.147

package/docs/03-ai-sdk-harnesses/05-harness-adapters.mdx

@@ -36,12 +36,12 @@ The AI SDK includes the following harness adapters:
 | Adapter                                                      | Runtime location | Custom tools | Custom skills | Structured output | Built-in tool approval | Built-in tool filtering      | Image input | History access |
 | ------------------------------------------------------------ | ---------------- | ------------ | ------------- | ----------------- | ---------------------- | ---------------------------- | ----------- | -------------- |
 | [Claude Code](/providers/ai-sdk-harnesses/claude-code)       | Sandbox bridge   | <Check />    | <Check />     | <Check />         | <Check />              | <Check />                    | <Check />   | <Cross />      |
-| [Cline](/providers/ai-sdk-harnesses/cline)                   | Host process     | <Check />    | <Check />     | <Check />         | <Check />              | <Check />                    | <Cross />   | <Cross />      |
-| [Codex](/providers/ai-sdk-harnesses/codex)                   | Sandbox bridge   | <Check />    | <Check />     | <Check />         | <Cross />              | <Cross />                    | <Cross />   | <Cross />      |
-| [Cursor](/providers/ai-sdk-harnesses/cursor)                 | Sandbox via ACP  | <Check />    | <Check />     | <Cross />         | <Cross />              | <Cross />                    | <Cross />   | <Cross />      |
-| [Deep Agents](/providers/ai-sdk-harnesses/deepagents)        | Sandbox bridge   | <Check />    | <Check />     | <Check />         | <Check />              | <Check /> via auto-rejection | <Cross />   | <Cross />      |
+| [Cline](/providers/ai-sdk-harnesses/cline)                   | Host process     | <Check />    | <Check />     | <Check />         | <Check />              | <Check />                    | <Check />   | <Cross />      |
+| [Codex](/providers/ai-sdk-harnesses/codex)                   | Sandbox bridge   | <Check />    | <Check />     | <Check />         | <Cross />              | <Cross />                    | <Check />   | <Cross />      |
+| [Cursor](/providers/ai-sdk-harnesses/cursor)                 | Sandbox via ACP  | <Check />    | <Check />     | <Cross />         | <Cross />              | <Cross />                    | <Check />   | <Cross />      |
+| [Deep Agents](/providers/ai-sdk-harnesses/deepagents)        | Sandbox bridge   | <Check />    | <Check />     | <Check />         | <Check />              | <Check /> via auto-rejection | <Check />   | <Cross />      |
 | [fx](/providers/ai-sdk-harnesses/fx)                         | Host process     | <Check />    | <Check />     | <Check />         | <Check />              | <Check />                    | <Cross />   | <Cross />      |
-| [GitHub Copilot](/providers/ai-sdk-harnesses/github-copilot) | Sandbox via ACP  | <Check />    | <Check />     | <Cross />         | <Cross />              | <Cross />                    | <Cross />   | <Cross />      |
-| [Grok Build](/providers/ai-sdk-harnesses/grok-build)         | Sandbox via ACP  | <Check />    | <Check />     | <Check />         | <Cross />              | <Cross />                    | <Cross />   | <Cross />      |
-| [OpenCode](/providers/ai-sdk-harnesses/opencode)             | Sandbox bridge   | <Check />    | <Check />     | <Check />         | <Check />              | <Check />                    | <Cross />   | <Cross />      |
-| [Pi](/providers/ai-sdk-harnesses/pi)                         | Host process     | <Check />    | <Check />     | <Cross />         | <Check />              | <Check />                    | <Cross />   | <Cross />      |
+| [GitHub Copilot](/providers/ai-sdk-harnesses/github-copilot) | Sandbox via ACP  | <Check />    | <Check />     | <Cross />         | <Cross />              | <Cross />                    | <Check />   | <Cross />      |
+| [Grok Build](/providers/ai-sdk-harnesses/grok-build)         | Sandbox via ACP  | <Check />    | <Check />     | <Check />         | <Cross />              | <Cross />                    | <Check />   | <Cross />      |
+| [OpenCode](/providers/ai-sdk-harnesses/opencode)             | Sandbox bridge   | <Check />    | <Check />     | <Check />         | <Check />              | <Check />                    | <Check />   | <Cross />      |
+| [Pi](/providers/ai-sdk-harnesses/pi)                         | Host process     | <Check />    | <Check />     | <Cross />         | <Check />              | <Check />                    | <Check />   | <Cross />      |

package/docs/03-ai-sdk-harnesses/06-workflow-utilities.mdx

@@ -308,6 +308,18 @@ export async function POST(request: Request) {
 }
 ```
 
+If you use Next.js, wrap your config with `withWorkflow()` so the Workflow SDK
+transforms `'use workflow'` and `'use step'` modules. Other frameworks have
+their own Workflow SDK setup.
+
+```js filename='next.config.js'
+import { withWorkflow } from 'workflow/next';
+
+const nextConfig = {};
+
+export default withWorkflow(nextConfig);
+```
+
 The workflow state `sessionId` identifies the harness session. The step derives
 `sandboxId` from it; otherwise, you must persist `sandboxSession.id` separately
 to reattach across steps. Keep

package/docs/03-ai-sdk-harnesses/07-ui.mdx

@@ -93,7 +93,7 @@ export const agent = new HarnessAgent({
 
 Persist the opaque resume state returned by `session.detach()`. If the
 turn paused for approval or was otherwise interrupted, that resume state carries
-the continuation state internally. The chat id can also be the harness
+the continuation state internally. The chat ID can also be the harness
 `sessionId`. Here we derive a stable `sandboxId` from that known chat id. If
 you do not derive one, persist the returned `sandboxSession.id` separately.
 
@@ -170,7 +170,7 @@ export async function POST(request: Request) {
   } = await request.json();
 
   if (!body.id) {
-    throw new Error('Missing chat id');
+    return new Response('Missing chat ID', { status: 400 });
   }
 
   const chatId = body.id;

package/docs/04-ai-sdk-ui/03-chatbot-tool-usage.mdx

@@ -16,12 +16,12 @@ The flow is as follows:
 
 1. The user enters a message in the chat UI.
 1. The message is sent to the API route.
-1. In your server side route, the language model generates tool calls during the `streamText` call.
+1. In your server-side route, the language model generates tool calls during the `streamText` call.
 1. All tool calls are forwarded to the client.
 1. Server-side tools are executed using their `execute` method and their results are forwarded to the client.
 1. Client-side tools that should be automatically executed are handled with the `onToolCall` callback.
    You must call `addToolOutput` to provide the tool result.
-1. Client-side tool that require user interactions can be displayed in the UI.
+1. Client-side tools that require user interactions can be displayed in the UI.
    The tool calls and results are available as tool invocation parts in the `parts` property of the last assistant message.
 1. When the user interaction is done, `addToolOutput` can be used to add the tool result to the chat.
 1. The chat can be configured to automatically submit when all tool results are available using `sendAutomaticallyWhen`.

package/docs/05-ai-sdk-rsc/01-overview.mdx

@@ -16,7 +16,7 @@ description: An overview of AI SDK RSC.
   Server Components.
 </Note>
 
-[React Server Components](https://nextjs.org/docs/app/building-your-application/rendering/server-components) (RSC) allow you to write UI that can be rendered on the server and streamed to the client. RSCs enable [ Server Actions ](https://nextjs.org/docs/app/building-your-application/data-fetching/server-actions-and-mutations#with-client-components), a new way to call server-side code directly from the client just like any other function with end-to-end type-safety. This combination opens the door to a new way of building AI applications, allowing the large language model (LLM) to generate and stream UI directly from the server to the client.
+[React Server Components](https://nextjs.org/docs/app/building-your-application/rendering/server-components) (RSC) allow you to write UI that can be rendered on the server and streamed to the client. RSCs enable [Server Actions](https://nextjs.org/docs/app/building-your-application/data-fetching/server-actions-and-mutations#with-client-components), a new way to call server-side code directly from the client just like any other function with end-to-end type-safety. This combination opens the door to a new way of building AI applications, allowing the large language model (LLM) to generate and stream UI directly from the server to the client.
 
 ## AI SDK RSC Functions
 

package/docs/05-ai-sdk-rsc/10-migrating-to-ui.mdx

@@ -166,7 +166,7 @@ export default function Page() {
 
 In AI SDK RSC, `streamUI` does not support parallel tool calls. You will have to use a combination of `streamText`, `createStreamableUI` and `createStreamableValue`.
 
-With AI SDK UI, `useChat` comes with built-in support for parallel tool calls. You can define multiple tools in the `streamText` and have them called them in parallel. The `useChat` hook will then handle the parallel tool calls for you automatically.
+With AI SDK UI, `useChat` comes with built-in support for parallel tool calls. You can define multiple tools in the `streamText` and have them called in parallel. The `useChat` hook will then handle the parallel tool calls for you automatically.
 
 ### Multi-Step Tool Calls
 

package/docs/06-advanced/01-prompt-engineering.mdx

@@ -17,7 +17,7 @@ Prompts are the starting points for LLMs. They are the inputs that trigger the m
 
 ## Why is prompt engineering needed?
 
-Prompt engineering currently plays a pivotal role in shaping the responses of LLMs. It allows us to tweak the model to respond more effectively to a broader range of queries. This includes the use of techniques like semantic search, command grammars, and the ReActive model architecture. The performance, context window, and cost of LLMs varies between models and model providers which adds further constraints to the mix. For example, the GPT-4 model is more expensive than GPT-3.5-turbo and significantly slower, but it can also be more effective at certain tasks. And so, like many things in software engineering, there is a trade-offs between cost and performance.
+Prompt engineering currently plays a pivotal role in shaping the responses of LLMs. It allows us to tweak the model to respond more effectively to a broader range of queries. This includes the use of techniques like semantic search, command grammars, and the ReActive model architecture. The performance, context window, and cost of LLMs varies between models and model providers which adds further constraints to the mix. For example, the GPT-4 model is more expensive than GPT-3.5-turbo and significantly slower, but it can also be more effective at certain tasks. And so, like many things in software engineering, there is a trade-off between cost and performance.
 
 To assist with comparing and tweaking LLMs, we've built an AI playground that allows you to compare the performance of different models side-by-side online. When you're ready, you can even generate code with the AI SDK to quickly use your prompt and your selected model into your own applications.
 

package/docs/06-advanced/03-backpressure.mdx

@@ -120,7 +120,7 @@ function createStream(iterator) {
 }
 // Collect data from stream
 async function run() {
-  // Set up a stream that of integers
+  // Set up a stream of integers
   const stream = createStream(integers());
 
   // Read values from our stream

package/docs/06-advanced/10-vercel-deployment-guide.mdx

@@ -16,7 +16,7 @@ Vercel allows for automatic deployments on every branch push and merges onto the
 To follow along with this guide, you will need:
 
 - a Vercel account
-- an account with a Git provider (this tutorial will use [Github](https://github.com))
+- an account with a Git provider (this tutorial will use [GitHub](https://github.com))
 - an OpenAI API key
 
 This guide will teach you how to deploy the application you built in the Next.js (App Router) quickstart tutorial to Vercel. If you haven’t completed the quickstart guide, you can start with [this repo](https://github.com/vercel-labs/ai-sdk-deployment-guide).

package/docs/07-reference/01-ai-sdk-core/01-generate-text.mdx

@@ -7,7 +7,7 @@ description: API Reference for generateText.
 
 Generates text and calls tools for a given prompt using a language model.
 
-It is ideal for non-interactive use cases such as automation tasks where you need to write text (e.g. drafting email or summarizing web pages) and for agents that use tools.
+It is ideal for non-interactive use cases such as automation tasks where you need to write text (e.g. drafting emails or summarizing web pages) and for agents that use tools.
 
 ```ts
 import { generateText } from 'ai';

package/docs/07-reference/01-ai-sdk-core/14-decide.mdx

@@ -14,19 +14,24 @@ state. See [Decisions](/docs/ai-sdk-core/decisions) for examples and semantics.
 
 ## Parameters
 
-| Parameter         | Type                                             | Description                                                                                                                               |
-| ----------------- | ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
-| `model`           | `Experimental_DecisionModel`                     | Required experimental v4 model instance or a string ID resolved by Gateway or an explicitly configured decision-capable default provider. |
-| `state`           | `Experimental_DecisionState`                     | Required string, JSON object, or ordered array of text, file, and JSON parts.                                                             |
-| `questions`       | `Record<string, Experimental_DecisionQuestion>`  | Required nonempty question map.                                                                                                           |
-| `maxRetries`      | `number`                                         | Nonnegative integer; defaults to 2.                                                                                                       |
-| `abortSignal`     | `AbortSignal`                                    | Cancels the decisions request.                                                                                                            |
-| `headers`         | `Record<string, string>`                         | Additional HTTP headers.                                                                                                                  |
-| `providerOptions` | `ProviderOptions`                                | Provider-specific options.                                                                                                                |
-| `telemetry`       | `TelemetryOptions`                               | Telemetry configuration, including per-call integrations, input/output recording, and a function ID.                                      |
-| `runtimeContext`  | `Record<string, unknown>`                        | Context available to lifecycle callbacks and selectively included in telemetry with `telemetry.includeRuntimeContext`.                    |
-| `onStart`         | `(event: Experimental_DecideStartEvent) => void` | Called when the decision operation begins.                                                                                                |
-| `onEnd`           | `(event: Experimental_DecideEndEvent) => void`   | Called when the decision operation completes successfully.                                                                                |
+| Parameter         | Type                                                                                           | Description                                                                                                                               |
+| ----------------- | ---------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| `model`           | `Experimental_DecisionModel`                                                                   | Required experimental v4 model instance or a string ID resolved by Gateway or an explicitly configured decision-capable default provider. |
+| `state`           | `Experimental_DecisionState`                                                                   | Required string, JSON object, or ordered array of text, file, and JSON parts.                                                             |
+| `questions`       | `Record<string, Experimental_DecisionQuestion>`                                                | Required nonempty question map.                                                                                                           |
+| `maxOutputTokens` | `number`                                                                                       | Optional maximum output tokens, an integer >= 1.                                                                                          |
+| `reasoning`       | `'provider-default' \| 'none' \| 'minimal' \| 'low' \| 'medium' \| 'high' \| 'xhigh' \| 'max'` | Optional reasoning effort. Language-model adapters default to `'none'`. Native decision providers return an unsupported-setting warning.  |
+| `maxRetries`      | `number`                                                                                       | Nonnegative integer; defaults to 2.                                                                                                       |
+| `abortSignal`     | `AbortSignal`                                                                                  | Cancels the decisions request.                                                                                                            |
+| `headers`         | `Record<string, string>`                                                                       | Additional HTTP headers.                                                                                                                  |
+| `providerOptions` | `ProviderOptions`                                                                              | Provider-specific options.                                                                                                                |
+| `telemetry`       | `TelemetryOptions`                                                                             | Telemetry configuration, including per-call integrations, input/output recording, and a function ID.                                      |
+| `runtimeContext`  | `Record<string, unknown>`                                                                      | Context available to lifecycle callbacks and selectively included in telemetry with `telemetry.includeRuntimeContext`.                    |
+| `onStart`         | `(event: Experimental_DecideStartEvent) => void`                                               | Called when the decision operation begins.                                                                                                |
+| `onEnd`           | `(event: Experimental_DecideEndEvent) => void`                                                 | Called when the decision operation completes successfully.                                                                                |
+
+Set `reasoning: 'provider-default'` to use the underlying language model's default
+reasoning effort instead of the adapter's `'none'` default.
 
 See [Lifecycle Callbacks](/docs/ai-sdk-core/lifecycle-callbacks#experimental_decide)
 for the complete `onStart` and `onEnd` event fields.

package/docs/07-reference/01-ai-sdk-core/14-upload-skill.mdx

@@ -17,7 +17,7 @@ const { providerReference } = await uploadSkill({
   files: [
     {
       path: 'my-skill/SKILL.md',
-      content: readFileSync('./SKILL.md'),
+      data: readFileSync('./SKILL.md'),
     },
   ],
   displayTitle: 'My Skill',
@@ -42,9 +42,9 @@ const { providerReference } = await uploadSkill({
     },
     {
       name: 'files',
-      type: 'SkillsV4File[]',
+      type: 'UploadSkillFile[]',
       description:
-        'The files that make up the skill. Each file has a relative `path` and `content` (either a `Uint8Array` or a base64-encoded string).',
+        "The files that make up the skill. Each file must have a relative `path` and `data`. The `data` can be a string, a `Uint8Array`, or an object with `type: 'text'` and a string `text` value, or `type: 'data'` and a string `data` value.",
     },
     {
       name: 'displayTitle',

package/docs/07-reference/01-ai-sdk-core/22-dynamic-tool.mdx

@@ -224,7 +224,7 @@ When used with useChat (`UIMessage` format), dynamic tools appear as `dynamic-to
     switch (part.type) {
       case 'dynamic-tool':
         return (
-          <div>
+          <div key={part.toolCallId}>
             <h4>Tool: {part.toolName}</h4>
             <pre>{JSON.stringify(part.input, null, 2)}</pre>
           </div>

package/docs/08-migration-guides/index.mdx

@@ -6,18 +6,18 @@ collapsed: true
 
 # Migration Guides
 
-- [ Migrate AI SDK 6.x to 7.0 ](/docs/migration-guides/migration-guide-7-0)
-- [ Migrate AI SDK 5.x to 6.0 ](/docs/migration-guides/migration-guide-6-0)
-- [ Migrate AI SDK 4.x to 5.0 ](/docs/migration-guides/migration-guide-5-0)
-- [ Migrate your data to AI SDK 5.0 ](/docs/migration-guides/migration-guide-5-0-data)
-- [ Migrate AI SDK 4.1 to 4.2 ](/docs/migration-guides/migration-guide-4-2)
-- [ Migrate AI SDK 4.0 to 4.1 ](/docs/migration-guides/migration-guide-4-1)
-- [ Migrate AI SDK 3.4 to 4.0 ](/docs/migration-guides/migration-guide-4-0)
-- [ Migrate AI SDK 3.3 to 3.4 ](/docs/migration-guides/migration-guide-3-4)
-- [ Migrate AI SDK 3.2 to 3.3 ](/docs/migration-guides/migration-guide-3-3)
-- [ Migrate AI SDK 3.1 to 3.2 ](/docs/migration-guides/migration-guide-3-2)
-- [ Migrate AI SDK 3.0 to 3.1 ](/docs/migration-guides/migration-guide-3-1)
+- [Migrate AI SDK 6.x to 7.0](/docs/migration-guides/migration-guide-7-0)
+- [Migrate AI SDK 5.x to 6.0](/docs/migration-guides/migration-guide-6-0)
+- [Migrate AI SDK 4.x to 5.0](/docs/migration-guides/migration-guide-5-0)
+- [Migrate your data to AI SDK 5.0](/docs/migration-guides/migration-guide-5-0-data)
+- [Migrate AI SDK 4.1 to 4.2](/docs/migration-guides/migration-guide-4-2)
+- [Migrate AI SDK 4.0 to 4.1](/docs/migration-guides/migration-guide-4-1)
+- [Migrate AI SDK 3.4 to 4.0](/docs/migration-guides/migration-guide-4-0)
+- [Migrate AI SDK 3.3 to 3.4](/docs/migration-guides/migration-guide-3-4)
+- [Migrate AI SDK 3.2 to 3.3](/docs/migration-guides/migration-guide-3-3)
+- [Migrate AI SDK 3.1 to 3.2](/docs/migration-guides/migration-guide-3-2)
+- [Migrate AI SDK 3.0 to 3.1](/docs/migration-guides/migration-guide-3-1)
 
 ## Versioning
 
-- [ Versioning ](/docs/migration-guides/versioning)
+- [Versioning](/docs/migration-guides/versioning)

package/docs/09-troubleshooting/05-tool-invocation-missing-result.mdx

@@ -38,7 +38,7 @@ const tools = {
 };
 ```
 
-2. Client-side execution with `useChat` (omitting the `execute` function), you must provide results using `addToolOutput`:
+2. For client-side execution with `useChat` (omitting the `execute` function), you must provide results using `addToolOutput`:
 
 ```tsx
 import { useChat } from '@ai-sdk/react';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ai",
-  "version": "7.0.145",
+  "version": "7.0.147",
   "type": "module",
   "description": "AI SDK by Vercel - build apps like ChatGPT, Claude, Gemini, and more with a single interface for any model using the Vercel AI Gateway or go direct to OpenAI, Anthropic, Google, or any other model provider.",
   "license": "Apache-2.0",
@@ -42,20 +42,20 @@
     }
   },
   "dependencies": {
-    "@ai-sdk/gateway": "4.0.118",
-    "@ai-sdk/provider": "4.0.30",
-    "@ai-sdk/provider-utils": "5.0.63"
+    "@ai-sdk/gateway": "4.0.120",
+    "@ai-sdk/provider": "4.0.31",
+    "@ai-sdk/provider-utils": "5.0.64"
   },
   "devDependencies": {
-    "@ai-sdk/amazon-bedrock": "5.0.119",
-    "@ai-sdk/deepseek": "3.0.68",
-    "@ai-sdk/google": "4.0.100",
-    "@ai-sdk/groq": "4.0.65",
-    "@ai-sdk/huggingface": "2.0.73",
-    "@ai-sdk/moonshotai": "3.0.72",
-    "@ai-sdk/openai": "4.0.97",
+    "@ai-sdk/amazon-bedrock": "5.0.120",
+    "@ai-sdk/deepseek": "3.0.69",
+    "@ai-sdk/google": "4.0.101",
+    "@ai-sdk/groq": "4.0.66",
+    "@ai-sdk/huggingface": "2.0.74",
+    "@ai-sdk/moonshotai": "3.0.73",
+    "@ai-sdk/openai": "4.0.98",
     "@ai-sdk/test-server": "2.0.4",
-    "@ai-sdk/xai": "5.0.25",
+    "@ai-sdk/xai": "5.0.26",
     "@edge-runtime/vm": "^5.0.0",
     "@smithy/eventstream-codec": "^4.3.3",
     "@smithy/util-utf8": "^4.3.3",

package/src/decide/decide-events.ts

@@ -34,6 +34,12 @@ export type DecideStartEvent<RUNTIME_CONTEXT extends Context = Context> = {
   /** The questions to decide against the shared state. */
   readonly questions: Readonly<Record<string, DecisionQuestion>>;
 
+  /** Maximum output tokens requested for the decision. */
+  readonly maxOutputTokens?: number;
+
+  /** Reasoning effort requested for the decision. */
+  readonly reasoning?: DecisionModelV4CallOptions['reasoning'];
+
   /** Maximum number of retries for the decision model call. */
   readonly maxRetries: number;
 

package/src/decide/decide.ts

@@ -2,6 +2,7 @@ import {
   Experimental_DecisionRefusalError as DecisionRefusalError,
   Experimental_DecisionUnsupportedQuestionTypeError as DecisionUnsupportedQuestionTypeError,
   type Experimental_DecisionModelV4Question as DecisionQuestion,
+  type Experimental_DecisionModelV4CallOptions as DecisionCallOptions,
 } from '@ai-sdk/provider';
 import {
   createIdGenerator,
@@ -16,6 +17,7 @@ import type { TelemetryOptions } from '../telemetry/telemetry-options';
 import type { Callback } from '../util/callback';
 import { notify } from '../util/notify';
 import { prepareRetries } from '../util/prepare-retries';
+import { prepareLanguageModelCallOptions } from '../prompt/prepare-language-model-call-options';
 import { VERSION } from '../version';
 import type { DecideEndEvent, DecideStartEvent } from './decide-events';
 import type { DecisionModel, DecisionResult } from './decision-result';
@@ -38,6 +40,8 @@ export async function decide<
   model: modelArg,
   state,
   questions,
+  maxOutputTokens,
+  reasoning,
   maxRetries,
   abortSignal,
   headers,
@@ -52,6 +56,10 @@ export async function decide<
   model: DecisionModel;
   state: DecisionState;
   questions: QUESTIONS;
+  /** Maximum output tokens for supported models. Must be an integer >= 1. */
+  maxOutputTokens?: number;
+  /** Reasoning effort for supported models. Language-model adapters default to none. */
+  reasoning?: DecisionCallOptions['reasoning'];
   /** Maximum retries for transient provider failures. Defaults to 2. */
   maxRetries?: number;
   abortSignal?: AbortSignal;
@@ -72,6 +80,7 @@ export async function decide<
 }): Promise<DecisionResult<QUESTIONS>> {
   const model = resolveDecisionModel(modelArg);
 
+  prepareLanguageModelCallOptions({ maxOutputTokens });
   validateDecisionInput({ state, questions });
 
   for (const [questionId, question] of Object.entries(questions)) {
@@ -105,6 +114,8 @@ export async function decide<
     modelId: model.modelId,
     state,
     questions,
+    maxOutputTokens,
+    reasoning,
     maxRetries: resolvedMaxRetries,
     headers,
     providerOptions,
@@ -139,6 +150,8 @@ export async function decide<
           return await model.doDecide({
             state: preparedState,
             questions,
+            maxOutputTokens,
+            reasoning,
             abortSignal,
             headers: withUserAgentSuffix(headers ?? {}, `ai/${VERSION}`),
             providerOptions,

package/src/generate-text/output.ts

@@ -491,7 +491,7 @@ function getArrayLengthValidationError({
 
 /**
  * Output specification for choice generation.
- * When the model generates a text response, it will return a one of the choice options.
+ * When the model generates a text response, it will return one of the choice options.
  *
  * @param options - The available choices.
  * @param name - Optional name of the output that should be generated. Used by some providers for additional LLM guidance, e.g. via tool or schema name.

package/src/generate-text/prune-messages.ts

@@ -163,42 +163,101 @@ export function pruneMessages({
         return message;
       }
 
-      return {
-        ...message,
-        content: message.content.filter(part => {
-          // keep non-tool parts:
-          if (
-            part.type !== 'tool-call' &&
-            part.type !== 'tool-result' &&
-            part.type !== 'tool-approval-request' &&
-            part.type !== 'tool-approval-response'
-          ) {
-            return true;
+      const keepParts = message.content.map(part => {
+        // keep non-tool parts:
+        if (
+          part.type !== 'tool-call' &&
+          part.type !== 'tool-result' &&
+          part.type !== 'tool-approval-request' &&
+          part.type !== 'tool-approval-response'
+        ) {
+          return true;
+        }
+
+        // keep parts that are associated with a tool call or approval that needs to be kept:
+        if (
+          ((part.type === 'tool-call' || part.type === 'tool-result') &&
+            keptToolCallIds.has(part.toolCallId)) ||
+          ((part.type === 'tool-approval-request' ||
+            part.type === 'tool-approval-response') &&
+            keptApprovalIds.has(part.approvalId))
+        ) {
+          return true;
+        }
+
+        // keep parts that are not associated with a tool that should be removed:
+        const partToolName =
+          part.type === 'tool-call' || part.type === 'tool-result'
+            ? part.toolName
+            : approvalIdToToolName.get(part.approvalId);
+
+        return (
+          toolCall.tools != null &&
+          partToolName != null &&
+          !toolCall.tools.includes(partToolName)
+        );
+      });
+
+      // Consecutive reasoning parts can belong to the same provider item.
+      // Remove the whole group when its following content was pruned.
+      if (message.role === 'assistant') {
+        for (
+          let reasoningIndex = 0;
+          reasoningIndex < message.content.length;
+          reasoningIndex++
+        ) {
+          const part = message.content[reasoningIndex];
+          if (part.type !== 'reasoning' && part.type !== 'reasoning-file') {
+            continue;
+          }
+
+          let reasoningEndIndex = reasoningIndex + 1;
+          while (reasoningEndIndex < message.content.length) {
+            const nextPart = message.content[reasoningEndIndex];
+            if (
+              nextPart.type !== 'reasoning' &&
+              nextPart.type !== 'reasoning-file'
+            ) {
+              break;
+            }
+            reasoningEndIndex++;
           }
 
-          // keep parts that are associated with a tool call or approval that needs to be kept:
-          if (
-            ((part.type === 'tool-call' || part.type === 'tool-result') &&
-              keptToolCallIds.has(part.toolCallId)) ||
-            ((part.type === 'tool-approval-request' ||
-              part.type === 'tool-approval-response') &&
-              keptApprovalIds.has(part.approvalId))
-          ) {
-            return true;
+          let followingPartIndex = reasoningEndIndex;
+          let hasFollowingPart = false;
+          let hasKeptFollowingPart = false;
+
+          while (followingPartIndex < message.content.length) {
+            const followingPart = message.content[followingPartIndex];
+            if (
+              followingPart.type === 'reasoning' ||
+              followingPart.type === 'reasoning-file'
+            ) {
+              break;
+            }
+
+            hasFollowingPart = true;
+            hasKeptFollowingPart ||= keepParts[followingPartIndex];
+            followingPartIndex++;
           }
 
-          // keep parts that are not associated with a tool that should be removed:
-          const partToolName =
-            part.type === 'tool-call' || part.type === 'tool-result'
-              ? part.toolName
-              : approvalIdToToolName.get(part.approvalId);
-
-          return (
-            toolCall.tools != null &&
-            partToolName != null &&
-            !toolCall.tools.includes(partToolName)
-          );
-        }),
+          if (hasFollowingPart && !hasKeptFollowingPart) {
+            for (
+              let index = reasoningIndex;
+              index < reasoningEndIndex;
+              index++
+            ) {
+              keepParts[index] = false;
+            }
+          }
+
+          reasoningIndex = followingPartIndex - 1;
+        }
+      }
+
+      return {
+        ...message,
+        content: message.content.filter((_, index) => keepParts[index]),
       } as AssistantModelMessage | ToolModelMessage;
     });
   }

package/src/generate-text/tool-call.ts

@@ -18,7 +18,7 @@ type BaseToolCall = {
  * with an `input` type inferred from that tool's input schema.
  */
 export type StaticToolCall<TOOLS extends ToolSet> = ValueOf<{
-  [NAME in keyof TOOLS]: BaseToolCall & {
+  [NAME in keyof TOOLS]-?: BaseToolCall & {
     toolName: NAME & string;
     input: InferToolInput<TOOLS[NAME]>;
     dynamic?: false | undefined;

package/src/generate-text/tool-error.ts

@@ -4,7 +4,7 @@ import type { ProviderMetadata } from '../types';
 import type { ValueOf } from '../util/value-of';
 
 export type StaticToolError<TOOLS extends ToolSet> = ValueOf<{
-  [NAME in keyof TOOLS]: {
+  [NAME in keyof TOOLS]-?: {
     type: 'tool-error';
     toolCallId: string;
     toolName: NAME & string;

package/src/generate-text/tool-execution-events.ts

@@ -36,7 +36,7 @@ type BaseToolExecutionStartFields = {
  * validated `toolContext` type.
  */
 type StaticToolExecutionStartEvent<TOOLS extends ToolSet> = ValueOf<{
-  [NAME in keyof TOOLS]: BaseToolExecutionStartFields & {
+  [NAME in keyof TOOLS]-?: BaseToolExecutionStartFields & {
     readonly toolCall: Extract<StaticToolCall<TOOLS>, { toolName: NAME }>;
     readonly toolContext: ToolContextFor<TOOLS[NAME]>;
   };
@@ -93,7 +93,7 @@ type BaseToolExecutionEndFields = {
  * corresponding validated `toolContext`, and the tool execution result.
  */
 type StaticToolExecutionEndEvent<TOOLS extends ToolSet> = ValueOf<{
-  [NAME in keyof TOOLS]: BaseToolExecutionEndFields & {
+  [NAME in keyof TOOLS]-?: BaseToolExecutionEndFields & {
     readonly toolCall: Extract<StaticToolCall<TOOLS>, { toolName: NAME }>;
     readonly toolContext: ToolContextFor<TOOLS[NAME]>;
     readonly toolOutput: ToolOutput<TOOLS>;

package/src/generate-text/tool-output-denied.ts

@@ -5,7 +5,7 @@ import type { ToolSet } from '@ai-sdk/provider-utils';
  * Tool output when the tool execution has been denied (for static tools).
  */
 export type StaticToolOutputDenied<TOOLS extends ToolSet> = ValueOf<{
-  [NAME in keyof TOOLS]: {
+  [NAME in keyof TOOLS]-?: {
     type: 'tool-output-denied';
     toolCallId: string;
     toolName: NAME & string;

package/src/generate-text/tool-result.ts

@@ -8,7 +8,7 @@ import type { ProviderMetadata } from '../types';
 import type { ValueOf } from '../../src/util/value-of';
 
 export type StaticToolResult<TOOLS extends ToolSet> = ValueOf<{
-  [NAME in keyof TOOLS]: {
+  [NAME in keyof TOOLS]-?: {
     type: 'tool-result';
     toolCallId: string;
     toolName: NAME & string;

package/src/ui/process-ui-message-stream.ts

@@ -271,6 +271,7 @@ export function processUIMessageStream<UI_MESSAGE extends UIMessage>({
 
             if (part != null) {
               part.state = options.state;
+              anyPart.type = `tool-${options.toolName}`;
               anyPart.input = anyOptions.input;
               anyPart.output = anyOptions.output;
               anyPart.errorText = anyOptions.errorText;