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

package/.docs/raw/docs/migrations/v0-15.mdx

@@ -0,0 +1,236 @@
+---
+title: Migration to v0.15
+description: Drops the v0.12-era legacy runtime hooks, the deprecated tools map, and the "mcp-app" group key. Scope accessors become properties.
+---
+
+Version 0.15 finishes the deprecation cycle started in v0.12: the legacy context hooks are removed in favor of `useAui` / `useAuiState`, and `aui` scope accessors become properties.
+
+## Migrate with an AI Agent
+
+Paste this into an AI coding agent to run the migration for you:
+
+```text
+Migrate this codebase from assistant-ui v0.14 to v0.15.
+
+1. Read the migration guide: https://assistant-ui.com/docs/migrations/v0-15
+2. Run `npx assistant-ui@latest upgrade` to apply the codemods.
+3. Apply the remaining changes from the guide by hand:
+   - Replace removed legacy hooks with the useAui / useAuiState
+     equivalents from the guide's mapping table.
+   - Replace availability checks with `aui.<scope>.source != null`.
+   - Replace `s.tools.tools` reads with `s.tools.toolUIs`.
+   - Replace the "mcp-app" groupPartByType key with "standalone-tool-call".
+4. Typecheck, build, and run tests; fix any remaining fallout.
+```
+
+## Automatic Migration
+
+```bash
+npx assistant-ui@latest upgrade
+```
+
+This runs the `v0-15/aui-accessor-calls-to-properties` codemod, which rewrites nullary accessor calls (`aui.thread()`) to property access (`aui.thread`).
+
+## Scope Accessors Are Properties
+
+Nullary scope accessors are now properties. Calling them still works but is deprecated:
+
+```ts
+// Before
+aui.thread().getState();
+aui.threads().switchToNewThread();
+
+// After
+aui.thread.getState();
+aui.threads.switchToNewThread();
+```
+
+Selecting an unavailable scope no longer throws: `aui.thread` always succeeds and is always truthy. Its `source` is `null` when the scope is unavailable, and any other property read (or a call) throws. Check availability via:
+
+```ts
+if (aui.thread.source != null) {
+  // scope is available
+}
+```
+
+Accessors expose `source`, `query`, and `name` selection metadata as properties — previously found on the accessor function, now on the same names on the proxy. These three names are reserved and never resolve to scope methods.
+
+## Legacy Context Hooks Removed
+
+The v0.12-era runtime hooks are removed. Replace state reads with `useAuiState` and actions with `useAui`:
+
+| Removed                                                       | Replacement                                     |
+| ------------------------------------------------------------- | ----------------------------------------------- |
+| `useAssistantRuntime()`                                        | `useAui()`                                      |
+| `useThreadList(selector)`                                      | `useAuiState((s) => s.threads)`                 |
+| `useThreadRuntime()`                                           | `useAui().thread`                               |
+| `useThread(selector)`                                          | `useAuiState((s) => s.thread)`                  |
+| `useThreadComposer(selector)`                                  | `useAuiState((s) => s.thread.composer)`         |
+| `useThreadModelContext(selector)`                              | `useAuiState((s) => s.thread.modelContext)`     |
+| `useMessageRuntime()`                                          | `useAui().message`                              |
+| `useMessage(selector)`                                         | `useAuiState((s) => s.message)`                 |
+| `useEditComposer(selector)`                                    | `useAuiState((s) => s.message.composer)`        |
+| `useComposerRuntime()`                                         | `useAui().composer`                             |
+| `useComposer(selector)`                                        | `useAuiState((s) => s.composer)`                |
+| `useMessagePartRuntime()`                                      | `useAui().part`                                 |
+| `useMessagePart(selector)`                                     | `useAuiState((s) => s.part)`                    |
+| `useAttachmentRuntime()`                                       | `useAui().attachment`                           |
+| `useAttachment(selector)`                                      | `useAuiState((s) => s.attachment)`              |
+| `useThreadListItemRuntime()`                                   | `useAui().threadListItem`                       |
+| `useThreadListItem(selector)`                                  | `useAuiState((s) => s.threadListItem)`          |
+
+The attachment variants (`useThreadComposerAttachment(Runtime)`, `useEditComposerAttachment(Runtime)`, `useMessageAttachment(Runtime)`) are removed with them; use `useAui().attachment` / `useAuiState((s) => s.attachment)`.
+
+```tsx
+// Before
+const runtime = useAssistantRuntime();
+const isRunning = useThread((s) => s.isRunning);
+runtime.threads.switchToNewThread();
+
+// After
+const aui = useAui();
+const isRunning = useAuiState((s) => s.thread.isRunning);
+aui.threads.switchToNewThread();
+```
+
+## `ToolsState.tools` Removed
+
+The component-only tool-UI map is replaced by `toolUIs`, whose entries carry the renderer alongside its presentation options:
+
+```tsx
+// Before
+const Render = useAuiState((s) => s.tools.tools[toolName]?.[0]);
+
+// After
+const Render = useAuiState((s) => s.tools.toolUIs[toolName]?.[0]?.render);
+```
+
+## `"mcp-app"` Group Key Removed
+
+`groupPartByType` no longer accepts the `"mcp-app"` key. Use `"standalone-tool-call"`, a superset that matches MCP-app tool calls plus any tool call whose registered UI opts into standalone display:
+
+```tsx
+// Before
+groupPartByType({
+  "tool-call": ["group-tool"],
+  "mcp-app": [],
+});
+
+// After
+groupPartByType({
+  "tool-call": ["group-tool"],
+  "standalone-tool-call": [],
+});
+```
+
+## `useAui` `{ parent }` Config Removed
+
+The second argument (`useAui(clients, { parent })`) is removed. Provide the parent via context instead: wrap with `AuiProvider` and call the context form beneath it.
+
+```tsx
+// Before
+const aui = useAui(scopes, { parent });
+
+// After
+const Scoped = ({ children }) => {
+  const aui = useAui();
+  const config = AuiConfig(scopes);
+  return (
+    <AuiProvider extends={aui} config={config}>
+      {children}
+    </AuiProvider>
+  );
+};
+
+const rootConfig = AuiConfig({});
+
+<AuiProvider extends={parent} config={rootConfig}>
+  <Scoped />
+</AuiProvider>;
+```
+
+Where `{ parent: null }` was used to detach from context, `<AuiProvider extends={null} config={config}>` where `const config = AuiConfig({})` now provides an isolated empty root.
+
+## `AuiProvider` Grammar
+
+`AuiProvider` takes a `config` built with `AuiConfig(...)` — raw object literals are a type error. At the top level, `config` alone creates the subtree's client. Nested under a parent provider, `extends` is mandatory: `extends={aui}` extends the parent, `extends={null}` isolates (dev-enforced). `ref` receives the resulting client after mount.
+
+```tsx
+const aui = useAui();
+const config = AuiConfig({ tools: Tools({ toolkit }) });
+
+// Top-level root
+<AuiProvider config={config}>
+
+// Nested: extend the parent
+<AuiProvider extends={aui} config={config}>
+
+// Nested: isolate from the parent
+<AuiProvider extends={null} config={config}>
+```
+
+`AuiConfig` is exported from `@assistant-ui/store` and re-exported from `@assistant-ui/react`, `@assistant-ui/react-native`, and `@assistant-ui/react-ink`.
+
+### `value` Prop Deprecated
+
+```tsx
+// Before
+<AuiProvider value={client}>
+<AuiProvider value={null}>
+
+// After
+const config = AuiConfig({});
+
+<AuiProvider extends={client} config={config}>
+<AuiProvider extends={null} config={config}>
+```
+
+The replacement exposes a client extending the given one, not the same instance — `useAui()` beneath it returns the new client, with scope access delegating to `client`. The deprecated `value={client}` form behaves the same way: it also exposes a derived client rather than the exact instance, and the given client must implement `subscribe`.
+
+### `useAui({ ... })` Extension Overload Deprecated
+
+```tsx
+// Before
+const aui = useAui({ tools: Tools({ toolkit }) });
+return <AuiProvider value={aui}>{children}</AuiProvider>;
+
+// After
+const aui = useAui();
+const config = AuiConfig({ tools: Tools({ toolkit }) });
+return (
+  <AuiProvider extends={aui} config={config}>
+    {children}
+  </AuiProvider>
+);
+```
+
+Where the extended client was passed to `<AssistantRuntimeProvider aui={aui}>`, use the new `config` prop instead — the scopes are provided alongside the runtime's threads scope:
+
+```tsx
+// Before
+const aui = useAui({ tools: Tools({ toolkit }) });
+return (
+  <AssistantRuntimeProvider aui={aui} runtime={runtime}>
+    {children}
+  </AssistantRuntimeProvider>
+);
+
+// After
+const config = AuiConfig({ tools: Tools({ toolkit }) });
+return (
+  <AssistantRuntimeProvider runtime={runtime} config={config}>
+    {children}
+  </AssistantRuntimeProvider>
+);
+```
+
+## Still Deprecated (not removed)
+
+- Primitive `If` components (`ThreadPrimitive.If`, `MessagePrimitive.If`, `ThreadPrimitive.Empty`) — replaced by `AuiIf`. The codemod migrates these.
+- `useMessagePartText` / `useMessagePartReasoning` / `useMessagePartSource` / `useMessagePartImage` / `useMessagePartFile` / `useMessagePartData` — use `useAuiState` to select and narrow `s.part`.
+- The `components` prop on primitives — replaced by the children render function pattern (see the [v0.14 guide](/docs/migrations/v0-14)).
+
+## Getting Help
+
+- File issues at https://github.com/assistant-ui/assistant-ui/issues
+- See the [deprecation policy](/docs/migrations/deprecation-policy) for the support window

