@assistant-ui/mcp-docs-server 0.1.38 → 0.1.39

package/.docs/raw/docs/integrations/frameworks/mastra/overview.mdx

@@ -9,7 +9,7 @@ import { VercelIcon } from "@/components/icons/vercel";
 [Mastra](https://mastra.ai/) is an open-source TypeScript agent framework. It provides primitives for AI applications: agents with memory and tool calling, deterministic LLM workflows, RAG, model routing, workflow graphs, and automated evals.
 
 <Callout type="info">
-This is an integration guide, not a runtime adapter. assistant-ui does not ship a `@assistant-ui/react-mastra` package. You wire up Mastra through the standard [AI SDK runtime](/docs/runtimes/ai-sdk/v6) by routing your API endpoint through Mastra's agent stream.
+This is an integration guide, not a runtime adapter. assistant-ui does not ship a `@assistant-ui/react-mastra` package. You wire up Mastra through the standard [AI SDK runtime](/docs/runtimes/ai-sdk/v7) by routing your API endpoint through Mastra's agent stream.
 </Callout>
 
 ## Pick a pattern
@@ -19,7 +19,7 @@ This is an integration guide, not a runtime adapter. assistant-ui does not ship
 | [Full-stack](/docs/integrations/frameworks/mastra/full-stack) | One Next.js app: API routes call Mastra in-process. Simpler deployment, single repo. |
 | [Separate server](/docs/integrations/frameworks/mastra/separate-server) | Mastra runs as its own service; the Next.js frontend hits its API. Independent scaling, clearer separation of concerns. |
 
-Both use the same client-side `useChatRuntime` from [`@assistant-ui/react-ai-sdk`](/docs/runtimes/ai-sdk/v6). The only difference is where the Mastra agent lives.
+Both use the same client-side `useChatRuntime` from [`@assistant-ui/react-ai-sdk`](/docs/runtimes/ai-sdk/v7). The only difference is where the Mastra agent lives.
 
 ## Architecture
 
@@ -52,6 +52,6 @@ Shared adapters (attachments, speech, feedback, history) work the same way descr
     icon={<VercelIcon width={20} height={20} />}
     title="AI SDK runtime"
     description="The runtime that handles the client side of this integration."
-    href="/docs/runtimes/ai-sdk/v6"
+    href="/docs/runtimes/ai-sdk/v7"
   />
 </Cards>

package/.docs/raw/docs/integrations/frameworks/mastra/separate-server.mdx

@@ -196,6 +196,6 @@ Open `http://localhost:3000`, send a message, and confirm:
     icon={<VercelIcon width={20} height={20} />}
     title="AI SDK runtime"
     description="The runtime that handles the client side of this integration."
-    href="/docs/runtimes/ai-sdk/v6"
+    href="/docs/runtimes/ai-sdk/v7"
   />
 </Cards>

package/.docs/raw/docs/integrations/gateways/index.mdx

@@ -8,7 +8,7 @@ import { VercelIcon } from "@/components/icons/vercel";
 
 LLM gateways sit between your route handler and the upstream provider. They give you a single endpoint that fronts many providers, plus features like multi-provider fallback, prompt caching, and BYOK (bring-your-own-key) flows. Most are OpenAI API-compatible, so the integration is a `baseURL` swap on `createOpenAI` from `@ai-sdk/openai`.
 
-For pure observability (proxy that logs every call) see [Helicone](/docs/integrations/observability/helicone). The gateways here overlap in spirit but are positioned around routing rather than logging.
+For pure observability (proxy that logs every call) see [Helicone](/docs/integrations/observability/helicone). The gateways here overlap in spirit but are positioned around routing rather than logging. For local personal projects there is also a keyless option in the same `baseURL`-swap shape: a local OAuth proxy billed to your ChatGPT subscription; see [ChatGPT Subscription](/docs/guides/chatgpt-subscription).
 
 ## Compare
 
@@ -157,6 +157,6 @@ When to pick: self-host requirement, BYOK metering for end-users, or unified bil
     icon={<VercelIcon width={20} height={20} />}
     title="AI SDK runtime"
     description="The runtime that ferries gateway responses to the chat UI."
-    href="/docs/runtimes/ai-sdk/v6"
+    href="/docs/runtimes/ai-sdk/v7"
   />
 </Cards>

package/.docs/raw/docs/integrations/observability/helicone.mdx

@@ -124,6 +124,6 @@ If nothing appears, check the request in your network tab. The host should be `o
     icon={<VercelIcon width={20} height={20} />}
     title="AI SDK runtime"
     description="The most common pairing: AI SDK route handler proxied through Helicone."
-    href="/docs/runtimes/ai-sdk/v6"
+    href="/docs/runtimes/ai-sdk/v7"
   />
 </Cards>

package/.docs/raw/docs/integrations/observability/langfuse.mdx

@@ -156,6 +156,6 @@ If nothing appears, check the server logs for OTel errors and confirm `LANGFUSE_
     icon={<VercelIcon width={20} height={20} />}
     title="AI SDK runtime"
     description="The runtime that emits the telemetry Langfuse consumes."
-    href="/docs/runtimes/ai-sdk/v6"
+    href="/docs/runtimes/ai-sdk/v7"
   />
 </Cards>

package/.docs/raw/docs/integrations/observability/langsmith.mdx

@@ -146,6 +146,6 @@ Send a message. The trace should appear in your LangSmith project within seconds
     icon={<VercelIcon width={20} height={20} />}
     title="AI SDK runtime"
     description="The runtime that ferries traces from the route to the chat UI."
-    href="/docs/runtimes/ai-sdk/v6"
+    href="/docs/runtimes/ai-sdk/v7"
   />
 </Cards>

package/.docs/raw/docs/migrations/index.mdx

@@ -0,0 +1,50 @@
+---
+title: Migration Guides
+description: Upgrade assistant-ui versions and migrate deprecated APIs and integrations.
+---
+
+Use these guides when upgrading assistant-ui or moving from APIs that have been deprecated or replaced.
+
+## Version upgrades
+
+<Cards>
+  <Card title="Migration to v0.14" href="/docs/migrations/v0-14">
+    Replace APIs removed after v0.11 and v0.12, and migrate primitive
+    `components` props to children render functions.
+  </Card>
+  <Card title="Migration to v0.12" href="/docs/migrations/v0-12">
+    Move from individual context hooks to the unified state API.
+  </Card>
+  <Card title="Migration to v0.11" href="/docs/migrations/v0-11">
+    Update code affected by the `ContentPart` to `MessagePart` rename.
+  </Card>
+</Cards>
+
+## APIs and integrations
+
+<Cards>
+  <Card title="Migrating Tools to Toolkits" href="/docs/migrations/toolkit-tools">
+    Move legacy tool and tool UI registrations to the toolkit API.
+  </Card>
+  <Card
+    title="Migrating to react-langgraph v0.7"
+    href="/docs/migrations/react-langgraph-v0-7"
+  >
+    Upgrade to the simplified LangGraph integration API.
+  </Card>
+  <Card
+    title="Using old React versions"
+    href="/docs/migrations/react-compatibility"
+  >
+    Review compatibility notes for React 18 and React 19.
+  </Card>
+</Cards>
+
+## Stability
+
+<Cards>
+  <Card title="Deprecation Policy" href="/docs/migrations/deprecation-policy">
+    Review stability guarantees and deprecation timelines for assistant-ui
+    features.
+  </Card>
+</Cards>

package/.docs/raw/docs/migrations/toolkit-tools.mdx

@@ -32,7 +32,7 @@ const WeatherTool = makeAssistantTool({
 });
 
 export function App() {
-  const runtime = useChatRuntime({ api: "/api/chat" });
+  const runtime = useChatRuntime();
 
   return (
     <AssistantRuntimeProvider runtime={runtime}>
@@ -80,7 +80,7 @@ import { useChatRuntime } from "@assistant-ui/react-ai-sdk";
 import toolkit from "./toolkit";
 
 export function App() {
-  const runtime = useChatRuntime({ api: "/api/chat" });
+  const runtime = useChatRuntime();
   const aui = useAui({
     tools: Tools({ toolkit }),
   });
@@ -93,6 +93,8 @@ export function App() {
 }
 ```
 
+`useChatRuntime()` targets `/api/chat` by default. To point at a different endpoint or customize requests, see [Custom transport](/docs/runtimes/ai-sdk/v7#custom-transport).
+
 ## Mechanical Steps
 
 1. Create a `Toolkit` object.

package/.docs/raw/docs/primitives/chain-of-thought.mdx

@@ -5,6 +5,8 @@ platforms: ["react"]
 ---
 
 import { ChainOfThoughtPrimitiveSample } from "@/components/docs/samples/chain-of-thought-primitive";
+import { ChainOfThoughtPrimitiveSample as ChainOfThoughtPrimitiveSampleRadix } from "@/components/docs/samples/chain-of-thought-primitive.radix";
+import { Flavored } from "@/components/docs/contexts/flavor.server";
 import {
   ChainOfThoughtPrimitive as ChainOfThoughtPrimitiveDocs,
   MessagePrimitive as MessagePrimitiveDocs,
@@ -18,7 +20,10 @@ For new grouped reasoning/tool-call UI, use `MessagePrimitive.GroupedParts`. `Ch
 
 <Tabs items={["Preview", "Code"]}>
   <Tab>
-    <ChainOfThoughtPrimitiveSample />
+    <Flavored
+      base={<ChainOfThoughtPrimitiveSample />}
+      radix={<ChainOfThoughtPrimitiveSampleRadix />}
+    />
   </Tab>
   <Tab>
 ```tsx

package/.docs/raw/docs/primitives/composer.mdx

@@ -165,6 +165,22 @@ Form container for message composition. Renders a `<form>` element unless `asChi
 </ComposerPrimitive.Root>
 ```
 
+#### Compact Mode
+
+Pass `compact` to opt into compact detection. While the input holds at most a single line of text and the composer has no attachments, quote, queued messages, or active dictation, the root renders a `data-compact` attribute. The prop only exposes this attribute for styling — it does not change the layout by itself. Target it with CSS to collapse the composer into a single row:
+
+```tsx
+<ComposerPrimitive.Root
+  compact
+  className="group/composer flex flex-col data-[compact]:flex-row data-[compact]:items-center"
+>
+  <ComposerPrimitive.Input placeholder="Ask anything..." />
+  <ComposerPrimitive.Send>Send</ComposerPrimitive.Send>
+</ComposerPrimitive.Root>
+```
+
+Once the text wraps onto a second line, the composer expands and stays expanded until the input is cleared, so the layout doesn't oscillate at the wrap boundary.
+
 ### Input
 
 Text input with keyboard shortcuts. Renders a `<textarea>` element unless `asChild` is set.

package/.docs/raw/docs/primitives/selection-toolbar.mdx

@@ -63,6 +63,31 @@ The toolbar only appears when the selection is entirely within a single message.
 
 `Root` returns `null` when there is no valid selection (collapsed selection, empty text, or no single-message match).
 
+### Quote Regions
+
+By default, any selected text inside a message can be quoted. For rich messages with tool cards, attachments, or custom controls, add `data-aui-quote-selectable` to the element that contains the message text. Once a message has a quote-selectable region, selections must stay inside the same marked region for the toolbar to appear.
+
+```tsx
+<MessagePrimitive.Root>
+  <div data-aui-quote-selectable="">
+    <MessagePrimitive.Parts />
+  </div>
+  <ToolCard />
+</MessagePrimitive.Root>
+```
+
+Set `data-aui-quote-selectable="false"` to exclude an element instead: on the message root it disables quoting for the entire message, and inside a quotable region it carves that subtree out. The nearest marker wins, and any value other than `"false"` (including empty) marks a quotable region.
+
+Apps know the message role at render time, so a role gate is a conditional attribute:
+
+```tsx
+const UserMessage = () => (
+  <MessagePrimitive.Root data-aui-quote-selectable="false">
+    <MessagePrimitive.Parts />
+  </MessagePrimitive.Root>
+);
+```
+
 ### Quote Action
 
 The `Quote` button does two things on click:

package/.docs/raw/docs/react-native/primitives.mdx

@@ -362,6 +362,29 @@ Renders message content parts using render-prop functions instead of the compone
 | `renderFile` | `(props: { part, index }) => ReactElement` | Renderer for file parts |
 | `renderData` | `(props: { part, index }) => ReactElement` | Fallback renderer for data parts not handled by registered data UIs |
 
+#### Rendering Markdown
+
+`MessagePrimitive.Content` renders text parts with React Native's `<Text>` by default, so markdown syntax is displayed as plain text. To render markdown, install a React Native markdown renderer and pass it through `renderText`:
+
+<InstallCommand npm={["react-native-markdown-display"]} />
+
+```tsx
+import Markdown from "react-native-markdown-display";
+import { MessagePrimitive } from "@assistant-ui/react-native";
+
+const AssistantMessage = () => {
+  return (
+    <MessagePrimitive.Root>
+      <MessagePrimitive.Content
+        renderText={({ part }) => (
+          <Markdown>{part.text}</Markdown>
+        )}
+      />
+    </MessagePrimitive.Root>
+  );
+};
+```
+
 ### MessagePrimitive.Parts
 
 Renders message content parts via a `components` prop. Tool call and data parts automatically render registered toolkit renderers and data UIs (via `useAssistantDataUI`), falling back to components provided here. A default `Text` component using React Native's `<Text>` is provided out of the box.

package/.docs/raw/docs/runtimes/ag-ui/agent-state.mdx

@@ -0,0 +1,124 @@
+---
+title: Agent state
+description: Read and optimistically update agent-owned state with useAgUiState and useAgUiSetState over AG-UI.
+---
+
+`useAgUiState` mirrors the state your AG-UI agent owns. It updates live while the agent runs. `useAgUiSetState` lets you apply optimistic local updates that are sent with the next run.
+
+## Basic usage
+
+```tsx
+import { useAgUiState, useAgUiSetState } from "@assistant-ui/react-ag-ui";
+import { useAuiState } from "@assistant-ui/react";
+
+type ResearchState = {
+  topic: string;
+  sources: string[];
+};
+
+const state = useAgUiState<ResearchState>();
+// state: ResearchState | undefined  (latest agent state; updates live while the agent runs)
+
+const setState = useAgUiSetState<ResearchState>();
+// setState(next | (prev) => next)   (optimistic local update; sent with the NEXT run)
+
+const isRunning = useAuiState((s) => s.thread.isRunning);
+// isRunning: boolean                (whether the thread is currently running)
+```
+
+## Example
+
+Render agent state beside the chat and push an optimistic update from a control in your UI:
+
+```tsx
+"use client";
+
+import { useAgUiState, useAgUiSetState } from "@assistant-ui/react-ag-ui";
+import { useAuiState } from "@assistant-ui/react";
+import { Thread } from "@/components/assistant-ui/thread";
+
+type ResearchState = {
+  topic: string;
+  sources: string[];
+};
+
+export function ResearchAssistant() {
+  const state = useAgUiState<ResearchState>();
+  const setState = useAgUiSetState<ResearchState>();
+  const isRunning = useAuiState((s) => s.thread.isRunning);
+
+  return (
+    <div className="flex h-full">
+      <aside className="w-72 border-r p-4">
+        <h2>Research state</h2>
+        {state ? (
+          <ul>
+            <li>Topic: {state.topic}</li>
+            <li>Sources: {state.sources.join(", ") || "none"}</li>
+          </ul>
+        ) : (
+          <p>No agent state yet.</p>
+        )}
+        <button
+          type="button"
+          disabled={isRunning}
+          onClick={() =>
+            setState((prev) => ({
+              topic: prev?.topic ?? "market analysis",
+              sources: [...(prev?.sources ?? []), "sec-filings"],
+            }))
+          }
+        >
+          Prefer SEC filings
+        </button>
+        {isRunning && <p>Agent is running…</p>}
+      </aside>
+      <main className="flex-1">
+        <Thread />
+      </main>
+    </div>
+  );
+}
+```
+
+The panel re-renders as `STATE_SNAPSHOT` and `STATE_DELTA` events arrive. The button updates the local snapshot immediately; that value is included as the `state` field of the next run input.
+
+## How state is synced
+
+The AG-UI protocol delivers agent state on the wire:
+
+- `STATE_SNAPSHOT` replaces the full client-side snapshot.
+- `STATE_DELTA` applies a JSON Patch to the current snapshot.
+
+The runtime applies both client-side, so `useAgUiState` always reflects the latest merged snapshot. Calling the setter from `useAgUiSetState` updates that same local snapshot. On the next run, the runtime automatically includes it as the `state` field of the run input.
+
+This works with any AG-UI agent (Mastra, Pydantic AI, CrewAI, LangGraph via AG-UI adapters, and other AG-UI-compliant servers).
+
+## Write-back timing
+
+`useAgUiSetState` is optimistic and local first. The value reaches the agent only when the next run starts. It is not a live channel into a run that is already in progress. Use it to stage preferences, filters, or other agent-owned fields that the next turn should see.
+
+## Relationship to other state
+
+Keep the three state layers distinct:
+
+- **Your app state** stays yours (React state, URL, a store). assistant-ui does not own it.
+- **`useAuiState`** reads assistant-ui's client state (messages, composer, thread status).
+- **`useAgUiState` / `useAgUiSetState`** mirror state the **agent** owns, synced over the AG-UI wire via snapshots and deltas.
+
+Use `useAgUiState` and `useAgUiSetState` for fields your agent maintains as shared state on the protocol. Use `useAuiState` for UI that depends on the chat thread itself. Use your own state for everything else.
+
+## Next
+
+<Cards>
+  <Card
+    title="Runtime options"
+    description="useAgUiRuntime options, adapters, supported events."
+    href="/docs/runtimes/ag-ui/runtime-options"
+  />
+  <Card
+    title="Quickstart"
+    description="Minimal HttpAgent + useAgUiRuntime setup."
+    href="/docs/runtimes/ag-ui/quickstart"
+  />
+</Cards>

package/.docs/raw/docs/runtimes/ag-ui/runtime-options.mdx

@@ -14,6 +14,7 @@ Reference for the runtime's API surface. Start with [quickstart](/docs/runtimes/
 | `agent` | `HttpAgent` | An AG-UI client agent (from `@ag-ui/client`). Required. |
 | `logger` | `Partial<Logger>` | Optional logger overrides. The runtime logs event-parser warnings and run lifecycle events. |
 | `showThinking` | `boolean` | Whether to render `THINKING_*` and `REASONING_*` events as visible reasoning. Defaults to `true`. |
+| `autoCancelPendingToolCalls` | `boolean` | Cancel unresolved client-side tool calls automatically when the user sends, edits, or reloads a message. Defaults to `true`. See [below](#auto-cancelling-pending-tool-calls). |
 | `onError` | `(e: Error) => void` | Error callback fired on `RUN_ERROR` events and protocol errors. |
 | `onCancel` | `() => void` | Cancellation callback fired when the user cancels a run. |
 | `adapters` | `UseAgUiRuntimeAdapters` | Standard adapter slots (see below). |
@@ -137,7 +138,9 @@ await runtime.unstable_submitInterruptResponses(
 
 ### Steering away from an interrupt
 
-When the user ignores the interrupt UI and just sends a new message, use the `useAgUiSteerAway` hook. Every open interrupt defaults to `status: "cancelled"`, the new message is appended, and the run resumes with `resume: ResumeEntry[]` on the wire. With no pending interrupts it behaves like a normal append.
+When the user ignores the interrupt UI and just sends a new message, use the `useAgUiSteerAway` hook. Every open interrupt defaults to `status: "cancelled"`, the new message is appended, and the run resumes with `resume: ResumeEntry[]` on the wire.
+
+The same hook also steers away from pending client-side tool calls. When the head assistant message is in `requires-action` with `reason: "tool-calls"` (frontend tools awaiting a result) and the user sends a new message, every unresolved tool call is cancelled with an error result, the message is completed, and a single fresh run starts with those cancellations in its history. Passing `responses` in this case throws, since responses only address interrupts. With nothing pending, `steerAway` behaves like a normal append.
 
 ```tsx
 const steerAway = useAgUiSteerAway();
@@ -154,6 +157,12 @@ await steerAway("continue without the file", [
 ]);
 ```
 
+### Auto-cancelling pending tool calls
+
+By default the runtime does the tool-call half of this automatically: when client-side tool calls are still unresolved and the user sends a new message, edits an earlier one, or reloads, every unresolved tool call receives the same cancellation error result, the assistant message is completed, and the run proceeds with those cancellations in its history. Set `autoCancelPendingToolCalls: false` to opt out, in which case pending tool calls stay unresolved on a plain send and [steering away](#steering-away-from-an-interrupt) remains the explicit way to cancel them.
+
+Pending interrupts are never auto-cancelled: sending while an interrupt is open still throws, and the interrupt must be answered with `useAgUiSubmitInterruptResponses` or discarded with `useAgUiSteerAway`.
+
 ## Supported events
 
 The runtime parses the AG-UI event stream and maps each event type to assistant-ui state.

package/.docs/raw/docs/runtimes/ai-sdk/overview.mdx

@@ -11,16 +11,19 @@ import { VercelIcon } from "@/components/icons/vercel";
 
 | AI SDK | Runtime package | Docs |
 | --- | --- | --- |
-| `ai@^6` + `@ai-sdk/react@^3` | `@assistant-ui/react-ai-sdk` (latest) | [v6 (current)](/docs/runtimes/ai-sdk/v6) |
+| `ai@^7` + `@ai-sdk/react@^4` | `@assistant-ui/react-ai-sdk` (latest) | [v7 (current)](/docs/runtimes/ai-sdk/v7) |
+| `ai@^6` + `@ai-sdk/react@^3` | `@assistant-ui/react-ai-sdk@1.x` | [v6 (legacy)](/docs/runtimes/ai-sdk/v6-legacy) |
 | `ai@^5` + `@ai-sdk/react@^2` | `@assistant-ui/react-ai-sdk@0.x` | [v5 (legacy)](/docs/runtimes/ai-sdk/v5-legacy) |
 | `ai@^4` | `@assistant-ui/react-data-stream` | [v4 (legacy)](/docs/runtimes/ai-sdk/v4-legacy) |
 
-New projects should target v6. v5 and v4 are documented for projects that have not migrated yet; both have known compatibility gaps and receive no new features.
+New projects should target v7. v6, v5, and v4 are documented for projects that have not migrated yet; all have known compatibility gaps and receive no new features.
 
 ## Architecture
 
 `@assistant-ui/react-ai-sdk` is layered on `ExternalStoreRuntime` (see [architecture](/docs/runtimes/concepts/architecture)). Features that ship as runtime adapters work the same way they do everywhere else; see [adapters](/docs/runtimes/concepts/adapters).
 
+For reload-safe streaming (persist an in-flight response so the client can reconnect), see [Resumable Streams](/docs/guides/resumable-streams).
+
 ## Choosing useChatRuntime vs useAISDKRuntime
 
 Both ship in the same package.
@@ -33,9 +36,15 @@ Both ship in the same package.
 <Cards>
   <Card
     icon={<VercelIcon width={20} height={20} />}
-    title="v6 (current)"
+    title="v7 (current)"
     description="Quickstart, frontend tools, attachments, quotes, history, multi-step, useAISDKRuntime."
-    href="/docs/runtimes/ai-sdk/v6"
+    href="/docs/runtimes/ai-sdk/v7"
+  />
+  <Card
+    icon={<VercelIcon width={20} height={20} />}
+    title="v6 (legacy)"
+    description="Reference for projects still on AI SDK v6."
+    href="/docs/runtimes/ai-sdk/v6-legacy"
   />
   <Card
     icon={<VercelIcon width={20} height={20} />}

package/.docs/raw/docs/runtimes/ai-sdk/v4-legacy.mdx

@@ -1,12 +1,12 @@
 ---
 title: AI SDK v4 (legacy)
-description: Reference for projects still on AI SDK v4. New projects should use v6.
+description: Reference for projects still on AI SDK v4. New projects should use v7.
 ---
 
 import { VercelIcon } from "@/components/icons/vercel";
 
 <Callout type="warn">
-AI SDK v4 is a legacy version. New projects should use [AI SDK v6](/docs/runtimes/ai-sdk/v6). v4 integrations use the older `@assistant-ui/react-data-stream` package, not `@assistant-ui/react-ai-sdk`.
+AI SDK v4 is a legacy version. New projects should use [AI SDK v7](/docs/runtimes/ai-sdk/v7). v4 integrations use the older `@assistant-ui/react-data-stream` package, not `@assistant-ui/react-ai-sdk`.
 </Callout>
 
 ## Why legacy
@@ -53,10 +53,7 @@ import { useDataStreamRuntime } from "@assistant-ui/react-data-stream";
 import { Thread } from "@/components/assistant-ui/thread";
 
 export default function Home() {
-  const runtime = useDataStreamRuntime({
-    api: "/api/chat",
-    protocol: "data-stream",
-  });
+  const runtime = useDataStreamRuntime({ api: "/api/chat" });
   return (
     <AssistantRuntimeProvider runtime={runtime}>
       <div className="h-full">
@@ -67,7 +64,10 @@ export default function Home() {
 }
 ```
 
-AI SDK v4's `toDataStreamResponse()` emits the data stream wire format, so `protocol: "data-stream"` is required to pair with it; the default `protocol: "ui-message-stream"` expects the SSE format introduced in AI SDK v6.
+AI SDK v4's `toDataStreamResponse()` emits the data stream wire format with the
+`x-vercel-ai-data-stream: v1` response header, so `useDataStreamRuntime`
+detects it automatically. If a custom proxy strips or hides that header, pass
+`protocol: "data-stream"` explicitly.
 
 </Step>
 </Steps>
@@ -85,12 +85,12 @@ AI SDK v4's `toDataStreamResponse()` emits the data stream wire format, so `prot
 | Tool schema | `parameters: z.object({...})` | `inputSchema: zodSchema(z.object({...}))` |
 | Message type | (untyped) | `UIMessage` |
 
-## Migration to v6
+## Migration to v7
 
 When you are ready to upgrade:
 
 1. Swap `@assistant-ui/react-data-stream` for `@assistant-ui/react-ai-sdk`.
-2. Update your backend to AI SDK v6's `streamText` (see [v6 docs](/docs/runtimes/ai-sdk/v6)).
+2. Update your backend to the current AI SDK's `streamText` (see [v7 docs](/docs/runtimes/ai-sdk/v7)).
 3. Switch the runtime hook from `useDataStreamRuntime` to `useChatRuntime`.
 
 AI SDK provides codemods at [ai-sdk.dev/docs/migration-guides](https://ai-sdk.dev/docs/migration-guides) that handle the package-side rewrites.
@@ -104,9 +104,9 @@ An older release line of `@assistant-ui/react-ai-sdk` (0.1.10) supported AI SDK
 <Cards>
   <Card
     icon={<VercelIcon width={20} height={20} />}
-    title="AI SDK v6"
+    title="AI SDK v7"
     description="Current integration; what new projects should target."
-    href="/docs/runtimes/ai-sdk/v6"
+    href="/docs/runtimes/ai-sdk/v7"
   />
   <Card
     title="Data Stream Protocol"

package/.docs/raw/docs/runtimes/ai-sdk/v5-legacy.mdx

@@ -1,19 +1,19 @@
 ---
 title: AI SDK v5 (legacy)
-description: Reference for projects still on AI SDK v5. New projects should use v6.
+description: Reference for projects still on AI SDK v5. New projects should use v7.
 ---
 
 import { VercelIcon } from "@/components/icons/vercel";
 
 <Callout type="warn">
-AI SDK v5 is a legacy version. New projects should use [AI SDK v6](/docs/runtimes/ai-sdk/v6). v5 users stay on `@assistant-ui/react-ai-sdk@0.x`; the latest line targets v6+.
+AI SDK v5 is a legacy version. New projects should use [AI SDK v7](/docs/runtimes/ai-sdk/v7). v5 users stay on `@assistant-ui/react-ai-sdk@0.x`; the latest line targets v7+.
 </Callout>
 
 ## Why legacy
 
 AI SDK v6 introduced major API changes: async `convertToModelMessages`, a new tool schema, and `toUIMessageStreamResponse()`. v5 still works but no longer receives new features in `@assistant-ui/react-ai-sdk`. Pinning to `@0.x` keeps you on the v5-compatible surface.
 
-This page is reference for existing v5 projects. Plan to migrate to v6 when feasible.
+This page is reference for existing v5 projects. Plan to migrate to v7 when feasible.
 
 ## Setup
 
@@ -122,9 +122,9 @@ AI SDK provides codemods at [ai-sdk.dev/docs/migration-guides/migration-guide-6-
 <Cards>
   <Card
     icon={<VercelIcon width={20} height={20} />}
-    title="AI SDK v6"
+    title="AI SDK v7"
     description="Current integration; what new projects should target."
-    href="/docs/runtimes/ai-sdk/v6"
+    href="/docs/runtimes/ai-sdk/v7"
   />
   <Card
     icon={<VercelIcon width={20} height={20} />}

package/.docs/raw/docs/runtimes/ai-sdk/{v6.mdx → v6-legacy.mdx}

@@ -1,9 +1,13 @@
 ---
-title: AI SDK v6
-description: Integrate Vercel AI SDK v6 with assistant-ui for streaming chat.
+title: AI SDK v6 (legacy)
+description: Reference for projects still on AI SDK v6. New projects should use v7.
 ---
 
-Current-version integration. Requires `ai@^6` and `@ai-sdk/react@^3`. For older versions see the [overview](/docs/runtimes/ai-sdk/overview).
+<Callout type="warn">
+AI SDK v6 is a legacy version. New projects should use [AI SDK v7](/docs/runtimes/ai-sdk/v7). v6 users stay on `@assistant-ui/react-ai-sdk@1.x`; the latest line targets v7+.
+</Callout>
+
+Requires `ai@^6` and `@ai-sdk/react@^3`. For other versions see the [overview](/docs/runtimes/ai-sdk/overview).
 
 ## Quickstart
 
@@ -332,7 +336,6 @@ import { Thread } from "@/components/assistant-ui/thread";
 
 export default function Page() {
   const chat = useChat({
-    api: "/api/chat",
     sendAutomaticallyWhen: lastAssistantMessageIsCompleteWithApprovalResponses,
   });
   const runtime = useAISDKRuntime(chat);
@@ -391,7 +394,6 @@ const toolkit = defineToolkit({
 
 export default function Page() {
   const chat = useChat({
-    api: "/api/chat",
     sendAutomaticallyWhen: lastAssistantMessageIsCompleteWithApprovalResponses,
   });
   const runtime = useAISDKRuntime(chat);
@@ -610,7 +612,7 @@ const runtime = useAISDKRuntime(chat);
 
 ## Example
 
-[`examples/with-ai-sdk-v6`](https://github.com/assistant-ui/assistant-ui/tree/main/examples/with-ai-sdk-v6) shows a complete reference implementation.
+The maintained example targets v7: [`examples/with-ai-sdk-v7`](https://github.com/assistant-ui/assistant-ui/tree/main/examples/with-ai-sdk-v7). The last v6 revision of that example lives in the repository history alongside the `@assistant-ui/react-ai-sdk` 1.x releases.
 
 For responses that should survive a page reload mid-stream, see [Resumable streams](/docs/guides/resumable-streams), which wraps the same v6 byte stream in `assistant-stream/resumable`.