@assistant-ui/mcp-docs-server 0.2.2 → 0.2.3

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

@@ -8,7 +8,7 @@ If you already have an assistant-ui web app, most of your code transfers directl
 ## What stays the same
 
 - **Runtime setup** — `useChatRuntime`, `useLocalRuntime`, `ChatModelAdapter`, and all runtime options work identically.
-- **AI SDK integration** — `@assistant-ui/react-ai-sdk` works with React Native. Your `useChatRuntime` + `AssistantChatTransport` setup transfers directly.
+- **AI SDK integration** — `@assistant-ui/ai-sdk` works with React Native. Your `useChatRuntime` + `AssistantChatTransport` setup transfers directly.
 - **Tool definitions** — `Tools({ toolkit })` and toolkit renderers use the same API.
 - **State hooks** — `useAuiState`, `useAui`, and selector patterns are the same.
 - **Backend code** — Your API routes, streaming endpoints, and server-side logic need zero changes.
@@ -40,7 +40,7 @@ Your `useChatRuntime` setup works as-is — no changes needed:
 
 ```tsx title="hooks/use-app-runtime.ts"
 // This file is identical to your web version
-import { useChatRuntime, AssistantChatTransport } from "@assistant-ui/react-ai-sdk";
+import { useChatRuntime, AssistantChatTransport } from "@assistant-ui/ai-sdk";
 
 export function useAppRuntime() {
   return useChatRuntime({

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

@@ -12,7 +12,7 @@ Many primitives share their core logic with `@assistant-ui/react` via `@assistan
 ## Thread
 
 ```tsx
-import { ThreadPrimitive } from "@assistant-ui/react-native";
+import { AuiIf, ThreadPrimitive } from "@assistant-ui/react-native";
 ```
 
 ### ThreadPrimitive.Root
@@ -100,12 +100,17 @@ Renders a single message at a specific index in the thread. Provides message con
 
 ### ThreadPrimitive.Empty
 
-Renders its children only when the thread has no messages. Deprecated in favor of `AuiIf`.
+Renders its children only when the thread is empty (no messages and not loading). Deprecated in favor of `AuiIf`.
 
 ```tsx
 <ThreadPrimitive.Empty>
   <Text>Send a message to get started</Text>
 </ThreadPrimitive.Empty>
+
+// preferred
+<AuiIf condition={(s) => s.thread.isEmpty}>
+  <Text>Send a message to get started</Text>
+</AuiIf>
 ```
 
 ### ThreadPrimitive.If
@@ -117,9 +122,14 @@ Conditional rendering based on thread state. Deprecated in favor of `AuiIf`.
   <Text>No messages yet</Text>
 </ThreadPrimitive.If>
 
-<ThreadPrimitive.If running>
+// preferred
+<AuiIf condition={(s) => s.thread.isEmpty}>
+  <Text>No messages yet</Text>
+</AuiIf>
+
+<AuiIf condition={(s) => s.thread.isRunning}>
   <ActivityIndicator />
-</ThreadPrimitive.If>
+</AuiIf>
 ```
 
 | Prop | Type | Description |
@@ -197,7 +207,10 @@ import { AuiIf } from "@assistant-ui/react-native";
 ## Composer
 
 ```tsx
-import { ComposerPrimitive } from "@assistant-ui/react-native";
+import {
+  ComposerPrimitive,
+  QueueItemPrimitive,
+} from "@assistant-ui/react-native";
 ```
 
 ### ComposerPrimitive.Root
@@ -275,6 +288,79 @@ Renders composer attachments using the provided component configuration.
 </ComposerPrimitive.AddAttachment>
 ```
 
