ai 7.0.66 → 7.0.67

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # ai
 
+## 7.0.67
+
+### Patch Changes
+
+- Updated dependencies [a0b1ffc]
+  - @ai-sdk/gateway@4.0.53
+
 ## 7.0.66
 
 ### Patch Changes

package/dist/index.js

@@ -1143,7 +1143,7 @@ import {
 } from "@ai-sdk/provider-utils";
 
 // src/version.ts
-var VERSION = true ? "7.0.66" : "0.0.0-test";
+var VERSION = true ? "7.0.67" : "0.0.0-test";
 
 // src/util/download/download.ts
 var download = async ({

package/dist/internal/index.js

@@ -92,7 +92,7 @@ import {
 } from "@ai-sdk/provider-utils";
 
 // src/version.ts
-var VERSION = true ? "7.0.66" : "0.0.0-test";
+var VERSION = true ? "7.0.67" : "0.0.0-test";
 
 // src/util/download/download.ts
 var download = async ({

package/docs/03-ai-sdk-core/18-code-mode.mdx

@@ -180,6 +180,17 @@ const result = await runCodeMode({
 `runCodeMode` returns the value returned by the program. It uses the same
 sandbox and execution limits as the AI SDK tool.
 
+## Tool Approval
+
+Code mode does not currently integrate with AI SDK tool approval flows. Tool
+calls made by generated code are nested inside the code mode invocation, so
+they cannot pause the generation and surface a tool approval request to your
+application.
+
+Do not expose tools that rely on user approval to code mode. Keep those tools
+directly callable by the model instead. If a nested tool requires approval,
+the call is rejected rather than executed.
+
 ## Execution Limits
 
 Every invocation has limits for runtime, memory, source size, results, tool
@@ -244,6 +255,3 @@ to code mode.
 
 Tool input schemas are validated before their `execute` functions run. Abort
 signals and AI SDK tool execution context are forwarded to nested tool calls.
-
-Code mode does not currently support approval flows for nested tool calls.
-Tools that require approval are rejected instead of being executed.

package/docs/03-ai-sdk-harnesses/02-harness-agent.mdx

@@ -93,6 +93,60 @@ try {
 }
 ```
 
+## Generate Structured Output
+
+Set `output` when constructing `HarnessAgent` to require the same typed output
+on every turn. The agent converts the output specification to JSON Schema for
+the harness adapter, validates the completed response, and returns the parsed
+value through `result.output`.
+
+```ts
+import { HarnessAgent } from '@ai-sdk/harness/agent';
+import { Output } from 'ai';
+import { z } from 'zod';
+
+const agent = new HarnessAgent({
+  harness: claudeCode,
+  sandbox,
+  output: Output.object({
+    schema: z.object({
+      recipe: z.object({
+        name: z.string(),
+        ingredients: z.array(
+          z.object({
+            name: z.string(),
+            amount: z.number(),
+            unit: z.enum(['oz', 'fl oz', 'cup', 'gallon']),
+          }),
+        ),
+        steps: z.array(z.string()),
+      }),
+    }),
+  }),
+});
+
+const session = await agent.createSession();
+try {
+  const result = await agent.generate({
+    session,
+    prompt: 'Generate a lasagna recipe.',
+  });
+  console.dir(result.output, { depth: Infinity });
+} finally {
+  await session.destroy();
+}
+```
+
+With `stream()`, read `partialOutputStream` for incrementally parsed values and
+await `result.output` for the validated final value. Structured data also remains
+available as JSON in the normal text and stream surfaces; adapters do not add it
+to the `finish` part.
+
+Harness structured output requires a schema. Schema-less `Output.json()` and
+adapters or runtime configurations that cannot enforce the schema throw
+`HarnessCapabilityUnsupportedError`; see the
+[adapter capability table](/docs/ai-sdk-harnesses/harness-adapters#adapter-capabilities).
+
 ## Messages and History
 
 A harness session owns its native conversation history. When you pass `messages`
@@ -366,6 +420,7 @@ console.log(preparation.identity);
 - `id`: optional stable agent identifier.
 - `instructions`: instructions appended to the runtime's system or developer
   prompt when supported, or prepended to the first user prompt otherwise.
+- `output`: typed output specification applied to every turn.
 - `stopWhen`: condition(s) for finishing a result slice after a completed
   harness tool step that can continue into another model step.
 - `tools`: AI SDK tools executed by the host when the harness calls them.

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

@@ -30,12 +30,16 @@ The AI SDK includes the following harness adapters:
 
 ## Adapter Capabilities
 
-| Adapter                                                | Runtime location | Custom tools | Custom skills | Built-in tool approval | Built-in tool filtering      |
-| ------------------------------------------------------ | ---------------- | ------------ | ------------- | ---------------------- | ---------------------------- |
-| [Claude Code](/providers/ai-sdk-harnesses/claude-code) | Sandbox bridge   | <Check />    | <Check />     | <Check />              | <Check />                    |
-| [Cline](/providers/ai-sdk-harnesses/cline)             | Host process     | <Check />    | <Check />     | <Check />              | <Check />                    |
-| [Codex](/providers/ai-sdk-harnesses/codex)             | Sandbox bridge   | <Check />    | <Check />     | <Cross />              | <Cross />                    |
-| [Deep Agents](/providers/ai-sdk-harnesses/deepagents)  | Sandbox bridge   | <Check />    | <Check />     | <Check />              | <Check /> via auto-rejection |
-| [Grok Build](/providers/ai-sdk-harnesses/grok-build)   | Sandbox via ACP  | <Check />    | <Check />     | <Check />              | <Cross />                    |
-| [OpenCode](/providers/ai-sdk-harnesses/opencode)       | Sandbox bridge   | <Check />    | <Check />     | <Check />              | <Check /> via auto-rejection |
-| [Pi](/providers/ai-sdk-harnesses/pi)                   | Host process     | <Check />    | <Check />     | <Check />              | <Check />                    |
+| Adapter                                                | Runtime location | Custom tools | Custom skills | Structured output | Built-in tool approval | Built-in tool filtering      |
+| ------------------------------------------------------ | ---------------- | ------------ | ------------- | ----------------- | ---------------------- | ---------------------------- |
+| [Claude Code](/providers/ai-sdk-harnesses/claude-code) | Sandbox bridge   | <Check />    | <Check />     | <Check />         | <Check />              | <Check />                    |
+| [Cline](/providers/ai-sdk-harnesses/cline)             | Host process     | <Check />    | <Check />     | <Check />         | <Check />              | <Check />                    |
+| [Codex](/providers/ai-sdk-harnesses/codex)             | Sandbox bridge   | <Check />    | <Check />     | <Check />         | <Cross />              | <Cross />                    |
+| [Deep Agents](/providers/ai-sdk-harnesses/deepagents)  | Sandbox bridge   | <Check />    | <Check />     | <Check />         | <Check />              | <Check /> via auto-rejection |
+| [Grok Build](/providers/ai-sdk-harnesses/grok-build)   | Sandbox via ACP  | <Check />    | <Check />     | <Check />         | <Check />              | <Cross />                    |
+| [OpenCode](/providers/ai-sdk-harnesses/opencode)       | Sandbox bridge   | <Check />    | <Check />     | <Check />         | <Check />              | <Check /> via auto-rejection |
+| [Pi](/providers/ai-sdk-harnesses/pi)                   | Host process     | <Check />    | <Check />     | <Cross />         | <Check />              | <Check />                    |
+
+Generic ACP profiles do not support structured output unless they configure an
+implementation-specific prompt metadata mapping; Grok Build includes the
+required mapping, while Codex ACP does not expose one.

package/docs/07-reference/04-ai-sdk-workflow/01-workflow-agent.mdx

@@ -404,7 +404,8 @@ To see `WorkflowAgent` in action, check out [these examples](#examples).
       name: 'maxRetries',
       type: 'number',
       isOptional: true,
-      description: 'How many times to retry on failure. Default: 2.',
+      description:
+        'How many times to retry retryable model-call failures. Set to 0 to disable retries. Retry-After response headers are respected, and durable workflow step retries are not stacked. Default: 2.',
     },
     {
       name: 'headers',
@@ -678,6 +679,12 @@ Returns a `Promise<WorkflowAgentStreamResult>` with the following properties:
       description:
         'Tool results from the last step. Only includes results for tools that were executed.',
     },
+    {
+      name: 'error',
+      type: 'unknown | undefined',
+      description:
+        "The original value from a model stream error part. The property is present when an error part was emitted, even if its value is undefined; use `'error' in result` to distinguish that case.",
+    },
     {
       name: 'output',
       type: 'OUTPUT',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ai",
-  "version": "7.0.66",
+  "version": "7.0.67",
   "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,7 +42,7 @@
     }
   },
   "dependencies": {
-    "@ai-sdk/gateway": "4.0.52",
+    "@ai-sdk/gateway": "4.0.53",
     "@ai-sdk/provider": "4.0.7",
     "@ai-sdk/provider-utils": "5.0.27"
   },