package/.docs/raw/docs/primitives/attachment.mdx

@@ -53,7 +53,7 @@ import { AttachmentPrimitive, ComposerPrimitive } from "@assistant-ui/react";
 </ComposerPrimitive.Root>
 ```
 
-`Root` renders a `<div>`, `unstable_Thumb` renders a `<div>` showing the file extension with a leading dot (e.g., `.pdf`), `Name` renders plain text, and `Remove` renders a `<button>`.
+`Root` renders a `<div>`, `unstable_Thumb` renders a `<div>` showing the file extension with a leading dot (e.g., `.pdf`), or the attachment type (e.g., `image`) when the filename has no extension (including leading-dot names like `.env`), `Name` renders plain text, and `Remove` renders a `<button>`. If you pass `children` to `unstable_Thumb`, they override that text.
 
 <Callout type="info">
 Runtime setup: primitives require runtime context. Wrap your UI in `AssistantRuntimeProvider` with a runtime (for example `useLocalRuntime(...)`). See [Pick a Runtime](/docs/runtimes/pick-a-runtime).
@@ -124,7 +124,7 @@ Container for a single attachment item. Renders a `<div>` element unless `asChil
 
 ### unstable_Thumb
 
-Thumbnail slot for attachment previews. Renders a `<div>` element unless `asChild` is set.
+Thumbnail slot for attachment previews. Renders a `<div>` element unless `asChild` is set. By default it shows the file extension with a leading dot (e.g., `.pdf`); if you pass `children`, they override the automatic text.
 
 ```tsx
 <AttachmentPrimitive.unstable_Thumb className="flex size-10 items-center justify-center rounded bg-muted text-xs" />

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

@@ -258,7 +258,7 @@ Renders a single attachment at a specific index.
 
 ### AttachmentDropzone
 
-Drag-and-drop zone for file attachments. Sets `data-dragging` when a file is being dragged over it. Renders a `<div>` element unless `asChild` is set.
+Drag-and-drop zone for file attachments. Sets `data-dragging` when a file is being dragged over it and the runtime supports attachments; without the attachments capability the dropzone accepts no files and shows no highlight. Non-file drags (text, links) are ignored. Renders a `<div>` element unless `asChild` is set.
 
 ```tsx
 <ComposerPrimitive.AttachmentDropzone className="rounded-xl border-2 border-dashed data-[dragging]:border-primary data-[dragging]:bg-primary/5">
