ai 7.0.3 → 7.0.5

package/dist/internal/index.js

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

package/docs/03-ai-sdk-core/16-mcp-tools.mdx

@@ -360,6 +360,52 @@ Resource templates are dynamic URI patterns that allow flexible queries. List al
 const templates = await mcpClient.listResourceTemplates();
 ```
 
+## Using MCP Completions
+
+MCP servers can provide autocompletion suggestions for prompt arguments and
+resource template variables when they advertise the `completions` capability.
+Use `complete` to ask the server for suggestions based on the current partial
+argument value:
+
+```typescript
+const completion = await mcpClient.complete({
+  ref: {
+    type: 'ref/resource',
+    uri: 'file:///{path}',
+  },
+  argument: {
+    name: 'path',
+    value: 'doc',
+  },
+});
+
+console.log(completion.completion.values);
+```
+
+For resource templates or prompts with multiple arguments, pass already resolved
+values through `context.arguments`:
+
+```typescript
+const completion = await mcpClient.complete({
+  ref: {
+    type: 'ref/resource',
+    uri: 'kubernetes://namespaced/{plural}/{namespace}',
+  },
+  argument: {
+    name: 'namespace',
+    value: 'auth',
+  },
+  context: {
+    arguments: {
+      plural: 'deployments',
+    },
+  },
+});
+```
+
+If the connected server does not advertise `capabilities.completions`, the
+client throws an `MCPClientError`.
+
 ## Using MCP Prompts
 
 <Note type="warning">

package/docs/07-reference/01-ai-sdk-core/23-create-mcp-client.mdx

@@ -10,6 +10,7 @@ Creates a lightweight Model Context Protocol (MCP) client that connects to an MC
 - **Tools**: Automatic conversion between MCP tools and AI SDK tools
 - **Resources**: Methods to list, read, and discover resource templates from MCP servers
 - **Prompts**: Methods to list available prompts and retrieve prompt messages
+- **Completions**: Methods to request autocompletion suggestions for prompt arguments and resource template variables
 - **Elicitation**: Support for handling server requests for additional input during tool execution
 
 It currently does not support accepting notifications from an MCP server, and custom configuration of the client.
@@ -440,6 +441,47 @@ Returns a Promise that resolves to an `MCPClient` with the following properties
         },
       ],
     },
+    {
+      name: 'complete',
+      type: `async (args: CompleteRequestParams & {
+        options?: RequestOptions;
+      }) => Promise<CompleteResult>`,
+      description:
+        'Requests autocompletion suggestions for a prompt argument or resource template variable. The server must advertise the completions capability.',
+      properties: [
+        {
+          type: 'args',
+          parameters: [
+            {
+              name: 'ref',
+              type: "{ type: 'ref/prompt'; name: string } | { type: 'ref/resource'; uri: string }",
+              description:
+                'Reference to the prompt or resource template being completed.',
+            },
+            {
+              name: 'argument',
+              type: '{ name: string; value: string }',
+              description:
+                'Argument name and current partial value to complete.',
+            },
+            {
+              name: 'context',
+              type: '{ arguments: Record<string, string> }',
+              isOptional: true,
+              description:
+                'Previously resolved argument values used to provide context for multi-argument prompts or resource templates.',
+            },
+            {
+              name: 'options',
+              type: 'RequestOptions',
+              isOptional: true,
+              description:
+                'Optional request options including signal and timeout.',
+            },
+          ],
+        },
+      ],
+    },
     {
       name: 'experimental_listPrompts',
       type: `async (options?: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ai",
-  "version": "7.0.3",
+  "version": "7.0.5",
   "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,9 +42,9 @@
     }
   },
   "dependencies": {
-    "@ai-sdk/gateway": "4.0.3",
+    "@ai-sdk/gateway": "4.0.4",
     "@ai-sdk/provider": "4.0.0",
-    "@ai-sdk/provider-utils": "5.0.0"
+    "@ai-sdk/provider-utils": "5.0.1"
   },
   "devDependencies": {
     "@edge-runtime/vm": "^5.0.0",

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

@@ -100,6 +100,44 @@ export function pruneMessages({
       }
     }
 
+    // Build global maps from tool call id and approval id to tool name.
+    // These must be global (not per-message) because a `tool-approval-response`
+    // lives in a separate `tool` message from its `tool-approval-request`
+    // (assistant message), so the tool name of a response can only be resolved
+    // by looking across messages. Resolving names per-message left responses
+    // unresolved, which caused them to be kept while their request was pruned,
+    // producing orphaned approval responses.
+    const toolCallIdToToolName = new Map<string, string>();
+    for (const message of messages) {
+      if (
+        (message.role === 'assistant' || message.role === 'tool') &&
+        typeof message.content !== 'string'
+      ) {
+        for (const part of message.content) {
+          if (part.type === 'tool-call' || part.type === 'tool-result') {
+            toolCallIdToToolName.set(part.toolCallId, part.toolName);
+          }
+        }
+      }
+    }
+
+    const approvalIdToToolName = new Map<string, string>();
+    for (const message of messages) {
+      if (
+        (message.role === 'assistant' || message.role === 'tool') &&
+        typeof message.content !== 'string'
+      ) {
+        for (const part of message.content) {
+          if (part.type === 'tool-approval-request') {
+            const toolName = toolCallIdToToolName.get(part.toolCallId);
+            if (toolName != null) {
+              approvalIdToToolName.set(part.approvalId, toolName);
+            }
+          }
+        }
+      }
+    }
+
     messages = messages.map((message, messageIndex) => {
       if (
         (message.role !== 'assistant' && message.role !== 'tool') ||
@@ -110,9 +148,6 @@ export function pruneMessages({
         return message;
       }
 
-      const toolCallIdToToolName: Record<string, string> = {};
-      const approvalIdToToolName: Record<string, string> = {};
-
       return {
         ...message,
         content: message.content.filter(part => {
@@ -126,14 +161,6 @@ export function pruneMessages({
             return true;
           }
 
-          // track tool calls and approvals:
-          if (part.type === 'tool-call') {
-            toolCallIdToToolName[part.toolCallId] = part.toolName;
-          } else if (part.type === 'tool-approval-request') {
-            approvalIdToToolName[part.approvalId] =
-              toolCallIdToToolName[part.toolCallId];
-          }
-
           // 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') &&
@@ -146,13 +173,15 @@ export function pruneMessages({
           }
 
           // 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 &&
-            !toolCall.tools.includes(
-              part.type === 'tool-call' || part.type === 'tool-result'
-                ? part.toolName
-                : approvalIdToToolName[part.approvalId],
-            )
+            partToolName != null &&
+            !toolCall.tools.includes(partToolName)
           );
         }),
       } as AssistantModelMessage | ToolModelMessage;