+### ComposerPrimitive.Queue
+
+Renders all queued composer items. Each item is wrapped in a `QueueItemByIndexProvider`, so `QueueItemPrimitive.*` can read item state and call queue actions inside the render prop. Backed by the shared `ComposerPrimitiveQueue` from `@assistant-ui/core/react`.
+
+```tsx
+<ComposerPrimitive.Queue>
+  {({ queueItem }) => (
+    <View>
+      <QueueItemPrimitive.Text />
+      <QueueItemPrimitive.Steer>
+        <Text>Run now</Text>
+      </QueueItemPrimitive.Steer>
+      <QueueItemPrimitive.Remove>
+        <Text>Remove</Text>
+      </QueueItemPrimitive.Remove>
+    </View>
+  )}
+</ComposerPrimitive.Queue>
+```
+
+| Prop | Type | Description |
+|------|------|-------------|
+| `children` | `(value: { queueItem: QueueItemState }) => ReactNode` | Render function called for each queue item |
+
+### ComposerPrimitive.Quote
+
+Renders the active composer quote preview. Children are only rendered while `s.composer.quote` is set, so this acts as both a container and a gate.
+
+```tsx
+<ComposerPrimitive.Quote>
+  <View>
+    <Text>Quoting:</Text>
+    <ComposerPrimitive.QuoteText />
+    <ComposerPrimitive.QuoteDismiss>
+      <Text>Clear</Text>
+    </ComposerPrimitive.QuoteDismiss>
+  </View>
+</ComposerPrimitive.Quote>
+```
+
+| Prop | Type | Description |
+|------|------|-------------|
+| `children` | `ReactNode` | Quote preview content; only rendered when a quote is set |
+| `...rest` | `ViewProps` | Standard React Native View props |
+
+### ComposerPrimitive.QuoteText
+
+Renders the quoted text from `s.composer.quote?.text`. Pass `children` to override the displayed value.
+
+```tsx
+<ComposerPrimitive.QuoteText />
+```
+
+| Prop | Type | Description |
+|------|------|-------------|
+| `children` | `ReactNode` | Override content; defaults to `s.composer.quote?.text` |
+| `...rest` | `TextProps` | Standard React Native Text props |
+
+### ComposerPrimitive.QuoteDismiss
+
+`Pressable` that clears the active quote by calling `aui.composer.setQuote(undefined)`.
+
+```tsx
+<ComposerPrimitive.QuoteDismiss>
+  <Text>Clear</Text>
+</ComposerPrimitive.QuoteDismiss>
+```
+
+| Prop | Type | Description |
+|------|------|-------------|
+| `children` | `PressableProps["children"]` | Button content, including Pressable render-function children |
+| `...rest` | `Omit<PressableProps, "onPress">` | Standard React Native Pressable props except `onPress` |
+
 ### ComposerPrimitive.AttachmentByIndex
 
 Renders a single composer attachment at the specified index. Useful for building custom attachment layouts.
@@ -557,6 +643,57 @@ Container `View` for an attachment.
 </AttachmentPrimitive.Remove>
 ```
 
+## QueueItem
+
+```tsx
+import { QueueItemPrimitive } from "@assistant-ui/react-native";
+```
+
+Primitives for rendering individual queued composer items. Use inside a `ComposerPrimitive.Queue` render prop, where the queue item context is set up by `QueueItemByIndexProvider`.
+
+### QueueItemPrimitive.Text
+
+Renders the queue item's text with React Native `<Text>`. Pass `children` to override the displayed value.
+
+```tsx
+<QueueItemPrimitive.Text />
+```
+
+| Prop | Type | Description |
+|------|------|-------------|
+| `children` | `ReactNode` | Override content; defaults to the text parts of `s.queueItem.parts` |
+| `...rest` | `TextProps` | Standard React Native Text props |
+
+### QueueItemPrimitive.Remove
+
+`Pressable` that removes the queue item by calling `aui.queueItem.remove()`.
+
+```tsx
+<QueueItemPrimitive.Remove>
+  <Text>Remove</Text>
+</QueueItemPrimitive.Remove>
+```
+
+| Prop | Type | Description |
+|------|------|-------------|
+| `children` | `PressableProps["children"]` | Button content, including Pressable render-function children |
+| `...rest` | `Omit<PressableProps, "onPress">` | Standard React Native Pressable props except `onPress` |
+
+### QueueItemPrimitive.Steer
+
+`Pressable` that promotes the queue item to run next by calling `aui.queueItem.steer()`.
+
+```tsx
+<QueueItemPrimitive.Steer>
+  <Text>Run now</Text>
+</QueueItemPrimitive.Steer>
+```
+
+| Prop | Type | Description |
+|------|------|-------------|
+| `children` | `PressableProps["children"]` | Button content, including Pressable render-function children |
+| `...rest` | `Omit<PressableProps, "onPress">` | Standard React Native Pressable props except `onPress` |
+
 ## ActionBar
 
 ```tsx

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

@@ -1,6 +1,6 @@
 ---
 title: Runtime options
-description: useAgUiRuntime options, adapters, supported events, thread list.
+description: useAgUiRuntime options, adapters, message conversion, thread list.
 ---
 
 import { AguiIcon } from "@/components/icons/agui";
@@ -85,6 +85,18 @@ An assistant message whose tool call has no matching tool result is reconstructe
 
 Interrupts are restored when your backend persists them on the assistant message. The AG-UI message body has no interrupt field, so persist the runtime's own `metadata.custom.agui.interrupts` array alongside the message; `fromAgUiMessages` reads it back, reconstructs `requires-action` / `interrupt` status, and re-attaches the metadata, so `getPendingInterrupts`, `useAgUiInterrupts`, and `submitInterruptResponses` work on reload. When both a pending tool call and an interrupt are present on the same message, interrupt status wins. Without the persisted array, interrupt state cannot be reconstructed.
 