@@ -507,7 +507,7 @@ Wrap your composer with `AttachmentDropzone` to support dragging files directly
 </ComposerPrimitive.AttachmentDropzone>
 ```
 
-The dropzone sets `data-dragging` when a file is being dragged over it, so you can style the active state with CSS.
+The dropzone sets `data-dragging` when a file is being dragged over it, so you can style the active state with CSS. It requires the runtime's attachments capability (an attachment adapter); without it the dropzone stays inert.
 
 ### With Voice Input
 
@@ -570,7 +570,7 @@ When `isSendDisabled` is `true`:
 - `composer.canSend` becomes `false`
 - `<ComposerPrimitive.Send>` is disabled
 - Enter and the `Cmd/Ctrl+Shift+Enter` steer hotkey become no-ops
-- `aui.composer().send()` short-circuits at the runtime, so direct calls cannot escape the gate
+- `aui.composer.send()` short-circuits at the runtime, so direct calls cannot escape the gate
 
 Read the same flag from React with `<AuiIf>` to render hints alongside the input:
 

package/.docs/raw/docs/primitives/message.mdx

@@ -112,6 +112,37 @@ Runtime setup: primitives require runtime context. Wrap your UI in `AssistantRun
 For most new code, prefer `MessagePrimitive.Parts` with a `children` render function. When you need adjacent grouping, use `MessagePrimitive.GroupedParts`.
 </Callout>
 
