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

package/.docs/raw/docs/integrations/persistence/custom-adapter.mdx

@@ -305,7 +305,7 @@ export const threadListAdapter: RemoteThreadListAdapter = {
         async append() {},
         withFormat: (fmt) => ({
           async load() {
-            const { remoteId } = aui.threadListItem().getState();
+            const { remoteId } = aui.threadListItem.getState();
             if (!remoteId) return { messages: [] };
             const rows = await fetch(
               `/api/threads/${remoteId}/messages`,
@@ -322,7 +322,7 @@ export const threadListAdapter: RemoteThreadListAdapter = {
             };
           },
           async append(item) {
-            const { remoteId } = await aui.threadListItem().initialize();
+            const { remoteId } = await aui.threadListItem.initialize();
             await fetch(`/api/threads/${remoteId}/messages`, {
               method: "POST",
               body: JSON.stringify({
@@ -422,7 +422,7 @@ export const threadListAdapter: RemoteThreadListAdapter = {
         async append() {},
         withFormat: (fmt) => ({
           async load() {
-            const { remoteId } = aui.threadListItem().getState();
+            const { remoteId } = aui.threadListItem.getState();
             if (!remoteId) return { messages: [] };
             const rows = await fetch(
               `${API_URL}/threads/${remoteId}/messages`,
@@ -439,7 +439,7 @@ export const threadListAdapter: RemoteThreadListAdapter = {
             };
           },
           async append(item) {
-            const { remoteId } = await aui.threadListItem().initialize();
+            const { remoteId } = await aui.threadListItem.initialize();
             await fetch(`${API_URL}/threads/${remoteId}/messages`, {
               method: "POST",
               body: JSON.stringify({
@@ -541,7 +541,7 @@ export const threadListAdapter: RemoteThreadListAdapter = {
         async append() {},
         withFormat: (fmt) => ({
           async load() {
-            const { remoteId } = aui.threadListItem().getState();
+            const { remoteId } = aui.threadListItem.getState();
             if (!remoteId) return { messages: [] };
             const rows = await fetch(
               `${API_URL}/threads/${remoteId}/messages`,
@@ -558,7 +558,7 @@ export const threadListAdapter: RemoteThreadListAdapter = {
             };
           },
           async append(item) {
-            const { remoteId } = await aui.threadListItem().initialize();
+            const { remoteId } = await aui.threadListItem.initialize();
             await fetch(`${API_URL}/threads/${remoteId}/messages`, {
               method: "POST",
               body: JSON.stringify({
@@ -592,6 +592,32 @@ The top-level `load`/`append` on the history adapter are required by the type bu
 </Step>
 <Step>
 
+### Support in-place updates (optional)
+
+The optional `update(item, localMessageId)` method on the object returned from `withFormat` lets the runtime rewrite an already-persisted message in place. It receives the same `{ parentId, message }` item shape as `append`, plus the id of the row to rewrite.
+
+The runtime calls `update` after a run for persisted messages whose content changed, to finalize assistant messages persisted early while waiting for tool call approval, and to refresh run timing metadata.
+
+`update` is opt-in. When it is absent, messages paused for tool approval are not persisted until the run reaches a terminal status, so a page refresh during the pause loses the pending approval state. Implementing `update` enables early persistence.
+
+```tsx title="runtime/thread-adapter.tsx"
+async update(item, localMessageId) {
+  const { remoteId } = await aui.threadListItem.initialize();
+  await fetch(`${API_URL}/threads/${remoteId}/messages/${localMessageId}`, {
+    method: "PATCH",
+    body: JSON.stringify({
+      format: fmt.format,
+      content: fmt.encode(item),
+    }),
+  });
+},
+```
+
+The backend needs a matching update route keyed by message id, mirroring the append route from the earlier step.
+
+</Step>
+<Step>
+
 ### Mount the runtime
 
 Wrap the app in a `useRemoteThreadListRuntime` that delegates per-thread runtime to `useChatRuntime`:
@@ -694,7 +720,7 @@ Send a message in a fresh thread. Check the database:
 
 - The `threads` table has a new row with the current `userId`.
 - The `messages` table has at least two rows (user + assistant) for that thread.
-- `format` matches what `fmt.format` wrote (`"ai-sdk/v6"` for AI SDK v6) and `content` is the encoded `UIMessage` (a `role` plus `parts`), not a placeholder blob.
+- `format` matches what `fmt.format` wrote (`"ai-sdk/v6"`) and `content` is the encoded `UIMessage` (a `role` plus `parts`), not a placeholder blob. The format string names the stored `UIMessage` shape, not the installed AI SDK major; it stays `"ai-sdk/v6"` on AI SDK v7 and must never be renamed, or previously stored history stops matching.
 - Reload the page; the thread list and the messages survive.
 
 </Step>
@@ -702,9 +728,10 @@ Send a message in a fresh thread. Check the database:
 
 ## Notes
 
-- **First-message race.** `append` may fire before the thread row exists. The `unstable_Provider` example above always awaits `aui.threadListItem().initialize()` before writing; do the same in any custom implementation.
-- **Reload after async auth.** If `auth()` resolves after the initial `list()` call, threads won't appear until the user refreshes. Call `aui.threads().reload()` from a `useEffect` watching the session. Pattern is documented in [threads](/docs/runtimes/concepts/threads#reloading-after-async-authentication).
+- **First-message race.** `append` may fire before the thread row exists. The `unstable_Provider` example above always awaits `aui.threadListItem.initialize()` before writing; do the same in any custom implementation.
+- **Reload after async auth.** If `auth()` resolves after the initial `list()` call, threads won't appear until the user refreshes. Call `aui.threads.reload()` from a `useEffect` watching the session. Pattern is documented in [threads](/docs/runtimes/concepts/threads#reloading-after-async-authentication).
 - **Format string.** The `format` column is *not* a free-text label; it identifies the on-disk shape so multiple runtimes can coexist. Don't strip it. Don't make assumptions about its value (`useChatRuntime` is responsible for setting and decoding it).
+- **Pending approvals need `update`.** Tool call approvals persist across reloads only when the formatted adapter implements `update`; omitting it keeps the pre-approval snapshot out of storage by design.
 - **`unstable_Provider` synchronous-children rule.** The Provider must render `children` on first commit; do not gate them behind suspense, loading state, or `useEffect`. Load data inside an always-rendered child.
 
 ## Related

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

@@ -0,0 +1,156 @@
+---
+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(scopes); // extends the AuiProvider parent
+  return <AuiProvider value={aui}>{children}</AuiProvider>;
+};
+
+<AuiProvider value={parent}>
+  <Scoped />
+</AuiProvider>;
+```
+
+Where `{ parent: null }` was used to detach from context, `<AuiProvider value={null}>` now provides an isolated empty root (experimental).
+
+## 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/composer.mdx

@@ -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/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

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

@@ -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
 
@@ -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
 
@@ -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>
@@ -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`) |

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

@@ -4,7 +4,7 @@ description: Reference for projects still on AI SDK v6. New projects should use
 ---
 
 <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+.
+AI SDK v6 is a legacy version. New projects should use [AI SDK v7](/docs/runtimes/ai-sdk/v7). v6 users pin `@assistant-ui/react-ai-sdk@1.3.40` (the last v6-compatible release); later releases target v7.
 </Callout>
 
 Requires `ai@^6` and `@ai-sdk/react@^3`. For other versions see the [overview](/docs/runtimes/ai-sdk/overview).
@@ -52,17 +52,17 @@ npm init -y
 <PlatformTabs>
 <Tab value="React">
 
-<InstallCommand npm={["@assistant-ui/react", "@assistant-ui/react-ai-sdk", "ai@^6", "@ai-sdk/react@^3", "@ai-sdk/openai", "zod"]} />
+<InstallCommand npm={["@assistant-ui/react", "@assistant-ui/react-ai-sdk@1.3.40", "ai@^6", "@ai-sdk/react@^3", "@ai-sdk/openai", "zod"]} />
 
 </Tab>
 <Tab value="React Native">
 
-<InstallCommand expo={["@assistant-ui/react-native", "@assistant-ui/react-ai-sdk", "ai@^6", "@ai-sdk/react@^3", "@ai-sdk/openai", "zod"]} />
+<InstallCommand expo={["@assistant-ui/react-native", "@assistant-ui/react-ai-sdk@1.3.40", "ai@^6", "@ai-sdk/react@^3", "@ai-sdk/openai", "zod"]} />
 
 </Tab>
 <Tab value="React Ink">
 
-<InstallCommand npm={["@assistant-ui/react-ink", "@assistant-ui/react-ai-sdk", "ai@^6", "@ai-sdk/react@^3", "@ai-sdk/openai", "zod", "ink", "react"]} />
+<InstallCommand npm={["@assistant-ui/react-ink", "@assistant-ui/react-ai-sdk@1.3.40", "ai@^6", "@ai-sdk/react@^3", "@ai-sdk/openai", "zod", "ink", "react"]} />
 
 </Tab>
 </PlatformTabs>

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

@@ -3,7 +3,7 @@ title: AI SDK v7
 description: Integrate Vercel AI SDK v7 with assistant-ui for streaming chat.
 ---
 
-Current-version integration. Requires `ai@^7` and `@ai-sdk/react@^4`. For older versions see the [overview](/docs/runtimes/ai-sdk).
+Current-version integration. Requires `ai@^7` and `@ai-sdk/react@^4`. For older versions see the [overview](/docs/runtimes/ai-sdk/overview).
 
 ## Quickstart
 
@@ -601,7 +601,7 @@ Beyond transports and adapters, `useChatRuntime` accepts options that control th
 
 ### onThreadIdChange
 
-Called whenever the active thread's settled ID changes, e.g. to sync the active thread to a URL query param:
+Called whenever the runtime changes the active thread's settled ID, e.g. to sync the active thread to a URL query param. Changes supplied through the controlled `threadId` option are not echoed back through this callback.
 
 ```tsx
 const runtime = useChatRuntime({

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

@@ -149,7 +149,7 @@ const adapterWithHistory: RemoteThreadListAdapter = {
     const history = useMemo<ThreadHistoryAdapter>(
       () => ({
         async load() {
-          const { remoteId } = aui.threadListItem().getState();
+          const { remoteId } = aui.threadListItem.getState();
           if (!remoteId) return { messages: [] };
           const rows = await fetch(
             `/api/threads/${remoteId}/messages`,
@@ -157,7 +157,7 @@ const adapterWithHistory: RemoteThreadListAdapter = {
           return { messages: rows.map(toThreadMessage) };
         },
         async append({ message, parentId }) {
-          const { remoteId } = await aui.threadListItem().initialize();
+          const { remoteId } = await aui.threadListItem.initialize();
           await fetch(`/api/threads/${remoteId}/messages`, {
             method: "POST",
             body: JSON.stringify({ message, parentId }),
@@ -181,11 +181,11 @@ const adapterWithHistory: RemoteThreadListAdapter = {
 
 ### Avoiding the first-message race
 
-`append` may be called before the thread record exists in your backend. Always await `aui.threadListItem().initialize()` before writing:
+`append` may be called before the thread record exists in your backend. Always await `aui.threadListItem.initialize()` before writing:
 
 ```ts
 async append({ message, parentId }) {
-  const { remoteId } = await aui.threadListItem().initialize();
+  const { remoteId } = await aui.threadListItem.initialize();
   await saveMessage(remoteId, parentId, message);
 }
 ```
@@ -194,14 +194,14 @@ async append({ message, parentId }) {
 
 ### Reloading after async authentication
 
-If your adapter depends on a user that resolves asynchronously (oidc, `next-auth`, `better-auth`), the initial `list()` may run before the user is available. Call `aui.threads().reload()` after auth completes:
+If your adapter depends on a user that resolves asynchronously (oidc, `next-auth`, `better-auth`), the initial `list()` may run before the user is available. Call `aui.threads.reload()` after auth completes:
 
 ```tsx
 function ReloadOnAuth() {
   const aui = useAui();
   const { isLoading, user } = useAuth();
   useEffect(() => {
-    if (!isLoading && user) aui.threads().reload();
+    if (!isLoading && user) aui.threads.reload();
   }, [isLoading, user?.id]);
   return null;
 }
@@ -211,7 +211,7 @@ function ReloadOnAuth() {
 
 ### Paginating the thread list
 
-If your backend returns thread pages, return a `nextCursor` from `list()` and consume `aui.threads().hasMore` plus `aui.threads().loadMore()` in the UI. The runtime threads `params.after` back through `list()` on every `loadMore()`; the initial call passes no `params`, so treat a missing `after` as "first page". `reload()` resets the cursor so the next load starts from page 1 again.
+If your backend returns thread pages, return a `nextCursor` from `list()` and consume `aui.threads.hasMore` plus `aui.threads.loadMore()` in the UI. The runtime threads `params.after` back through `list()` on every `loadMore()`; the initial call passes no `params`, so treat a missing `after` as "first page". `reload()` resets the cursor so the next load starts from page 1 again.
 
 ```ts title="threadListAdapter.ts (excerpt)"
 async list({ after } = {}) {
@@ -271,7 +271,7 @@ A few invariants worth knowing when wiring a custom UI on top of `loadMore()`:
       name: "list",
       type: "(params?: { after?: string }) => Promise<{ threads: RemoteThreadMetadata[]; nextCursor?: string }>",
       description:
-        "Hydrate threads on mount. Each thread must include status and remoteId; title, externalId, and custom are optional. Return a `nextCursor` to enable `aui.threads().loadMore()`; the runtime will pass it back as `params.after` on the next call.",
+        "Hydrate threads on mount. Each thread must include status and remoteId; title, externalId, and custom are optional. Return a `nextCursor` to enable `aui.threads.loadMore()`; the runtime will pass it back as `params.after` on the next call.",
       required: true,
     },
     {
@@ -291,7 +291,7 @@ A few invariants worth knowing when wiring a custom UI on top of `loadMore()`:
       name: "updateCustom",
       type: "(remoteId: string, custom: Record<string, unknown> | undefined) => Promise<void>",
       description:
-        "Optional. Persist replacement custom metadata from `aui.threadListItem().updateCustom(custom)`.",
+        "Optional. Persist replacement custom metadata from `aui.threadListItem.updateCustom(custom)`.",
     },
     {
       name: "archive",
@@ -361,7 +361,7 @@ function ThreadListItemMeta() {
 }
 ```
 
-`custom` is preserved across `rename`, `archive`, `unarchive`, and `generateTitle`. To replace it from your UI, implement `RemoteThreadListAdapter.updateCustom` and call `aui.threadListItem().updateCustom(custom)`. The cloud adapter persists this through `cloud.threads.update(threadId, { metadata })`. If your adapter mutates thread metadata through a separate application path, return the updated values from `fetch()` or call `aui.threads().reload()` to re-run `list()`.
+`custom` is preserved across `rename`, `archive`, `unarchive`, and `generateTitle`. To replace it from your UI, implement `RemoteThreadListAdapter.updateCustom` and call `aui.threadListItem.updateCustom(custom)`. The cloud adapter persists this through `cloud.threads.update(threadId, { metadata })`. If your adapter mutates thread metadata through a separate application path, return the updated values from `fetch()` or call `aui.threads.reload()` to re-run `list()`.
 
 ## ExternalStoreThreadListAdapter
 

package/.docs/raw/docs/runtimes/custom/assistant-transport.mdx

@@ -536,8 +536,8 @@ function useResumeOnMount(threadId: string) {
         r.json(),
       );
       if (status.isRunning) {
-        const parentId = aui.thread().getState().messages.at(-1)?.id ?? null;
-        aui.thread().resumeRun({ parentId });
+        const parentId = aui.thread.getState().messages.at(-1)?.id ?? null;
+        aui.thread.resumeRun({ parentId });
       }
     })();
   }, [aui, threadId]);

package/.docs/raw/docs/runtimes/custom/external-store.mdx

@@ -741,7 +741,7 @@ useExternalStoreRuntime({
       name: "isSendDisabled",
       type: "boolean",
       description:
-        "Blocks new-message sending while leaving the input usable. When true, the thread composer's canSend becomes false, the Send button is disabled, Enter and the steer hotkey are no-ops, and aui.composer().send() short-circuits. Edit composers (saving message edits) ignore this flag. Use this to gate sending on external React state (e.g. while tools or auth are still loading).",
+        "Blocks new-message sending while leaving the input usable. When true, the thread composer's canSend becomes false, the Send button is disabled, Enter and the steer hotkey are no-ops, and aui.composer.send() short-circuits. Edit composers (saving message edits) ignore this flag. Use this to gate sending on external React state (e.g. while tools or auth are still loading).",
       default: "false",
     },
     {