+## Building AG-UI run input
+
+`toAgUiMessages` is the converter the runtime uses to build `runAgent` input. Use it when you own the transport, for example an AG-UI WebSocket, and need the same conversion from `onNew`'s `AppendMessage`:
+
+```tsx
+import { toAgUiMessages } from "@assistant-ui/react-ag-ui";
+
+const [agUiMessage] = toAgUiMessages([message]);
+```
+
+`AppendMessage` has no `id`. The converter assigns one so the AG-UI message schema is satisfied. A caller-supplied id is kept. A generated id is new on every call, so convert once and send that object. Only `user`, `assistant`, `system`, `developer`, `tool`, and `reasoning` inputs are converted.
+
 ## Thread list (experimental)
 
 <Callout type="warn">

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

@@ -5,13 +5,13 @@ description: Connect the Vercel AI SDK to a React chat UI via assistant-ui — u
 
 import { VercelIcon } from "@/components/icons/vercel";
 
-`@assistant-ui/react-ai-sdk` integrates assistant-ui with the [Vercel AI SDK](https://ai-sdk.dev/). It covers `useChat` flows, custom transports, frontend tools, attachments, quote context, multi-step agents, token usage, and cloud persistence.
+`@assistant-ui/ai-sdk` integrates assistant-ui with the [Vercel AI SDK](https://ai-sdk.dev/). It covers `useChat` flows, custom transports, frontend tools, attachments, quote context, multi-step agents, token usage, and cloud persistence.
 
 ## Pick a version
 
 | AI SDK | Runtime package | Docs |
 | --- | --- | --- |
-| `ai@^7` + `@ai-sdk/react@^4` | `@assistant-ui/react-ai-sdk@^1.4` (latest) | [v7 (current)](/docs/runtimes/ai-sdk/v7) |
+| `ai@^7` + `@ai-sdk/react@^4` | `@assistant-ui/ai-sdk` (latest) | [v7 (current)](/docs/runtimes/ai-sdk/v7) |
 | `ai@^6` + `@ai-sdk/react@^3` | `@assistant-ui/react-ai-sdk@1.3.40` | [v6 (legacy)](/docs/runtimes/ai-sdk/v6-legacy) |
 | `ai@^5` + `@ai-sdk/react@^2` | `@assistant-ui/react-ai-sdk@1.1.21` | [v5 (legacy)](/docs/runtimes/ai-sdk/v5-legacy) |
 | `ai@^4` | `@assistant-ui/react-data-stream` | [v4 (legacy)](/docs/runtimes/ai-sdk/v4-legacy) |
@@ -20,7 +20,7 @@ New projects should target v7. v6, v5, and v4 are documented for projects that h
 
 ## 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).
+`@assistant-ui/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).
 

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

@@ -6,12 +6,12 @@ description: Reference for projects still on AI SDK v4. New projects should use
 import { VercelIcon } from "@/components/icons/vercel";
 
 <Callout type="warn">
-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`.
+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/ai-sdk`.
 </Callout>
 
 ## Why legacy
 
-Vercel ships AI SDK majors roughly yearly; v4 is three majors behind v7. The current `@assistant-ui/react-ai-sdk` package targets the current AI SDK major (v7) exclusively, so v4 users plug into [`@assistant-ui/react-data-stream`](/docs/runtimes/custom/data-stream) instead — the same data stream protocol that v4's `toDataStreamResponse()` emits.
+Vercel ships AI SDK majors roughly yearly; v4 is three majors behind v7. The current `@assistant-ui/ai-sdk` package targets the current AI SDK major (v7) exclusively, so v4 users plug into [`@assistant-ui/react-data-stream`](/docs/runtimes/custom/data-stream) instead — the same data stream protocol that v4's `toDataStreamResponse()` emits.
 
 This page is reference for existing v4 projects. Plan to migrate to v7 when feasible.
 
@@ -79,7 +79,7 @@ detects it automatically. If a custom proxy strips or hides that header, pass
 | Feature | v4 | v6 |
 | --- | --- | --- |
 | `ai` package | `ai@^4` | `ai@^6` |
-| Runtime package | `@assistant-ui/react-data-stream` | `@assistant-ui/react-ai-sdk` |
+| Runtime package | `@assistant-ui/react-data-stream` | `@assistant-ui/react-ai-sdk@1.3.40` |
 | Runtime hook | `useDataStreamRuntime` | `useChatRuntime` |
 | Response | `toDataStreamResponse()` | `toUIMessageStreamResponse()` |
 | Tool schema | `parameters: z.object({...})` | `inputSchema: zodSchema(z.object({...}))` |
@@ -89,7 +89,7 @@ detects it automatically. If a custom proxy strips or hides that header, pass
 
 When you are ready to upgrade:
 
-1. Swap `@assistant-ui/react-data-stream` for `@assistant-ui/react-ai-sdk`.
+1. Swap `@assistant-ui/react-data-stream` for `@assistant-ui/ai-sdk`.
 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`.
 

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

@@ -48,17 +48,17 @@ npm init -y
 <PlatformTabs>
 <Tab value="React">
 
-<InstallCommand npm={["@assistant-ui/react", "@assistant-ui/react-ai-sdk", "ai@^7", "@ai-sdk/react@^4", "@ai-sdk/openai", "zod"]} />
+<InstallCommand npm={["@assistant-ui/react", "@assistant-ui/ai-sdk", "ai@^7", "@ai-sdk/react@^4", "@ai-sdk/openai", "zod"]} />
 
 </Tab>
 <Tab value="React Native">
 
-<InstallCommand expo={["@assistant-ui/react-native", "@assistant-ui/react-ai-sdk", "ai@^7", "@ai-sdk/react@^4", "@ai-sdk/openai", "zod"]} />
+<InstallCommand expo={["@assistant-ui/react-native", "@assistant-ui/ai-sdk", "ai@^7", "@ai-sdk/react@^4", "@ai-sdk/openai", "zod"]} />
 
 </Tab>
 <Tab value="React Ink">
 
-<InstallCommand npm={["@assistant-ui/react-ink", "@assistant-ui/react-ai-sdk", "ai@^7", "@ai-sdk/react@^4", "@ai-sdk/openai", "zod", "ink", "react"]} />
+<InstallCommand npm={["@assistant-ui/react-ink", "@assistant-ui/ai-sdk", "ai@^7", "@ai-sdk/react@^4", "@ai-sdk/openai", "zod", "ink", "react"]} />
 
 </Tab>
 </PlatformTabs>
@@ -122,7 +122,7 @@ export async function POST(req: Request) {
 
 import { Thread } from "@/components/assistant-ui/thread";
 import { AssistantRuntimeProvider } from "@assistant-ui/react";
-import { useChatRuntime } from "@assistant-ui/react-ai-sdk";
+import { useChatRuntime } from "@assistant-ui/ai-sdk";
 
 export default function Home() {
   const runtime = useChatRuntime();
@@ -144,7 +144,7 @@ import { AssistantRuntimeProvider } from "@assistant-ui/react-native";
 import {
   AssistantChatTransport,
   useChatRuntime,
-} from "@assistant-ui/react-ai-sdk";
+} from "@assistant-ui/ai-sdk";
 import { View } from "react-native";
 import { Thread } from "@/components/assistant-ui/thread";
 
@@ -174,7 +174,7 @@ import { AssistantRuntimeProvider } from "@assistant-ui/react-ink";
 import {
   AssistantChatTransport,
   useChatRuntime,
-} from "@assistant-ui/react-ai-sdk";
+} from "@assistant-ui/ai-sdk";
 import { Box } from "ink";
 import { Thread } from "./components/thread.js";
 
@@ -231,7 +231,7 @@ Follow the [Ink setup](/docs/ink) to add a terminal Thread, composer, and suppor
 import { openai } from "@ai-sdk/openai";
 import { streamText, convertToModelMessages, zodSchema, createUIMessageStreamResponse, toUIMessageStream } from "ai";
 import type { UIMessage } from "ai";
-import { frontendTools } from "@assistant-ui/react-ai-sdk";
+import { frontendTools } from "@assistant-ui/ai-sdk";
 
 export async function POST(req: Request) {
   const {
@@ -341,7 +341,7 @@ import { useChat } from "@ai-sdk/react";
 import {
   AssistantRuntimeProvider,
   useAISDKRuntime,
-} from "@assistant-ui/react-ai-sdk";
+} from "@assistant-ui/ai-sdk";
 import { lastAssistantMessageIsCompleteWithApprovalResponses } from "ai";
 import { Thread } from "@/components/assistant-ui/thread";
 
@@ -372,7 +372,7 @@ import {
   defineToolkit,
   Tools,
 } from "@assistant-ui/react";
-import { useAISDKRuntime } from "@assistant-ui/react-ai-sdk";
+import { useAISDKRuntime } from "@assistant-ui/ai-sdk";
 import { lastAssistantMessageIsCompleteWithApprovalResponses } from "ai";
 import { Thread } from "@/components/assistant-ui/thread";
 
@@ -432,7 +432,7 @@ import {
   createUIMessageStreamResponse,
   toUIMessageStream,
 } from "ai";
-import { injectQuoteContext } from "@assistant-ui/react-ai-sdk";
+import { injectQuoteContext } from "@assistant-ui/ai-sdk";
 import { openai } from "@ai-sdk/openai";
 
 export async function POST(req: Request) {
@@ -455,7 +455,7 @@ export async function POST(req: Request) {
 
 ```ts title="@/app/api/chat/route.ts"
 import { streamText, convertToModelMessages, createUIMessageStreamResponse, toUIMessageStream } from "ai";
-import { frontendTools } from "@assistant-ui/react-ai-sdk";
+import { frontendTools } from "@assistant-ui/ai-sdk";
 
 export async function POST(req: Request) {
   const { messages, tools, config } = await req.json();
@@ -484,7 +484,7 @@ export async function POST(req: Request) {
 ```tsx title="@/components/TokenCounter.tsx"
 "use client";
 
-import { useThreadTokenUsage } from "@assistant-ui/react-ai-sdk";
+import { useThreadTokenUsage } from "@assistant-ui/ai-sdk";
 
 export function TokenCounter() {
   const usage = useThreadTokenUsage();
@@ -539,7 +539,7 @@ For server-side cloud persistence with zero adapter code, see the [AssistantClou
 ```tsx
 "use client";
 
-import { useChatRuntime } from "@assistant-ui/react-ai-sdk";
+import { useChatRuntime } from "@assistant-ui/ai-sdk";
 import type { ThreadHistoryAdapter } from "@assistant-ui/react";
 
 const historyAdapter: ThreadHistoryAdapter = {
@@ -585,7 +585,7 @@ Each persisted row follows `{ id, parent_id, format, content }`. `fmt.encode` pr
 import {
   useChatRuntime,
   AssistantChatTransport,
-} from "@assistant-ui/react-ai-sdk";
+} from "@assistant-ui/ai-sdk";
 
 const runtime = useChatRuntime({
   transport: new AssistantChatTransport({ api: "/my-custom-api/chat" }),
@@ -644,13 +644,28 @@ const runtime = useChatRuntime({
 
 When omitted, `resumeRun` throws `"Runtime does not support resuming runs."`. For streams that should survive a page reload without a custom channel, use the built-in transport-level path instead: see [Resumable streams](/docs/guides/resumable-streams), which reconnects automatically on mount and reports failures via `onResumeError`.
 
+### messageRepository
+
+Import a branch-aware AI SDK message tree once, and only when `useChat` is empty. After that seed, live updates come only from `useChat`. Clearing the chat or passing a new object identity does not reload the tree. Persisted threads that already go through `adapters.history` do not need this.
+
+```tsx
+const runtime = useChatRuntime({
+  messageRepository: storedTree,
+  unstable_onBranchChange: ({ headId }) => {
+    saveSelectedBranch(headId);
+  },
+});
+```
+
+`unstable_onBranchChange` fires after an explicit `switchToBranch` (for example a BranchPicker click). It complements `setMessages` and does not enable switching by itself. The callback is unstable and may change without notice.
+
 ## Advanced: useAISDKRuntime
 
 When you need direct access to the `useChat` instance (e.g. to share it with non-assistant-ui code), drop down to `useAISDKRuntime`:
 
 ```tsx
 import { useChat } from "@ai-sdk/react";
-import { useAISDKRuntime } from "@assistant-ui/react-ai-sdk";
+import { useAISDKRuntime } from "@assistant-ui/ai-sdk";
 
 const chat = useChat();
 const runtime = useAISDKRuntime(chat);
@@ -658,7 +673,7 @@ const runtime = useAISDKRuntime(chat);
 
 `useAISDKRuntime` does not provide `cloud` or the higher-level adapter slots; those are part of `useChatRuntime`. If you need both your own `useChat` access AND cloud thread support, you generally want `useChatRuntime` and to read the chat state through assistant-ui hooks instead.
 
-`useAISDKRuntime` accepts `joinStrategy` and `onResume` (see [Runtime options](#runtime-options)) plus one option of its own, `cancelPendingToolCallsOnSend`:
+`useAISDKRuntime` accepts `joinStrategy`, `onResume`, `messageRepository`, and `unstable_onBranchChange` (see [Runtime options](#runtime-options)) plus one option of its own, `cancelPendingToolCallsOnSend`:
 
 ```tsx
 const runtime = useAISDKRuntime(chat, {

package/.docs/raw/docs/runtimes/concepts/adapters.mdx

@@ -21,7 +21,7 @@ const runtime = useChatRuntime({ adapters: { attachments, history } });
 
 ## Support matrix
 
-| Adapter | LocalRuntime | ExternalStoreRuntime | DataStream | AssistantTransport | react-ai-sdk | react-langgraph | react-langchain | react-google-adk | react-a2a | react-ag-ui | react-opencode |
+| Adapter | LocalRuntime | ExternalStoreRuntime | DataStream | AssistantTransport | ai-sdk | react-langgraph | react-langchain | react-google-adk | react-a2a | react-ag-ui | react-opencode |
 | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
 | Attachments | Yes | Yes | Yes | Yes | Yes | (via thread state) | (via thread state) | Yes | Yes | Yes | (no) |
 | Speech | Yes | Yes | Yes | (no) | Yes | Yes | Yes | Yes | Yes | Yes | (no) |
@@ -173,7 +173,7 @@ const feedbackAdapter: FeedbackAdapter = {
 
 ## History adapter
 
-Per-thread message persistence. Used by `LocalRuntime` and adapters built on it (`react-ai-sdk`, `react-google-adk`, `react-a2a`, `useDataStreamRuntime`).
+Per-thread message persistence. Used by `LocalRuntime` and adapters built on it (`ai-sdk`, `react-google-adk`, `react-a2a`, `useDataStreamRuntime`).
 
 `ExternalStoreRuntime` does not use a history adapter directly, since you already own the message array. Persist via your store instead. `react-langgraph` and `react-langchain` source persistence from server-side thread state, exposed through their `load` callbacks.
 
@@ -196,7 +196,7 @@ type ThreadHistoryAdapter = {
 `load` runs when a thread opens. `append` runs after each message completes.
 
 <Callout type="info">
-`react-ai-sdk` requires `withFormat` so messages round-trip as AI SDK `UIMessage` objects. An adapter without `withFormat` throws at runtime in the AI SDK path. See the [AI SDK history docs](/docs/runtimes/ai-sdk/v7) for the full pattern.
+`ai-sdk` requires `withFormat` so messages round-trip as AI SDK `UIMessage` objects. An adapter without `withFormat` throws at runtime in the AI SDK path. See the [AI SDK history docs](/docs/runtimes/ai-sdk/v7) for the full pattern.
 </Callout>
 
 ## Suggestion adapter

package/.docs/raw/docs/runtimes/concepts/architecture.mdx

@@ -10,7 +10,7 @@ assistant-ui exposes runtime integrations at three layers. Understanding which l
 <Flow.Root
   llm={`graph TD
     subgraph Framework["Framework adapters"]
-      A1[react-ai-sdk]
+      A1[ai-sdk]
       A2[react-langgraph]
       A3[react-langchain]
       A4[react-google-adk]
@@ -58,7 +58,7 @@ assistant-ui exposes runtime integrations at three layers. Understanding which l
       <Flow.Group flowId="adapters">
         <Flow.GroupLabel>Framework adapters</Flow.GroupLabel>
         <Flow.Row className="flex-wrap justify-start">
-          <Flow.Node>react-ai-sdk</Flow.Node>
+          <Flow.Node>ai-sdk</Flow.Node>
           <Flow.Node>react-langgraph</Flow.Node>
           <Flow.Node>react-langchain</Flow.Node>
           <Flow.Node>react-google-adk</Flow.Node>
@@ -118,7 +118,7 @@ The fastest path. Each adapter wraps one of the core or protocol layers and adds
 
 | Adapter | Layered on | Targets |
 | --- | --- | --- |
-| `react-ai-sdk` | `ExternalStoreRuntime` | Vercel AI SDK v7 (`useChat`) |
+| `ai-sdk` | `ExternalStoreRuntime` | Vercel AI SDK v7 (`useChat`) |
 | `react-langgraph` | `ExternalStoreRuntime` | LangGraph Cloud via `@langchain/langgraph-sdk` |
 | `react-langchain` | `ExternalStoreRuntime` | LangGraph Cloud via `@langchain/react`'s `useStream` |
 | `react-google-adk` | `ExternalStoreRuntime` | Google ADK JS or Python agents |

package/.docs/raw/docs/runtimes/concepts/threads.mdx

@@ -50,9 +50,9 @@ See the [cloud documentation](/docs/cloud) for setup, auth, and self-host option
 
 ## RemoteThreadListRuntime (custom database)
 
-`useRemoteThreadListRuntime` lets you back the thread list with any database while keeping the per-thread runtime simple. You provide a `RemoteThreadListAdapter` describing how to list, create, rename, archive, and delete threads.
+`useRemoteThreadListRuntime` lets you back the thread list with any database while keeping the per-thread runtime simple. You provide a `RemoteThreadListAdapter` describing how to list, create, rename, archive, and delete threads. Keep that adapter reference stable across renders (module scope or `useMemo`). Replacing it reloads the list and drops cached threads that are not in the replacement page.
 
-Works with any `LocalRuntime`-based runtime, including framework adapters that build on it (`react-ai-sdk`, `react-google-adk`, `react-a2a`, `useDataStreamRuntime`).
+Works with any `LocalRuntime`-based runtime, including framework adapters that build on it (`ai-sdk`, `react-google-adk`, `react-a2a`, `useDataStreamRuntime`).
 
 ```tsx title="app/MyProvider.tsx"
 "use client";
@@ -241,11 +241,11 @@ function ReloadOnAuth() {
 }
 ```
 
-`reload()` discards in-flight responses from superseded calls, so it is safe to invoke on every auth transition.
+`reload()` discards in-flight responses from superseded calls, so it is safe to invoke on every auth transition. On the `RemoteThreadList` store entry, a recreated adapter object is a no-op until you call `reload()`. `reload()` against the same instance refreshes the list and keeps the open thread. `reload()` after a different adapter instance resets selection and cached records, then loads the replacement store.
 
 ### Refetching the open thread
 
-`reload()` re-runs `list()`, which refreshes thread list metadata only. It does not touch the messages of the thread the user is looking at. When the open thread's server state changes out of band, so that nothing arrives over the stream (a human-in-the-loop interrupt raised by another process, a stalled stream, a status change picked up by polling), call `aui.threads.reloadMainThread()`:
+`reload()` against the same adapter instance re-runs `list()`, which refreshes thread list metadata only. It does not touch the messages of the thread the user is looking at. When the open thread's server state changes out of band, so that nothing arrives over the stream (a human-in-the-loop interrupt raised by another process, a stalled stream, a status change picked up by polling), call `aui.threads.reloadMainThread()`:
 
 ```tsx
 function RefetchOnInterrupt({ status }: { status: string }) {
@@ -268,7 +268,7 @@ How the refetch happens depends on the runtime, in one of three ways. When it de
 
 `useAuiState((s) => s.thread.capabilities.refetchThread)` reports which of those you would get, in place or not. It is not a signal for whether to offer a refresh at all: it is false on the remount path, where the call still does the work, and false again where the call does nothing.
 
-Both the LangGraph and Google ADK adapters register the in-place refetch capability when their runtime hook receives a `load` function; without one they fall back to the remount path. Other remote adapters take the remount path unless they provide the capability themselves.
+Both the LangGraph and Google ADK adapters register the in-place refetch capability when their runtime hook receives a `load` function; without one they fall back to the remount path. The Eve adapter registers it when the installed `eve` exposes `resume()` (0.44.1 and later), with no option to pass; on older releases it falls back like any other adapter, which for the single and in-memory thread lists it is usually paired with means the call resolves without doing anything. A refetch that lands during a run also settles differently across the three: LangGraph and Google ADK issue the load right away, so the promise settles at fetch latency and each decides on arrival how much of the snapshot a racing run leaves standing, while Eve queues the replay behind the in-flight turn, so its promise settles only once that turn parks. Other remote adapters take the remount path unless they provide the capability themselves.
 
 For an external store runtime, declare it with `onRefetchThread`, which is unrelated to `onReload` (that one re-generates an assistant message); the tap `ExternalThread` accepts the same prop:
 

package/.docs/raw/docs/runtimes/langchain.mdx

@@ -744,8 +744,8 @@ Register the components with `makeAssistantDataUI`, keyed by the `UIMessage`'s `
 import {
   AssistantRuntimeProvider,
   makeAssistantDataUI,
-  Thread,
 } from "@assistant-ui/react";
+import { Thread } from "@/components/assistant-ui/thread";
 import { useStreamRuntime } from "@assistant-ui/react-langchain";
 
 const ChartUI = makeAssistantDataUI({

package/.docs/raw/docs/runtimes/opencode/quickstart.mdx

@@ -41,7 +41,7 @@ export function MyRuntimeProvider({
 ### Render the Thread
 
 ```tsx title="app/page.tsx"
-import { Thread } from "@assistant-ui/react";
+import { Thread } from "@/components/assistant-ui/thread";
 import { MyRuntimeProvider } from "./MyRuntimeProvider";
 
 export default function Page() {

package/.docs/raw/docs/runtimes/pick-a-runtime.mdx

@@ -88,7 +88,7 @@ For frameworks without a dedicated adapter, these wiring guides route through an
       icon={<CloudflareIcon width={20} height={20} />}
       title="Cloudflare Agents"
       description="Stateful agents on Durable Objects with WebSocket streaming. Wired through the Vercel AI SDK runtime."
-      href="/docs/integrations/frameworks/cloudflare-agents/overview"
+      href="/docs/integrations/frameworks/cloudflare-agents"
     />
     <Card
       icon={<MastraIcon width={20} height={20} />}

package/.docs/raw/docs/tools/backend.mdx

@@ -10,10 +10,10 @@ For authoring tools, see [Defining Tools](/docs/tools/defining-tools). For MCP s
 
 ## The request body
 
-`@assistant-ui/react-ai-sdk` posts `{ messages, system, tools }` to your route. `tools` is the map of **frontend** tools the client serialized for this request (the model needs their schemas to call them, even though they run in the browser):
+`@assistant-ui/ai-sdk` posts `{ messages, system, tools }` to your route. `tools` is the map of **frontend** tools the client serialized for this request (the model needs their schemas to call them, even though they run in the browser):
 
 ```ts
-import type { FrontendTools } from "@assistant-ui/react-ai-sdk";
+import type { FrontendTools } from "@assistant-ui/ai-sdk";
 
 const {
   messages,
@@ -31,7 +31,7 @@ const {
 When you author tools in a [`"use generative"` file](/docs/tools/defining-tools#quick-start-use-generative), the same import resolves to the **server build** inside a route handler — schema plus any backend `execute`, with renderers stripped. Wrap it in an `AISDKToolkit` and call `.tools()` with the uploaded `tools`:
 
 ```ts title="app/api/chat/route.ts"
-import { AISDKToolkit } from "@assistant-ui/react-ai-sdk";
+import { AISDKToolkit } from "@assistant-ui/ai-sdk";
 import { streamText, convertToModelMessages, type UIMessage } from "ai";
 import { openai } from "@ai-sdk/openai";
 import toolkit from "../../toolkit";
@@ -70,7 +70,7 @@ serializes browser-executed tools into the request `tools`. Convert them to the
 AI SDK shape with `frontendTools` and spread your own server tools alongside:
 
 ```ts title="app/api/chat/route.ts"
-import { frontendTools } from "@assistant-ui/react-ai-sdk";
+import { frontendTools } from "@assistant-ui/ai-sdk";
 import { streamText, convertToModelMessages, tool, zodSchema } from "ai";
 import { openai } from "@ai-sdk/openai";
 import { z } from "zod";

package/.docs/raw/docs/tools/defining-tools.mdx

@@ -121,7 +121,7 @@ Import the toolkit in your runtime provider and pass it to `config` via `Tools`:
 "use client";
 
 import { AssistantRuntimeProvider, AuiConfig, Tools } from "@assistant-ui/react";
-import { useChatRuntime } from "@assistant-ui/react-ai-sdk";
+import { useChatRuntime } from "@assistant-ui/ai-sdk";
 import toolkit from "./toolkit";
 
 export function MyRuntimeProvider({ children }: { children: React.ReactNode }) {
@@ -148,7 +148,7 @@ export function MyRuntimeProvider({ children }: { children: React.ReactNode }) {
 The same import resolves to the **server build** inside a route handler. Wrap it in an `AISDKToolkit` so the model is configured with every tool's schema:
 
 ```ts title="app/api/chat/route.ts"
-import { AISDKToolkit } from "@assistant-ui/react-ai-sdk";
+import { AISDKToolkit } from "@assistant-ui/ai-sdk";
 import { streamText, convertToModelMessages } from "ai";
 import { openai } from "@ai-sdk/openai";
 import toolkit from "../../toolkit";

package/.docs/raw/docs/tools/generative-ui.mdx

@@ -99,7 +99,7 @@ import {
   AuiConfig,
   Tools,
 } from "@assistant-ui/react";
-import { useChatRuntime } from "@assistant-ui/react-ai-sdk";
+import { useChatRuntime } from "@assistant-ui/ai-sdk";
 import { lastAssistantMessageIsCompleteWithToolCalls } from "ai";
 import toolkit from "./toolkit";
 
@@ -135,7 +135,7 @@ The route imports the same toolkit module. The compiler resolves that import to
 
 ```ts title="app/api/chat/route.ts"
 import { openai } from "@ai-sdk/openai";
-import { AISDKToolkit } from "@assistant-ui/react-ai-sdk";
+import { AISDKToolkit } from "@assistant-ui/ai-sdk";
 import { convertToModelMessages, stepCountIs, streamText } from "ai";
 import toolkit from "@/app/toolkit";