+### Part Types
+
+A message part is one of three kinds, and which kind a new capability belongs to is decided by the list below rather than case by case.
+
+| Kind | Parts | Grows by |
+|------|-------|----------|
+| Modality | `text`, `image`, `file` | Never. `file` carries every non-image binary modality through its `mimeType`. |
+| Provider channel | `reasoning`, `source`, `tool-call`, `generative-ui` | Never. These mirror channels a model already emits. |
+| Extensibility | `data` | Freely, through `name`. This is the growth path for anything app-level. |
+
+`file` is the media carrier. Audio, video, PDFs and everything else are `{ type: "file", mimeType: "audio/mpeg" }` rather than part types of their own, so one renderer and one converter branch handle them all. The payload can be inline base64 or a URL; `sourceType` additionally allows an opaque storage id, which the LangChain-family runtimes honor and other adapters ignore.
+
+Anything that is not a modality the model consumes or a channel it emits is a `data` part, routed by `name`:
+
+```tsx
+<MessagePrimitive.Parts
+  components={{
+    data: {
+      by_name: { citation: MyCitation },
+      Fallback: MyDataFallback,
+    },
+  }}
+/>
+```
+
+<Callout type="warn">
+`Unstable_AudioMessagePart` and the `Unstable_Audio` slot are deprecated. The audio part cannot carry a filename, has no way to declare how its payload goes on the wire (no `sourceType`, so no storage id), and exists only on user messages, so a model that returns audio has no way to express it. Send audio as a `file` part with an `audio/*` mime type instead, and give it a filename.
+
+Adapter coverage for the file path is still uneven, so check your adapter's converter before relying on file parts. Known so far: `react-pi` and the assistant-transport runtime have no file part on their user-content surface at all, so one is dropped; `react-data-stream` carries the payload but not the filename. Existing audio parts keep working; they will not gain fields.
+</Callout>
+
 ### Tool Resolution
 
 Tool call parts resolve in this order:
