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

package/.docs/raw/docs/copilots/assistant-frame.mdx

@@ -29,7 +29,10 @@ import { z } from "zod";
 const registry = new ModelContextRegistry();
 
 // Expose the registry to the parent window
-AssistantFrameProvider.addModelContextProvider(registry);
+AssistantFrameProvider.addModelContextProvider(
+  registry,
+  "https://parent-app.com",
+);
 
 // Add tools that will be available to the parent assistant
 registry.addTool({
@@ -70,7 +73,7 @@ function ParentComponent() {
   // Connect to the iframe's model context
   useAssistantFrameHost({
     iframeRef,
-    targetOrigin: "https://trusted-iframe-domain.com", // optional for increased security
+    targetOrigin: "https://trusted-iframe-domain.com",
   });
 
   return (
@@ -160,9 +163,15 @@ analyticsRegistry.addTool({
 
 // Register both providers
 const unsubscribe1 =
-  AssistantFrameProvider.addModelContextProvider(catalogRegistry);
+  AssistantFrameProvider.addModelContextProvider(
+    catalogRegistry,
+    "https://parent-app.com",
+  );
 const unsubscribe2 =
-  AssistantFrameProvider.addModelContextProvider(analyticsRegistry);
+  AssistantFrameProvider.addModelContextProvider(
+    analyticsRegistry,
+    "https://parent-app.com",
+  );
 
 // Later, unsubscribe if needed
 unsubscribe1();
@@ -173,7 +182,7 @@ unsubscribe2();
 
 #### Origin Validation
 
-Both the provider and host can specify allowed origins for security:
+Both the provider and host validate message origins. They default to the current page's origin, so cross-origin frames must specify the exact trusted origin on both sides:
 
 ```tsx
 // In iframe - only accept messages from specific parent
@@ -222,10 +231,12 @@ Registers a model context provider to share with parent windows.
 ```tsx
 const unsubscribe = AssistantFrameProvider.addModelContextProvider(
   registry,
-  "https://parent-domain.com", // Optional origin restriction
+  "https://parent-domain.com",
 );
 ```
 
+When `targetOrigin` is omitted, the provider only communicates with `window.location.origin`. All providers in a frame share one origin policy. Registering an explicit origin tightens an existing wildcard policy, while registering two different explicit origins throws an error. Unsubscribing drops that registration's requirement. The wildcard value `*` is available as an explicit opt-in, but it should not be used for contexts that expose tools or sensitive instructions.
+
 ##### `dispose()`
 
 Cleans up all resources and removes all providers.
@@ -243,7 +254,7 @@ Class that connects to an iframe's model context providers.
 ```tsx
 const host = new AssistantFrameHost(
   iframeWindow,
-  targetOrigin? // Optional origin restriction
+  targetOrigin?, // Defaults to window.location.origin
 );
 ```
 
@@ -283,7 +294,7 @@ React hook that manages the lifecycle of an AssistantFrameHost.
 ```tsx
 useAssistantFrameHost({
   iframeRef: RefObject<HTMLIFrameElement>,
-  targetOrigin?: string,
+  targetOrigin?: string, // Defaults to window.location.origin
 });
 ```
 

package/.docs/raw/docs/guides/attachments.mdx

@@ -4,7 +4,7 @@ description: Let users attach images, PDFs, and other files to AI chat messages
 platforms: ["react"]
 ---
 
-import { AttachmentSample } from "@/components/docs/samples/attachment";
+import { AttachmentSample } from "@/components/pages/docs/samples/attachment";
 
 Enable users to attach files to their messages, enhancing conversations with images, documents, and other content.
 
@@ -44,7 +44,7 @@ This adds `/components/assistant-ui/attachment.tsx` to your project.
 For `useChatRuntime`, attachments work automatically without additional configuration:
 
 ```tsx title="/app/MyRuntimeProvider.tsx"
-import { useChatRuntime } from "@assistant-ui/react-ai-sdk";
+import { useChatRuntime } from "@assistant-ui/ai-sdk";
 
 const runtime = useChatRuntime();
 ```

package/.docs/raw/docs/guides/branching.mdx

@@ -4,7 +4,7 @@ description: Edit messages or regenerate AI responses, then switch between alter
 platforms: ["react"]
 ---
 
-import { BranchingSample } from "@/components/docs/samples/branching";
+import { BranchingSample } from "@/components/pages/docs/samples/branching";
 
 Branching lets users navigate between alternative versions of a message. A new branch is created when:
 

package/.docs/raw/docs/guides/chatgpt-subscription.mdx

@@ -30,7 +30,7 @@ In your chat route, swap `@ai-sdk/openai` for the OAuth provider. Starting from
 
 ```ts title="/app/api/chat/route.ts" {10}
 import { createOpenAIOAuth } from "openai-oauth-provider";
-import { frontendTools } from "@assistant-ui/react-ai-sdk";
+import { frontendTools } from "@assistant-ui/ai-sdk";
 import {
   type JSONSchema7,
   streamText,

package/.docs/raw/docs/guides/dictation.mdx

@@ -4,7 +4,7 @@ description: Add voice dictation to your AI chat composer with the Web Speech AP
 platforms: ["react"]
 ---
 
-import { DictationSample } from "@/components/docs/samples/dictation";
+import { DictationSample } from "@/components/pages/docs/samples/dictation";
 
 assistant-ui supports speech-to-text (dictation) via the `DictationAdapter` interface. Users speak into the microphone and transcribed text lands in the composer, either as interim preview or as committed final text.
 

package/.docs/raw/docs/guides/electron.mdx

@@ -38,7 +38,7 @@ import { AssistantRuntimeProvider } from "@assistant-ui/react";
 import {
   AssistantChatTransport,
   useChatRuntime,
-} from "@assistant-ui/react-ai-sdk";
+} from "@assistant-ui/ai-sdk";
 
 const transport = new AssistantChatTransport({
   api: "https://api.example.com/chat",

package/.docs/raw/docs/guides/latex.mdx

@@ -4,7 +4,7 @@ description: Render LaTeX math expressions in AI chat messages with KaTeX — dr
 platforms: ["react"]
 ---
 
-import { PackageManagerTabs } from "@/components/docs/fumadocs/install/package-manager-tabs";
+import { PackageManagerTabs } from "@/components/pages/docs/fumadocs/install/package-manager-tabs";
 
 Render LaTeX mathematical expressions in chat messages using KaTeX.
 

package/.docs/raw/docs/guides/message-timing.mdx

@@ -100,7 +100,7 @@ Timing is tracked automatically on the client side by observing streaming state
 </Callout>
 
 ```tsx
-import { useChatRuntime } from "@assistant-ui/react-ai-sdk";
+import { useChatRuntime } from "@assistant-ui/ai-sdk";
 
 const runtime = useChatRuntime();
 // useMessageTiming() works out of the box
@@ -174,14 +174,20 @@ const runtime = useLangGraphRuntime({ stream: myStream });
 // useMessageTiming() works out of the box
 ```
 
-### AG-UI (`useAgUiThreadRuntime`)
+### AG-UI (`useAgUiRuntime`)
 
 Timing is tracked automatically on the client side by the AG-UI run aggregator. Each emitted message includes timing metadata computed from stream chunk observations.
 
 ```tsx
-import { useAgUiThreadRuntime } from "@assistant-ui/react-ag-ui";
-
-const runtime = useAgUiThreadRuntime({ runtimeUrl: "..." });
+import { useMemo } from "react";
+import { useAgUiRuntime } from "@assistant-ui/react-ag-ui";
+import { HttpAgent } from "@ag-ui/client";
+
+const agent = useMemo(
+  () => new HttpAgent({ url: "http://localhost:8000/agent" }),
+  [],
+);
+const runtime = useAgUiRuntime({ agent });
 // useMessageTiming() works out of the box
 ```
 

package/.docs/raw/docs/guides/quoting.mdx

@@ -4,7 +4,7 @@ description: Let users select text from AI messages and quote it back into the c
 platforms: ["react"]
 ---
 
-import { QuoteComposerSample } from "@/components/docs/samples/quote-composer";
+import { QuoteComposerSample } from "@/components/pages/docs/samples/quote-composer";
 
 <QuoteComposerSample />
 

package/.docs/raw/docs/guides/resumable-streams.mdx

@@ -84,7 +84,7 @@ The context exposes two more verbs: `ctx.status(streamId)` returns `"streaming"
 
 ## Client side: native integration
 
-`@assistant-ui/react-ai-sdk` ships a `resumable` option on `AssistantChatTransport`. It captures the stream id from the response header, redirects `chat.resumeStream()` reconnects to your resume route, and clears the stored id when the response finishes naturally. Pair it with `useChatRuntime`, which fires `chat.resumeStream()` whenever its resumable storage reports a pending id, including ids discovered after mount.
+`@assistant-ui/ai-sdk` ships a `resumable` option on `AssistantChatTransport`. It captures the stream id from the response header, redirects `chat.resumeStream()` reconnects to your resume route, and clears the stored id when the response finishes naturally. Pair it with `useChatRuntime`, which fires `chat.resumeStream()` whenever its resumable storage reports a pending id, including ids discovered after mount.
 
 ```tsx title="/app/page.tsx"
 "use client";
@@ -94,7 +94,7 @@ import {
   AssistantChatTransport,
   createResumableSessionStorage,
   useChatRuntime,
-} from "@assistant-ui/react-ai-sdk";
+} from "@assistant-ui/ai-sdk";
 import { useMemo } from "react";
 import { Thread } from "@/components/assistant-ui/thread";
 
@@ -153,7 +153,7 @@ import {
   AssistantChatTransport,
   createResumableSessionStorage,
   useChatRuntime,
-} from "@assistant-ui/react-ai-sdk";
+} from "@assistant-ui/ai-sdk";
 import { useMemo } from "react";
 import { Thread } from "@/components/assistant-ui/thread";
 import { ThreadList } from "@/components/assistant-ui/thread-list";

package/.docs/raw/docs/guides/speech.mdx

@@ -4,7 +4,7 @@ description: Read AI chat messages aloud with the Web Speech API or a custom TTS
 platforms: ["react"]
 ---
 
-import { SpeechSample } from "@/components/docs/samples/speech";
+import { SpeechSample } from "@/components/pages/docs/samples/speech";
 
 assistant-ui supports text-to-speech via the `SpeechSynthesisAdapter` interface. When a speech adapter is configured, users can trigger playback for any assistant message.
 

package/.docs/raw/docs/guides/suggestions.mdx

@@ -16,7 +16,7 @@ Configure suggestions using the `Suggestions()` API in your runtime provider:
 
 ```tsx
 import { AuiConfig, Tools, Suggestions } from "@assistant-ui/react";
-import { useChatRuntime } from "@assistant-ui/react-ai-sdk";
+import { useChatRuntime } from "@assistant-ui/ai-sdk";
 
 function MyRuntimeProvider({ children }: { children: React.ReactNode }) {
   const runtime = useChatRuntime();
@@ -218,7 +218,7 @@ They also accept the same `suggestion` adapter as the local runtime under `adapt
 
 ```tsx
 import { createSuggestionAdapter } from "@assistant-ui/react";
-import { useChatRuntime } from "@assistant-ui/react-ai-sdk";
+import { useChatRuntime } from "@assistant-ui/ai-sdk";
 
 const runtime = useChatRuntime({
   adapters: {

package/.docs/raw/docs/guides/voice.mdx

@@ -4,7 +4,7 @@ description: Build bidirectional voice conversations with AI in React. Realtime
 platforms: ["react"]
 ---
 
-import { VoiceSample } from "@/components/docs/samples/voice";
+import { VoiceSample } from "@/components/pages/docs/samples/voice";
 
 assistant-ui supports realtime bidirectional voice through the `RealtimeVoiceAdapter` interface. Users speak into their microphone, the agent answers with audio, and transcripts appear in the thread while the session runs.
 

package/.docs/raw/docs/ink/hooks.mdx

@@ -129,7 +129,7 @@ const runtime = useLocalRuntime(chatModel, {
 | `adapters.dictation` | `DictationAdapter` | Adapter for speech-to-text input |
 | `adapters.feedback` | `FeedbackAdapter` | Adapter for message feedback (thumbs up/down) |
 | `adapters.suggestion` | `SuggestionAdapter` | Adapter for suggested prompts |
-| `cloud` | `AssistantCloud` | Cloud instance for thread persistence via `@assistant-ui/cloud` |
+| `cloud` | `AssistantCloud` | Cloud instance for thread persistence via `assistant-cloud` |
 | `unstable_humanToolNames` | `string[]` | Tool names that pause the run until a result is added via `addResult` |
 
 ### useRemoteThreadListRuntime

package/.docs/raw/docs/ink/index.mdx

@@ -127,6 +127,7 @@ Use primitives to compose your terminal chat interface:
 ```tsx title="components/thread.tsx"
 import { Box, Text } from "ink";
 import {
+  AuiIf,
   ThreadPrimitive,
   ComposerPrimitive,
   LoadingPrimitive,
@@ -170,11 +171,11 @@ const StatusIndicator = () => (
 export const Thread = () => {
   return (
     <ThreadPrimitive.Root>
-      <ThreadPrimitive.Empty>
+      <AuiIf condition={(s) => s.thread.isEmpty}>
         <Box marginBottom={1}>
           <Text dimColor>No messages yet. Start typing below!</Text>
         </Box>
-      </ThreadPrimitive.Empty>
+      </AuiIf>
 
       <ThreadPrimitive.Messages>
         {() => <Message />}

package/.docs/raw/docs/ink/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** — `useLocalRuntime`, `ChatModelAdapter`, and all runtime options work identically.
-- **AI SDK integration** — `@assistant-ui/react-ai-sdk` works with React Ink. Your runtime setup transfers directly.
+- **AI SDK integration** — `@assistant-ui/ai-sdk` works with React Ink. Your runtime 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.

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

@@ -340,7 +340,7 @@ The shape of `content` matches the AI SDK part types. Use `image` for images and
 "use client";
 
 import { AssistantRuntimeProvider } from "@assistant-ui/react";
-import { useChatRuntime } from "@assistant-ui/react-ai-sdk";
+import { useChatRuntime } from "@assistant-ui/ai-sdk";
 import { attachmentAdapter } from "./attachment-adapter";
 
 export function MyProvider({ children }: { children: React.ReactNode }) {
@@ -363,7 +363,7 @@ import { AssistantRuntimeProvider } from "@assistant-ui/react-native";
 import {
   AssistantChatTransport,
   useChatRuntime,
-} from "@assistant-ui/react-ai-sdk";
+} from "@assistant-ui/ai-sdk";
 import { attachmentAdapter } from "./attachment-adapter";
 
 export function MyProvider({ children }: { children: React.ReactNode }) {
@@ -387,7 +387,7 @@ import { AssistantRuntimeProvider } from "@assistant-ui/react-ink";
 import {
   AssistantChatTransport,
   useChatRuntime,
-} from "@assistant-ui/react-ai-sdk";
+} from "@assistant-ui/ai-sdk";
 import { attachmentAdapter } from "./attachment-adapter";
 
 export function MyProvider({ children }: { children: React.ReactNode }) {

package/.docs/raw/docs/integrations/frameworks/ai-sdk.mdx

@@ -1,5 +1,5 @@
 ---
-title: Vercel AI SDK Integration
+title: Vercel AI SDK
 description: Wire the Vercel AI SDK into a React chat UI with assistant-ui — useChat, streaming, tools, attachments, multi-step agents, and persistence covered end-to-end.
 ---
 
@@ -16,14 +16,14 @@ If you arrived here looking to wire up your first chat: jump to [AI SDK v7 quick
 ```mermaid
 flowchart LR
     client["client"]
-    runtime["useChatRuntime (react-ai-sdk)<br/>(thread state · tool calls · attachments<br/>speech · dictation · feedback adapters)"]
+    runtime["useChatRuntime (ai-sdk)<br/>(thread state · tool calls · attachments<br/>speech · dictation · feedback adapters)"]
     api["/api/chat<br/>(streamText)"]
     provider["provider"]
 
     client --> runtime --> api --> provider
 ```
 
-`@assistant-ui/react-ai-sdk` wraps the AI SDK's `useChat` hook and exposes it as an assistant-ui runtime. The runtime owns conversation state on the client; your `/api/chat` route returns a UI message stream from `streamText`. Everything else (tools, attachments, observability, gateways, custom persistence) layers on top of this base.
+`@assistant-ui/ai-sdk` wraps the AI SDK's `useChat` hook and exposes it as an assistant-ui runtime. The runtime owns conversation state on the client; your `/api/chat` route returns a UI message stream from `streamText`. Everything else (tools, attachments, observability, gateways, custom persistence) layers on top of this base.
 
 ## Pick a version
 

package/.docs/raw/docs/integrations/frameworks/{cloudflare-agents/overview.mdx → cloudflare-agents.mdx}

@@ -1,6 +1,7 @@
 ---
-title: Cloudflare Agents Integration
+title: Cloudflare Agents
 description: Wire Cloudflare's stateful agent framework into a React chat UI with assistant-ui via the standard AI SDK runtime. WebSocket transport, server-side persistence, tool calling, all preserved.
+platforms: ["react"]
 ---
 
 import { CloudflareIcon } from "@/components/icons/cloudflare";
@@ -16,7 +17,7 @@ This is an integration guide, not a runtime adapter. assistant-ui does not ship
 
 Cloudflare Agents handles the server half: a Durable Object subclasses `AIChatAgent` from `@cloudflare/ai-chat`, owns the message history, and streams responses back over a WebSocket. `@cloudflare/ai-chat/react`'s `useAgentChat` hook wraps that WebSocket and exposes the same `messages`, `sendMessage`, `regenerate`, `status`, `stop`, `setMessages`, `addToolOutput` surface that the AI SDK's `useChat` does, plus a few Cloudflare-specific extras (`clearHistory`, `isServerStreaming`, `isToolContinuation`).
 
-assistant-ui handles the client half. `useAISDKRuntime` from [`@assistant-ui/react-ai-sdk`](/docs/runtimes/ai-sdk/v7) reads exactly those AI SDK methods off whatever you pass in, so feeding it `useAgentChat`'s return value yields a fully-featured runtime: streaming, tool calling, edit, reload, history import and export, attachments, suggestions.
+assistant-ui handles the client half. `useAISDKRuntime` from [`@assistant-ui/ai-sdk`](/docs/runtimes/ai-sdk/v7) reads exactly those AI SDK methods off whatever you pass in, so feeding it `useAgentChat`'s return value yields a fully-featured runtime: streaming, tool calling, edit, reload, history import and export, attachments, suggestions.
 
 Shared adapters (attachments, speech, feedback, history) work the same way as described in [adapters](/docs/runtimes/concepts/adapters). Multi-thread support needs a [custom thread list](/docs/runtimes/concepts/threads) wired around `useAISDKRuntime`; [AssistantCloud](/docs/cloud) integrates via `useChatRuntime` (which constructs its own `useChat` internally) and is not compatible with the `useAgentChat` wiring shown here.
 
@@ -198,7 +199,7 @@ In the frontend project:
 import { useAgent } from "agents/react";
 import { useAgentChat } from "@cloudflare/ai-chat/react";
 import { AssistantRuntimeProvider } from "@assistant-ui/react";
-import { useAISDKRuntime } from "@assistant-ui/react-ai-sdk";
+import { useAISDKRuntime } from "@assistant-ui/ai-sdk";
 import { Thread } from "@/components/assistant-ui/thread";
 
 export const Assistant = () => {

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

@@ -19,7 +19,7 @@ This is an integration guide, not a runtime adapter. assistant-ui does not ship
 | [Full-stack](/docs/integrations/frameworks/mastra/full-stack) | One Next.js app: API routes call Mastra in-process. Simpler deployment, single repo. |
 | [Separate server](/docs/integrations/frameworks/mastra/separate-server) | Mastra runs as its own service; the Next.js frontend hits its API. Independent scaling, clearer separation of concerns. |
 
-Both use the same client-side `useChatRuntime` from [`@assistant-ui/react-ai-sdk`](/docs/runtimes/ai-sdk/v7). The only difference is where the Mastra agent lives.
+Both use the same client-side `useChatRuntime` from [`@assistant-ui/ai-sdk`](/docs/runtimes/ai-sdk/v7). The only difference is where the Mastra agent lives.
 
 ## Architecture
 

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

@@ -129,7 +129,7 @@ Open the file containing `useChatRuntime` (typically `app/assistant.tsx`) and pa
 "use client";
 
 import { AssistantRuntimeProvider } from "@assistant-ui/react";
-import { AssistantChatTransport, useChatRuntime } from "@assistant-ui/react-ai-sdk";
+import { AssistantChatTransport, useChatRuntime } from "@assistant-ui/ai-sdk";
 import { Thread } from "@/components/assistant-ui/thread";
 
 export const Assistant = () => {

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

@@ -11,7 +11,7 @@ import { LangChainIcon } from "@/components/icons/langchain";
 import { McpIcon } from "@/components/icons/mcp";
 import { VercelIcon } from "@/components/icons/vercel";
 
-Integrations are wiring guides for using third-party services with assistant-ui, plus canonical recipes for the adapter slots (persistence, attachments). They are distinct from [runtimes](/docs/runtimes/pick-a-runtime), which are the React adapter packages (`@assistant-ui/react-ai-sdk`, `@assistant-ui/react-langgraph`, etc.) that connect the UI to a backend. An integration assumes you already have a working runtime and adds something on top.
+Integrations are wiring guides for using third-party services with assistant-ui, plus canonical recipes for the adapter slots (persistence, attachments). They are distinct from [runtimes](/docs/runtimes/pick-a-runtime), which are the React adapter packages (`@assistant-ui/ai-sdk`, `@assistant-ui/react-langgraph`, etc.) that connect the UI to a backend. An integration assumes you already have a working runtime and adds something on top.
 
 ## Where integrations slot in
 
@@ -40,7 +40,7 @@ Framework integrations that pair with assistant-ui at the API-route layer.
       icon={<CloudflareIcon width={20} height={20} />}
       title="Cloudflare Agents"
       description="Stateful Durable Object agents. Wired through the AI SDK runtime with WebSocket streaming."
-      href="/docs/integrations/frameworks/cloudflare-agents/overview"
+      href="/docs/integrations/frameworks/cloudflare-agents"
     />
     <Card
       icon={<MastraIcon width={20} height={20} />}

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

@@ -650,7 +650,7 @@ import {
   AssistantRuntimeProvider,
   useRemoteThreadListRuntime,
 } from "@assistant-ui/react";
-import { useChatRuntime } from "@assistant-ui/react-ai-sdk";
+import { useChatRuntime } from "@assistant-ui/ai-sdk";
 import { threadListAdapter } from "./thread-adapter";
 
 export function MyProvider({ children }: { children: React.ReactNode }) {
@@ -677,7 +677,7 @@ import {
 import {
   AssistantChatTransport,
   useChatRuntime,
-} from "@assistant-ui/react-ai-sdk";
+} from "@assistant-ui/ai-sdk";
 import { threadListAdapter } from "./thread-adapter";
 
 export function MyProvider({ children }: { children: React.ReactNode }) {
@@ -707,7 +707,7 @@ import {
 import {
   AssistantChatTransport,
   useChatRuntime,
-} from "@assistant-ui/react-ai-sdk";
+} from "@assistant-ui/ai-sdk";
 import { threadListAdapter } from "./thread-adapter";
 
 export function MyProvider({ children }: { children: React.ReactNode }) {

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

@@ -16,7 +16,7 @@ Use a toolkit registered with `Tools({ toolkit })` instead. Toolkits keep the mo
 
 ```tsx
 import { AssistantRuntimeProvider, makeAssistantTool } from "@assistant-ui/react";
-import { useChatRuntime } from "@assistant-ui/react-ai-sdk";
+import { useChatRuntime } from "@assistant-ui/ai-sdk";
 import { z } from "zod";
 
 const WeatherTool = makeAssistantTool({
@@ -76,7 +76,7 @@ import {
   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 App() {

package/.docs/raw/docs/primitives/action-bar.mdx

@@ -4,7 +4,7 @@ description: Build message action buttons with auto-hide, copy state, and intell
 platforms: ["react"]
 ---
 
-import { ActionBarPrimitiveSample } from "@/components/docs/samples/action-bar-primitive";
+import { ActionBarPrimitiveSample } from "@/components/pages/docs/samples/action-bar-primitive";
 import { ActionBarPrimitive as ActionBarPrimitiveDocs } from "@/generated/primitiveDocs";
 
 The ActionBar primitive provides message actions: copy, reload, edit, feedback, speech, and export. It handles intelligent visibility with auto-hide on hover, automatic disabling based on message state, and floating behavior. You compose the buttons; the primitive handles action state and availability.

package/.docs/raw/docs/primitives/assistant-modal.mdx

@@ -4,7 +4,7 @@ description: A floating chat popover with a fixed-position trigger button that o
 platforms: ["react"]
 ---
 
-import { AssistantModalSample } from "@/components/docs/samples/assistant-modal";
+import { AssistantModalSample } from "@/components/pages/docs/samples/assistant-modal";
 import { AssistantModalPrimitive as AssistantModalPrimitiveDocs } from "@/generated/primitiveDocs";
 
 The AssistantModal primitive is a floating chat popover built on [Radix Popover](https://www.radix-ui.com/primitives/docs/components/popover). A trigger button opens a chat panel, which is a common floating assistant launcher pattern. You control the trigger, content, positioning, and animations.

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

@@ -4,7 +4,7 @@ description: File and image attachment rendering for the composer and messages.
 platforms: ["react"]
 ---
 
-import { AttachmentSample } from "@/components/docs/samples/attachment";
+import { AttachmentSample } from "@/components/pages/docs/samples/attachment";
 
 The Attachment primitive renders file and image attachments. It appears in two places: inside the composer for pending uploads (with a remove button), and inside messages for sent attachments (read-only). You provide the layout and styling.
 

package/.docs/raw/docs/primitives/branch-picker.mdx

@@ -4,7 +4,7 @@ description: Navigate between message branches, which are alternative responses
 platforms: ["react"]
 ---
 
-import { BranchPickerPrimitiveSample } from "@/components/docs/samples/branch-picker-primitive";
+import { BranchPickerPrimitiveSample } from "@/components/pages/docs/samples/branch-picker-primitive";
 import { BranchPickerPrimitive as BranchPickerPrimitiveDocs } from "@/generated/primitiveDocs";
 
 The BranchPicker primitive lets users navigate between message branches, which are alternative responses generated by editing a message or regenerating a reply. It's used alongside ActionBar inside message components.

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

@@ -4,9 +4,9 @@ description: Collapsible accordion for grouping reasoning steps and tool calls.
 platforms: ["react"]
 ---
 
-import { ChainOfThoughtPrimitiveSample } from "@/components/docs/samples/chain-of-thought-primitive";
-import { ChainOfThoughtPrimitiveSample as ChainOfThoughtPrimitiveSampleRadix } from "@/components/docs/samples/chain-of-thought-primitive.radix";
-import { Flavored } from "@/components/docs/contexts/flavor.server";
+import { ChainOfThoughtPrimitiveSample } from "@/components/pages/docs/samples/chain-of-thought-primitive";
+import { ChainOfThoughtPrimitiveSample as ChainOfThoughtPrimitiveSampleRadix } from "@/components/pages/docs/samples/chain-of-thought-primitive.radix";
+import { Flavored } from "@/components/pages/docs/contexts/flavor.server";
 import {
   ChainOfThoughtPrimitive as ChainOfThoughtPrimitiveDocs,
   MessagePrimitive as MessagePrimitiveDocs,

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

@@ -4,7 +4,7 @@ description: Build custom message input UIs with full control over layout and be
 platforms: ["react"]
 ---
 
-import { ComposerPrimitiveSample } from "@/components/docs/samples/composer-primitive";
+import { ComposerPrimitiveSample } from "@/components/pages/docs/samples/composer-primitive";
 import { ComposerPrimitive as ComposerPrimitiveDocs } from "@/generated/primitiveDocs";
 
 The Composer primitive is the interface for composing new messages or editing existing ones. It handles submit behavior, keyboard shortcuts, focus management, attachment state, and streaming status. You provide the UI.

package/.docs/raw/docs/primitives/error.mdx

@@ -4,7 +4,7 @@ description: Accessible error display for messages with automatic error text ext
 platforms: ["react"]
 ---
 
-import { ErrorPrimitiveSample } from "@/components/docs/samples/error-primitive";
+import { ErrorPrimitiveSample } from "@/components/pages/docs/samples/error-primitive";
 
 The Error primitive renders error states on messages using an accessible `role="alert"` container with automatic error text extraction. `Root` always renders its container; `Message` only renders when the message has an error. Wrap in `MessagePrimitive.Error` if you need the entire block to be conditional.
 

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

@@ -4,7 +4,7 @@ description: Build custom message rendering with content parts, attachments, and
 platforms: ["react"]
 ---
 
-import { MessagePrimitiveSample } from "@/components/docs/samples/message-primitive";
+import { MessagePrimitiveSample } from "@/components/pages/docs/samples/message-primitive";
 import { MessagePrimitive as MessagePrimitiveDocs } from "@/generated/primitiveDocs";
 
 The Message primitive handles individual message rendering: content parts, attachments, quotes, hover state, and error display. It's the building block inside each message bubble, resolving text, images, tool calls, and more through a parts pipeline.

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

@@ -4,7 +4,7 @@ description: A floating toolbar that appears when text is selected within a mess
 platforms: ["react"]
 ---
 
-import { SelectionToolbarPrimitiveSample } from "@/components/docs/samples/selection-toolbar-primitive";
+import { SelectionToolbarPrimitiveSample } from "@/components/pages/docs/samples/selection-toolbar-primitive";
 
 The SelectionToolbar primitive is a floating toolbar that appears when the user selects text within a message. It lets users quote selected text into the composer. Styling and action layout are fully customizable.
 

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

@@ -4,7 +4,7 @@ description: Suggested prompts that users can click to quickly send or populate
 platforms: ["react"]
 ---
 
-import { SuggestionPrimitiveSample } from "@/components/docs/samples/suggestion-primitive";
+import { SuggestionPrimitiveSample } from "@/components/pages/docs/samples/suggestion-primitive";
 import { SuggestionPrimitive as SuggestionPrimitiveDocs } from "@/generated/primitiveDocs";
 
 The Suggestion primitive renders suggested prompts as clickable pills that send a message or populate the composer. Use it for welcome screen suggestions, follow-up prompts, or quick actions. You provide the layout and styling.

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

@@ -4,7 +4,7 @@ description: Multi-thread management for listing, creating, switching, archiving
 platforms: ["react"]
 ---
 
-import { ThreadListPrimitiveSample } from "@/components/docs/samples/thread-list-primitive";
+import { ThreadListPrimitiveSample } from "@/components/pages/docs/samples/thread-list-primitive";
 import { ThreadListPrimitive as ThreadListPrimitiveDocs, ThreadListItemPrimitive as ThreadListItemPrimitiveDocs, ThreadListItemMorePrimitive as ThreadListItemMorePrimitiveDocs } from "@/generated/primitiveDocs";
 
 The ThreadList primitive manages multiple conversations by listing threads, creating new ones, switching between them, and archiving or deleting old ones. It's composed from three primitive namespaces: `ThreadListPrimitive`, `ThreadListItemPrimitive`, and `ThreadListItemMorePrimitive`.

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

@@ -4,7 +4,7 @@ description: Build custom scrollable message containers with auto-scroll, empty
 platforms: ["react"]
 ---
 
-import { ThreadPrimitiveSample } from "@/components/docs/samples/thread-primitive";
+import { ThreadPrimitiveSample } from "@/components/pages/docs/samples/thread-primitive";
 import { ThreadPrimitive as ThreadPrimitiveDocs } from "@/generated/primitiveDocs";
 
 The Thread primitive is the scrollable message container, and the backbone of any chat interface. It handles viewport management, auto-scrolling, empty states, message rendering, and suggestions. You provide the layout and styling.

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

@@ -15,7 +15,7 @@ The simplest way to add persistence. Pass a `cloud` option to `useLocalRuntime`:
 
 ```tsx
 import { useLocalRuntime } from "@assistant-ui/react-native";
-import { AssistantCloud } from "@assistant-ui/cloud";
+import { AssistantCloud } from "assistant-cloud";
 
 const cloud = new AssistantCloud({
   baseUrl: "https://backend.assistant-ui.com",

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

@@ -49,7 +49,7 @@ If you prefer to add assistant-ui to an existing Expo project, follow these step
 
 ### Install dependencies
 
-<InstallCommand expo={["@assistant-ui/react-native", "@assistant-ui/react-ai-sdk"]} />
+<InstallCommand expo={["@assistant-ui/react-native", "@assistant-ui/ai-sdk"]} />
 
   </Step>
   <Step>
@@ -120,7 +120,7 @@ export async function POST(req: Request) {
 ### Set up the runtime
 
 ```tsx title="hooks/use-app-runtime.ts"
-import { useChatRuntime, AssistantChatTransport } from "@assistant-ui/react-ai-sdk";
+import { useChatRuntime, AssistantChatTransport } from "@assistant-ui/ai-sdk";
 
 const API_URL = process.env.EXPO_PUBLIC_API_URL ?? "http://localhost:3000";