@@ -149,7 +180,8 @@ Returning `null` still allows registered tool UIs and data renderer UIs to rende
 - `components.ChainOfThought` takes over all reasoning and tool-call rendering (mutually exclusive with `ToolGroup`, `ReasoningGroup`, `tools`, and `Reasoning`). This legacy path is deprecated; use `MessagePrimitive.GroupedParts` for grouped Chain of Thought in new code.
 - `data.by_name` and `data.Fallback` let you route custom data part types
 - `Quote` renders quoted message references from metadata
-- `Empty` and `Unstable_Audio` are available for edge and experimental rendering paths
+- `Empty` is available for edge rendering paths
+- `Unstable_Audio` is deprecated; render `audio/*` from the `File` slot instead
 
 ```tsx
 <MessagePrimitive.Parts

package/.docs/raw/docs/primitives/suggestion.mdx

@@ -106,7 +106,7 @@ Both render a `<span>` and accept `children` to override the value from state:
 
 `Trigger`'s `send` prop controls what happens on click:
 
-- **`send={true}`**: immediately sends the suggestion as a new message. When the thread is running, it falls back to populating the composer instead.
+- **`send={true}`**: immediately sends the suggestion as a new message. While a run is in progress, the suggestion is queued on runtimes that support queueing (leaving the composer draft untouched); otherwise the trigger is disabled.
 - **`send={false}`** (default): populates the composer text so the user can edit before sending
 
 ```tsx

package/.docs/raw/docs/primitives/thread-list.mdx

@@ -253,7 +253,7 @@ Button that appends the next page of threads. Renders a `<button>` element unles
 </ThreadListPrimitive.LoadMore>
 ```
 
-For scroll-driven loading, wrap `aui.threads().loadMore()` in your own `IntersectionObserver` at the application layer; assistant-ui ships the explicit button to keep the primitive surface predictable.
+For scroll-driven loading, wrap `aui.threads.loadMore()` in your own `IntersectionObserver` at the application layer; assistant-ui ships the explicit button to keep the primitive surface predictable.
 
 ```tsx
 import { useAui, useAuiState } from "@assistant-ui/react";
@@ -271,7 +271,7 @@ function LoadMoreSentinel() {
     const el = ref.current;
     if (!el || disabled) return;
     const observer = new IntersectionObserver(([entry]) => {
-      if (entry?.isIntersecting) aui.threads().loadMore();
+      if (entry?.isIntersecting) aui.threads.loadMore();
     });
     observer.observe(el);
     return () => observer.disconnect();

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

@@ -41,11 +41,11 @@ import { useAui } from "@assistant-ui/react-native";
 const aui = useAui();
 
 // Composer actions
-aui.composer().setText("Hello");
-aui.composer().send();
+aui.composer.setText("Hello");
+aui.composer.send();
 
 // Thread actions
-aui.thread().cancelRun();
+aui.thread.cancelRun();
 ```
 
 ### useAuiEvent
@@ -155,12 +155,22 @@ export default defineToolkit({
 ```
 
 ```tsx title="ToolProvider.tsx"
-import { AuiProvider, Tools, useAui } from "@assistant-ui/react-native";
+import {
+  AuiConfig,
+  AuiProvider,
+  Tools,
+  useAui,
+} from "@assistant-ui/react-native";
 import toolkit from "./weather-toolkit";
 
 function ToolProvider({ children }: { children: React.ReactNode }) {
-  const aui = useAui({ tools: Tools({ toolkit }) });
-  return <AuiProvider value={aui}>{children}</AuiProvider>;
+  const aui = useAui();
+  const config = AuiConfig({ tools: Tools({ toolkit }) });
+  return (
+    <AuiProvider extends={aui} config={config}>
+      {children}
+    </AuiProvider>
+  );
 }
 ```
 
@@ -218,7 +228,7 @@ export function useMyToolToolkit(someOuterProp: string) {
 }
 ```
 
-Import the toolkit hook, pass its result to `useAui({ tools: Tools({ toolkit }) })`, and provide the returned `aui` with `AuiProvider`, as shown in the [Tools](#tools) section above.
+Import the toolkit hook, hoist `const aui = useAui()` and `const config = AuiConfig({ tools: Tools({ toolkit }) })` in the component body, and mount it with `<AuiProvider extends={aui} config={config}>`, as shown in the [Tools](#tools) section above.
 
 ### makeAssistantDataUI
 

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

@@ -69,7 +69,7 @@ export const maxDuration = 30;
 export async function POST(req: Request) {
   const { messages } = await req.json();
   const result = streamText({
-    model: openai("gpt-5.4-nano"),
+    model: openai("gpt-5.6-luna"),
     messages: await convertToModelMessages(messages),
   });
   return result.toUIMessageStreamResponse();
@@ -197,7 +197,7 @@ function Composer() {
     >
       <TextInput
         value={text}
-        onChangeText={(t) => aui.composer().setText(t)}
+        onChangeText={(t) => aui.composer.setText(t)}
         placeholder="Message..."
         multiline
         style={{
@@ -211,7 +211,7 @@ function Composer() {
         }}
       />
       <Pressable
-        onPress={() => aui.composer().send()}
+        onPress={() => aui.composer.send()}
         disabled={isEmpty}
         style={{
           marginLeft: 8,

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

@@ -31,7 +31,9 @@ Container `View` for the thread area.
 
 ### ThreadPrimitive.Messages
 
-`FlatList`-based message list with automatic runtime integration. Each message is wrapped in a scoped context so that `useAuiState((s) => s.message)` works inside the rendered component.
+Deprecated `FlatList`-based message list kept for backwards compatibility. It uses `ThreadPrimitive.MessagesFlatList` internally, but keeps the previous no-auto-scroll default so existing apps with custom scroll handling do not change behavior on upgrade.
+
+Use `ThreadPrimitive.MessagesFlatList` for new React Native threads.
 
 ```tsx
 <ThreadPrimitive.Messages>
@@ -53,7 +55,29 @@ You can also provide role-specific components:
 | Prop | Type | Description |
 |------|------|-------------|
 | `components` | `MessageComponents` | Component map — provide either a `Message` component (used for all roles) or role-specific `UserMessage`, `AssistantMessage`, and optionally `SystemMessage`. Edit composers can be set via `EditComposer` or role-specific variants (`UserEditComposer`, `AssistantEditComposer`, `SystemEditComposer`). |
-| `...rest` | `FlatListProps` | Standard FlatList props (except `data`, `renderItem`) |
+| `...rest` | `ThreadPrimitive.MessagesFlatList` props | Same props as `ThreadPrimitive.MessagesFlatList`, with the auto-scroll options defaulting to `false` on this deprecated wrapper |
+
+### ThreadPrimitive.MessagesFlatList
+
+Canonical React Native message viewport backed by `FlatList`. It scopes each row to its message, forwards refs to the underlying `FlatList`, and handles scroll-to-bottom behavior for common chat flows.
+
+```tsx
+<ThreadPrimitive.MessagesFlatList autoScroll>
+  {() => <MyMessage />}
+</ThreadPrimitive.MessagesFlatList>
+```
+
+| Prop | Type | Description |
+|------|------|-------------|
+| `children` | `({ message }) => ReactNode` | Render function for each message |
+| `components` | `MessageComponents` | Component map alternative to `children` |
+| `autoScroll` | `boolean` | Automatically keeps the list at the bottom while it is already near the bottom. Defaults to `true` |
+| `scrollToBottomOnRunStart` | `boolean` | Scrolls to the bottom when a run starts. Defaults to `true` |
+| `scrollToBottomOnInitialize` | `boolean` | Scrolls to the bottom when messages first appear. Defaults to `true` |
+| `scrollToBottomOnThreadSwitch` | `boolean` | Scrolls to the bottom when switching threads. Defaults to `true` |
+| `...rest` | `FlatListProps` | Standard FlatList props, except `data`, `renderItem`, and `children` |
+
+The built-in auto-scroll behavior assumes the default, non-inverted `FlatList` direction.
 
 ### ThreadPrimitive.MessageByIndex
 
@@ -413,7 +437,7 @@ Renders message content parts via a `components` prop. Tool call and data parts
 | `Reasoning` | `ReasoningMessagePartComponent` | Reasoning part renderer |
 | `Source` | `SourceMessagePartComponent` | Source part renderer |
 | `File` | `FileMessagePartComponent` | File part renderer |
-| `Unstable_Audio` | `AudioMessagePartComponent` | Audio part renderer (experimental) |
+| `Unstable_Audio` | `Unstable_AudioMessagePartComponent` | Audio part renderer (deprecated, render `audio/*` from `File`) |
 | `tools` | `{ by_name?, Fallback? }` or `{ Override }` | Tool call rendering config — use `by_name` to map tool names to components, `Fallback` for unregistered tools, or `Override` to handle all tool calls |
 | `data` | `{ by_name?, Fallback? }` | Data part rendering config — use `by_name` to map data event names, `Fallback` for unmatched events |
 | `Empty` | `EmptyMessagePartComponent` | Component shown for empty messages |
@@ -517,7 +541,7 @@ Container `View` for an attachment.
 
 ### AttachmentPrimitive.Thumb
 
-`Text` component displaying the file extension (e.g. `.pdf`).
+`Text` component displaying the file extension (e.g. `.pdf`), or the attachment type (e.g. `image`) when the filename has no extension (including leading-dot names like `.env`). If you pass `children`, they override that text.
 
 ```tsx
 <AttachmentPrimitive.Thumb style={styles.extension} />
@@ -541,10 +565,20 @@ import { ActionBarPrimitive } from "@assistant-ui/react-native";
 
 ### ActionBarPrimitive.Copy
 
-`Pressable` that copies the message content. Supports function-as-children for copy state feedback.
+`Pressable` that copies the message content. Pass a platform clipboard writer through `copyToClipboard`. Supports function-as-children for copy state feedback.
 
 ```tsx
-<ActionBarPrimitive.Copy copiedDuration={3000}>
+import * as Clipboard from "expo-clipboard";
+
+const copyToClipboard = async (text: string) => {
+  const didCopy = await Clipboard.setStringAsync(text);
+  if (!didCopy) throw new Error("Clipboard write failed");
+};
+
+<ActionBarPrimitive.Copy
+  copiedDuration={3000}
+  copyToClipboard={copyToClipboard}
+>
   {({ isCopied }) => <Text>{isCopied ? "Copied!" : "Copy"}</Text>}
 </ActionBarPrimitive.Copy>
 ```
@@ -552,7 +586,7 @@ import { ActionBarPrimitive } from "@assistant-ui/react-native";
 | Prop | Type | Description |
 |------|------|-------------|
 | `copiedDuration` | `number` | Duration in ms to show "copied" state (default: 3000) |
-| `copyToClipboard` | `(text: string) => void` | Custom clipboard function |
+| `copyToClipboard` | `(text: string) => void \| Promise<void>` | Platform clipboard writer |
 
 ### ActionBarPrimitive.Edit
 

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

@@ -11,9 +11,9 @@ import { VercelIcon } from "@/components/icons/vercel";
 
 | AI SDK | Runtime package | Docs |
 | --- | --- | --- |
-| `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@^7` + `@ai-sdk/react@^4` | `@assistant-ui/react-ai-sdk@^1.4` (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) |
 
 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.

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

@@ -11,9 +11,9 @@ AI SDK v4 is a legacy version. New projects should use [AI SDK v7](/docs/runtime
 
 ## Why legacy
 
-Vercel ships AI SDK majors roughly yearly; v4 is two majors behind v6. The current `@assistant-ui/react-ai-sdk` package targets v6+ 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/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.
 
-This page is reference for existing v4 projects. Plan to migrate to v6 when feasible.
+This page is reference for existing v4 projects. Plan to migrate to v7 when feasible.
 
 ## Setup
 
@@ -35,7 +35,7 @@ import { openai } from "@ai-sdk/openai";
 
 export async function POST(req: Request) {
   const { messages } = await req.json();
-  const result = streamText({ model: openai("gpt-5.4-nano"), messages });
+  const result = streamText({ model: openai("gpt-5.6-luna"), messages });
   return result.toDataStreamResponse();
 }
 ```
@@ -95,9 +95,9 @@ When you are ready to upgrade:
 
 AI SDK provides codemods at [ai-sdk.dev/docs/migration-guides](https://ai-sdk.dev/docs/migration-guides) that handle the package-side rewrites.
 
-## Alternative: react-ai-sdk@0.1.10
+## Alternative: react-ai-sdk@0.10.16
 
-An older release line of `@assistant-ui/react-ai-sdk` (0.1.10) supported AI SDK v4 directly. It is no longer maintained and has no upgrade path; if you are starting a new v4 project, use `@assistant-ui/react-data-stream` instead.
+An older release line of `@assistant-ui/react-ai-sdk` supported AI SDK v4 directly; its last release was `0.10.16`. It is no longer maintained and has no upgrade path; if you are starting a new v4 project, use `@assistant-ui/react-data-stream` instead.
 
 ## Related
 

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

@@ -6,12 +6,12 @@ description: Reference for projects still on AI SDK v5. New projects should use
 import { VercelIcon } from "@/components/icons/vercel";
 
 <Callout type="warn">
-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+.
+AI SDK v5 is a legacy version. New projects should use [AI SDK v7](/docs/runtimes/ai-sdk/v7). v5 users pin `@assistant-ui/react-ai-sdk@1.1.21` (the last v5-compatible release); later releases target newer AI SDK majors.
 </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.
+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 `1.1.21` keeps you on the v5-compatible surface.
 
 This page is reference for existing v5 projects. Plan to migrate to v7 when feasible.
 
@@ -22,7 +22,7 @@ This page is reference for existing v5 projects. Plan to migrate to v7 when feas
 
 ### Install v5-compatible versions
 
-<InstallCommand npm={["@assistant-ui/react", "@assistant-ui/react-ai-sdk@0.x", "ai@^5", "@ai-sdk/openai@^1", "zod"]} />
+<InstallCommand npm={["@assistant-ui/react", "@assistant-ui/react-ai-sdk@1.1.21", "ai@^5", "@ai-sdk/openai@^1", "zod"]} />
 
 </Step>
 <Step>
@@ -40,7 +40,7 @@ export const maxDuration = 30;
 export async function POST(req: Request) {
   const { messages }: { messages: Message[] } = await req.json();
   const result = streamText({
-    model: openai("gpt-5.4-nano"),
+    model: openai("gpt-5.6-luna"),
     messages,
     tools: {
       get_current_weather: tool({
@@ -98,7 +98,7 @@ const runtime = useVercelUseChatRuntime(chat);
 | Feature | v5 | v6 |
 | --- | --- | --- |
 | `ai` package | `ai@^5` | `ai@^6` |
-| `@assistant-ui/react-ai-sdk` | `@0.x` | `@latest` |
+| `@assistant-ui/react-ai-sdk` | `@1.1.21` | `@1.3.40` |
 | `@ai-sdk/openai` | `^1` | `^3` |
 | Message type | `Message` | `UIMessage` |
 | `convertToModelMessages` | Sync | Async (`await`) |