@assistant-ui/mcp-docs-server 0.1.30 → 0.1.31

package/.docs/raw/docs/(reference)/api-reference/primitives/index.mdx

@@ -0,0 +1,65 @@
+---
+title: Overview
+description: Generated API reference for assistant-ui React primitive namespaces and parts.
+---
+
+{/* AUTO-GENERATED by scripts/generate-api-reference-overviews.mts */}
+{/* Do not edit manually. */}
+
+Primitives are the composable React components exported from `@assistant-ui/react`. These pages focus on parts, props, rendered elements, and composition behavior.
+
+## Pages
+
+<Cards>
+  <Card title={"ActionBarPrimitive"} href={"/docs/api-reference/primitives/action-bar"}>
+    {"Buttons for message actions like copy, edit, reload, speak, and feedback."}
+  </Card>
+  <Card title={"ActionBarMorePrimitive"} href={"/docs/api-reference/primitives/action-bar-more"}>
+    {"API reference for ActionBarMorePrimitive."}
+  </Card>
+  <Card title={"AuiIf"} href={"/docs/api-reference/primitives/assistant-if"}>
+    {"Conditional rendering component based on thread, message, or composer state."}
+  </Card>
+  <Card title={"AssistantModalPrimitive"} href={"/docs/api-reference/primitives/assistant-modal"}>
+    {"A popover chat interface for floating assistant UI in the corner of the screen."}
+  </Card>
+  <Card title={"AttachmentPrimitive"} href={"/docs/api-reference/primitives/attachment"}>
+    {"Components for displaying and managing file attachments in messages and composer."}
+  </Card>
+  <Card title={"BranchPickerPrimitive"} href={"/docs/api-reference/primitives/branch-picker"}>
+    {"Navigate between conversation branches with previous/next controls."}
+  </Card>
+  <Card title={"ComposerPrimitive"} href={"/docs/api-reference/primitives/composer"}>
+    {"Primitives for the text input, send button, and attachments."}
+  </Card>
+  <Card title={"ErrorPrimitive"} href={"/docs/api-reference/primitives/error"}>
+    {"Components for displaying error messages in the chat interface."}
+  </Card>
+  <Card title={"MessagePrimitive"} href={"/docs/api-reference/primitives/message"}>
+    {"Components for rendering message content, parts, and attachments."}
+  </Card>
+  <Card title={"MessagePartPrimitive"} href={"/docs/api-reference/primitives/message-part"}>
+    {"Primitives for text, images, tool calls, and other message content."}
+  </Card>
+  <Card title={"SelectionToolbarPrimitive"} href={"/docs/api-reference/primitives/selection-toolbar"}>
+    {"A floating toolbar that appears when text is selected within a message."}
+  </Card>
+  <Card title={"SuggestionPrimitive"} href={"/docs/api-reference/primitives/suggestion"}>
+    {"API reference for SuggestionPrimitive."}
+  </Card>
+  <Card title={"ThreadPrimitive"} href={"/docs/api-reference/primitives/thread"}>
+    {"Primitives for the message list, viewport, and welcome screen."}
+  </Card>
+  <Card title={"ThreadListPrimitive"} href={"/docs/api-reference/primitives/thread-list"}>
+    {"Display and manage multiple conversation threads with create and archive actions."}
+  </Card>
+  <Card title={"ThreadListItemPrimitive"} href={"/docs/api-reference/primitives/thread-list-item"}>
+    {"Individual thread item with title, archive, and delete controls."}
+  </Card>
+  <Card title={"ThreadListItemMorePrimitive"} href={"/docs/api-reference/primitives/thread-list-item-more"}>
+    {"Dropdown menu for additional thread actions like archive and delete."}
+  </Card>
+  <Card title={"Composition"} href={"/docs/api-reference/primitives/composition"}>
+    {"How to compose primitives with custom components using asChild."}
+  </Card>
+</Cards>

package/.docs/raw/docs/(reference)/api-reference/primitives/message.mdx

@@ -3,6 +3,8 @@ title: MessagePrimitive
 description: Components for rendering message content, parts, and attachments.
 ---
 
+import { MessagePrimitive as MessagePrimitiveDocs } from "@/generated/primitiveDocs";
+
 A single message in a conversation. Messages may consist of multiple parts.
 
 
@@ -95,13 +97,13 @@ The content of the message. This renders a separate component for each message p
               name: "Reasoning",
               type: "ReasoningMessagePartComponent",
               description:
-                "The component to render for each reasoning message part. Cannot be used alongside ChainOfThought.",
+                "Deprecated components-map renderer for each reasoning message part. Prefer the children render function or MessagePrimitive.GroupedParts.",
             },
             {
               name: "tools",
               type: "object",
               description:
-                "Configuration for tool call rendering. Cannot be used alongside ChainOfThought.",
+                "Deprecated components-map configuration for tool call rendering. Prefer part.toolUI in the children render function or MessagePrimitive.GroupedParts.",
               children: [
                 {
                   parameters: [
@@ -155,7 +157,7 @@ The content of the message. This renders a separate component for each message p
               name: "ToolGroup",
               type: "ComponentType<PropsWithChildren<{ startIndex: number; endIndex: number }>>",
               description:
-                "Deprecated: This feature is still experimental and subject to change. Component for rendering grouped consecutive tool calls. When provided, consecutive tool-call message parts will be automatically grouped and wrapped with this component. Cannot be used alongside ChainOfThought.",
+                "Deprecated legacy wrapper for grouped consecutive tool calls. Prefer MessagePrimitive.GroupedParts with groupBy returning \"group-tool\".",
               children: [
                 {
                   type: "ToolGroupProps",
@@ -187,7 +189,7 @@ The content of the message. This renders a separate component for each message p
               name: "ReasoningGroup",
               type: "ReasoningGroupComponent",
               description:
-                "Component for rendering grouped consecutive reasoning parts. Cannot be used alongside ChainOfThought.",
+                "Deprecated legacy wrapper for grouped consecutive reasoning parts. Prefer MessagePrimitive.GroupedParts with groupBy returning \"group-reasoning\".",
               children: [
                 {
                   type: "ReasoningGroupProps",
@@ -219,7 +221,7 @@ The content of the message. This renders a separate component for each message p
               name: "ChainOfThought",
               type: "ComponentType",
               description:
-                "When set, groups all consecutive reasoning and tool-call parts into a single collapsible component. Mutually exclusive with Reasoning, tools, ToolGroup, and ReasoningGroup.",
+                "Deprecated legacy grouping path. Prefer MessagePrimitive.GroupedParts for grouped reasoning and tool calls.",
             },
             {
               name: "Empty",
@@ -400,9 +402,51 @@ type QuoteInfo = {
 See the [Quoting guide](/docs/guides/quoting) for a complete walkthrough.
 </Callout>
 
+### GroupedParts
+
+Renders adjacent message parts through a hierarchical grouping tree. Use this for grouped Chain of Thought, consecutive tool calls, or any other adjacent grouping where each part stays in chronological order.
+
+```tsx
+<MessagePrimitive.GroupedParts
+  groupBy={(part) => {
+    if (part.type === "reasoning")
+      return ["group-chainOfThought", "group-reasoning"];
+    if (part.type === "tool-call")
+      return ["group-chainOfThought", "group-tool"];
+    return null;
+  }}
+>
+  {({ part, children }) => {
+    switch (part.type) {
+      case "group-chainOfThought":
+        return <div>{children}</div>;
+      case "group-reasoning":
+        return <ReasoningRoot>{children}</ReasoningRoot>;
+      case "group-tool":
+        return <ToolGroupRoot>{children}</ToolGroupRoot>;
+      case "text":
+        return <MarkdownText />;
+      case "reasoning":
+        return <Reasoning {...part} />;
+      case "tool-call":
+        return part.toolUI ?? <ToolFallback {...part} />;
+      case "data":
+        return part.dataRendererUI;
+      default:
+        return null;
+    }
+  }}
+</MessagePrimitive.GroupedParts>
+```
+
+<ParametersTable
+  type="MessagePrimitiveGroupedPartsProps"
+  parameters={MessagePrimitiveDocs.GroupedParts.props}
+/>
+
 ### Unstable_PartsGrouped
 
-Renders the parts of a message grouped by a custom grouping function. Use this component when you need to visually group related message parts together — for example, grouping parts that share a common parent ID, or collecting consecutive tool calls under a single header.
+Renders the parts of a message grouped by a custom grouping function. Use this unstable API only when you need non-adjacent clustering, such as collecting parts that share a common parent ID across different positions. For adjacent grouping, prefer `MessagePrimitive.GroupedParts`.
 
 The `groupingFunction` prop controls how parts are grouped. It receives the full array of message parts and must return an array of group descriptors, each with a `groupKey` (or `undefined` for ungrouped parts) and an array of `indices` into the message parts array. The optional `components.Group` component is then rendered once per group and receives the `groupKey`, `indices`, and the rendered part children.
 

package/.docs/raw/docs/(reference)/api-reference/primitives/thread-list.mdx

@@ -124,3 +124,18 @@ Renders a single thread list item at the specified index.
     },
   ]}
 />
+
+### LoadMore
+
+A button that calls `aui.threads().loadMore()` to append the next page. See the [LoadMore primitive reference](/docs/primitives/thread-list#loadmore) for usage and [Threads concepts](/docs/runtimes/concepts/threads#paginating-the-thread-list) for the adapter contract.
+
+This primitive renders a `<button>` element unless `asChild` is set.
+
+<ParametersTable
+  type="ThreadListPrimitiveLoadMoreProps"
+  parameters={[
+    {
+      name: "asChild",
+    },
+  ]}
+/>

package/.docs/raw/docs/(reference)/api-reference/primitives/thread.mdx

@@ -67,6 +67,33 @@ This primitive renders a `<div>` element unless `asChild` is set.
       description:
         'Controls scroll anchoring behavior for new messages. "bottom" is the classic chat behavior where messages anchor at the bottom. "top" anchors new user messages at the top of the viewport for a focused reading experience.',
     },
+    {
+      name: "topAnchorMessageClamp",
+      type: '{ tallerThan?: string; visibleHeight?: string }',
+      default: '{ tallerThan: "10em", visibleHeight: "6em" }',
+      description:
+        'Clamps tall user messages so the assistant response stays in view when turnAnchor is "top". Messages up to `tallerThan` stay fully visible; taller messages show only `visibleHeight` of their bottom edge above the assistant response.',
+      children: [
+        {
+          type: '{ tallerThan?: string; visibleHeight?: string }',
+          parameters: [
+            {
+              name: "tallerThan",
+              type: "string",
+              default: '"10em"',
+              description: "Clamp messages taller than this CSS length.",
+            },
+            {
+              name: "visibleHeight",
+              type: "string",
+              default: '"6em"',
+              description:
+                "Visible portion of a clamped message's bottom edge.",
+            },
+          ],
+        },
+      ],
+    },
     {
       name: "scrollToBottomOnRunStart",
       type: "boolean",
@@ -90,9 +117,17 @@ This primitive renders a `<div>` element unless `asChild` is set.
   ]}
 />
 
+<Callout type="info">
+  `ThreadPrimitive.ViewportSlack` has been removed. When `turnAnchor="top"` is
+  set, `MessagePrimitive.Root` handles top-anchor registration automatically. If
+  you previously customized `fillClampThreshold` or `fillClampOffset` on
+  `ViewportSlack` or `MessagePrimitive.Root`, use `topAnchorMessageClamp`
+  instead.
+</Callout>
+
 ### ViewportFooter
 
-A footer container placed inside `ThreadPrimitive.Viewport` that measures its own height (including top margin) and reports it to the viewport context. The viewport uses this measurement in scroll calculations — for example, as the minimum height for `ViewportSlack` — so that the scroll-to-bottom behaviour accounts for any sticky footer overlapping the message list.
+A footer container placed inside `ThreadPrimitive.Viewport` that measures its own height (including top margin) and reports it to the viewport context. The viewport uses this measurement in scroll calculations so the scroll-to-bottom behaviour accounts for any sticky footer overlapping the message list.
 
 Multiple `ViewportFooter` components may be used; their heights are summed.
 

package/.docs/raw/docs/(reference)/api-reference/runtimes/index.mdx

@@ -0,0 +1,38 @@
+---
+title: Overview
+description: Runtime action and state references used by useAui and useAuiState.
+---
+
+{/* AUTO-GENERATED by scripts/generate-api-reference-overviews.mts */}
+{/* Do not edit manually. */}
+
+Runtime state pages document the objects exposed through `useAui` and `useAuiState`. Use this section when you need to control assistant-ui programmatically or inspect the exact state available in a context.
+
+## Pages
+
+<Cards>
+  <Card title={"AssistantRuntime"} href={"/docs/api-reference/runtimes/assistant-runtime"}>
+    {"Root runtime for managing threads, tool UIs, and assistant state."}
+  </Card>
+  <Card title={"AttachmentRuntime"} href={"/docs/api-reference/runtimes/attachment-runtime"}>
+    {"Hooks for accessing attachment state in composer and messages."}
+  </Card>
+  <Card title={"ComposerRuntime"} href={"/docs/api-reference/runtimes/composer-runtime"}>
+    {"Runtime for programmatically controlling the message composer."}
+  </Card>
+  <Card title={"MessagePartRuntime"} href={"/docs/api-reference/runtimes/message-part-runtime"}>
+    {"Hook for accessing message part state within parts."}
+  </Card>
+  <Card title={"MessageRuntime"} href={"/docs/api-reference/runtimes/message-runtime"}>
+    {"Hooks for accessing message state and edit composer."}
+  </Card>
+  <Card title={"ThreadListItemRuntime"} href={"/docs/api-reference/runtimes/thread-list-item-runtime"}>
+    {"Runtime for managing individual thread list items."}
+  </Card>
+  <Card title={"ThreadListRuntime"} href={"/docs/api-reference/runtimes/thread-list-runtime"}>
+    {"Runtime for accessing and managing the list of threads."}
+  </Card>
+  <Card title={"ThreadRuntime"} href={"/docs/api-reference/runtimes/thread-runtime"}>
+    {"Runtime for thread state, messages, and viewport management."}
+  </Card>
+</Cards>

package/.docs/raw/docs/(reference)/api-reference/runtimes/thread-list-runtime.mdx

@@ -22,6 +22,9 @@ await aui.threads().switchToThread(threadId);
 // (e.g. after async auth completes)
 await aui.threads().reload();
 
+// Append the next page of threads when the adapter returned a `nextCursor`
+await aui.threads().loadMore();
+
 // Access the main thread runtime
 const mainThread = aui.threads().main;
 
@@ -51,6 +54,8 @@ import { useAuiState } from "@assistant-ui/react";
 
 const threads = useAuiState((s) => s.threads.threadIds);
 const isLoading = useAuiState((s) => s.threads.isLoading);
+const hasMore = useAuiState((s) => s.threads.hasMore);
+const isLoadingMore = useAuiState((s) => s.threads.isLoadingMore);
 ```
 
 <ParametersTable {...ThreadListState} />

package/.docs/raw/docs/(reference)/migrations/v0-14.mdx

@@ -1,8 +1,139 @@
 ---
 title: Migration to v0.14
-description: Primitives migrate from components prop to children render functions.
+description: Drops APIs deprecated since v0.11/v0.12, and primitives migrate from components prop to children render functions.
 ---
 
+Version 0.14 finishes deprecation cycles started in v0.11 and v0.12, and replaces the `components` prop on primitives with a children render function pattern. If your app is on v0.13 and free of deprecation warnings, the only required change is the children API migration.
+
+## Automatic Migration
+
+The codemod that ships with the CLI handles the v0.12 hook renames (`useAssistantApi` → `useAui`, etc.) which are also removed in v0.14:
+
+```bash
+npx assistant-ui@latest upgrade
+```
+
+The other removals listed below are simple renames you can apply with find-and-replace.
+
+## Hook Aliases Removed
+
+These thin aliases existed only for backwards compatibility:
+
+| Removed                              | Replacement                  |
+| ------------------------------------ | ---------------------------- |
+| `useAssistantApi`                    | `useAui`                     |
+| `useAssistantState`                  | `useAuiState`                |
+| `useAssistantEvent`                  | `useAuiEvent`                |
+| `AssistantIf`                        | `AuiIf`                      |
+| `useLocalThreadRuntime`              | `useLocalRuntime`            |
+| `unstable_useRemoteThreadListRuntime`| `useRemoteThreadListRuntime` |
+| `unstable_useCloudThreadListAdapter` | `useCloudThreadListAdapter`  |
+| `unstable_RemoteThreadListAdapter`   | `RemoteThreadListAdapter`    |
+| `unstable_InMemoryThreadListAdapter` | `InMemoryThreadListAdapter`  |
+
+## Runtime API Cleanups
+
+### `AssistantRuntime`
+
+| Removed                                  | Replacement                               |
+| ---------------------------------------- | ----------------------------------------- |
+| `runtime.threadList`                     | `runtime.threads`                         |
+| `runtime.switchToNewThread()`            | `runtime.threads.switchToNewThread()`     |
+| `runtime.switchToThread(id)`             | `runtime.threads.switchToThread(id)`      |
+| `runtime.registerModelConfigProvider(p)` | `runtime.registerModelContextProvider(p)` |
+| `runtime.reset({ initialMessages })`     | `runtime.thread.reset(initialMessages)`   |
+
+### `ThreadRuntime`
+
+| Removed                                    | Replacement                         |
+| ------------------------------------------ | ----------------------------------- |
+| `thread.startRun(parentId)` (positional)   | `thread.startRun({ parentId })`     |
+| `thread.unstable_resumeRun(config)`        | `thread.resumeRun(config)`          |
+| `thread.unstable_loadExternalState(state)` | `thread.importExternalState(state)` |
+| `thread.getModelConfig()`                  | `thread.getModelContext()`          |
+
+### `MessageState` / `MessageRuntime`
+
+The duplicate top-level `submittedFeedback` field has been removed. It has always been mirrored from `message.metadata.submittedFeedback`, which remains the source of truth:
+
+```tsx
+// Before
+useAuiState((s) => s.message.submittedFeedback);
+
+// After
+useAuiState((s) => s.message.metadata.submittedFeedback);
+```
+
+### `ChatModelRunOptions`
+
+If you wrote a custom `ChatModelAdapter`, the legacy alias `options.config` (which mirrored `options.context`) is gone:
+
+```ts
+// Before
+const adapter: ChatModelAdapter = {
+  async run({ messages, config }) {
+    /* config.tools, config.config, ... */
+  },
+};
+
+// After
+const adapter: ChatModelAdapter = {
+  async run({ messages, context }) {
+    /* context.tools, context.config, ... */
+  },
+};
+```
+
+## External Store Helpers
+
+`getExternalStoreMessage` (singular) has been removed. Use `getExternalStoreMessages` (plural), which always returns an array — even when only one source message is bound:
+
+```ts
+// Before
+const original = getExternalStoreMessage<MyMessage>(threadMessage);
+
+// After
+const [original] = getExternalStoreMessages<MyMessage>(threadMessage);
+```
+
+## Assistant Transport Helpers
+
+`toAISDKTools` and `getEnabledTools` (re-exported from `@assistant-ui/react`) have been removed. Both wrapped functionality that's now exposed directly by `assistant-stream`:
+
+```ts
+// Before
+import { toAISDKTools } from "@assistant-ui/react";
+const schemas = toAISDKTools(tools);
+
+// After
+import { toToolsJSONSchema } from "assistant-stream";
+const schemas = toToolsJSONSchema(tools);
+```
+
+`toToolsJSONSchema` filters out `disabled` and `backend` tools by default. To replicate the old `toAISDKTools` behavior exactly (include all tools regardless), pass `{ filter: () => true }`.
+
+## react-langgraph
+
+`useLangGraphRuntime`'s `onSwitchToThread` option has been removed. Use `load`, which has the same signature plus an optional `AbortSignal`:
+
+```ts
+// Before
+useLangGraphRuntime({
+  stream,
+  onSwitchToThread: async (threadId) => {
+    return await fetchThread(threadId);
+  },
+});
+
+// After
+useLangGraphRuntime({
+  stream,
+  load: async (threadId, { signal } = {}) => {
+    return await fetchThread(threadId, { signal });
+  },
+});
+```
+
 ## Children API for Primitives
 
 Version 0.14 replaces the `components` prop on primitives with a children render function pattern. This gives you full control over rendering with simple inline logic.
@@ -150,10 +281,17 @@ When using the children API, tool-call parts include `addResult` and `resume` me
 
 The `components` prop is still supported on all primitives but is deprecated and will be removed in a future version.
 
-## Getting Help
+## Still Deprecated (not removed)
+
+Some APIs marked `@deprecated` are intentionally kept for one more release to give downstream runtimes time to migrate:
+
+- `ThreadState.threadId` and `ThreadState.metadata` — use `useThreadListItem()` (see [v0.12 guide](/docs/migrations/v0-12)). Will be removed in a future minor release.
+- Legacy context hooks under `legacy-runtime/hooks/*` (`useThreadRuntime`, `useMessageRuntime`, etc.) — replaced by `useAui()` / `useAuiState()` in v0.12. The codemod migrates these.
+- Primitive `If` components (`ThreadIf`, `MessageIf`, `ComposerIf`, `ThreadEmpty`) — replaced by `AuiIf`. The codemod migrates these.
 
-If you encounter issues during migration:
+You'll continue to see deprecation warnings on these; expect removal in a future minor release.
+
+## Getting Help
 
-1. Check the updated API documentation for detailed examples
-2. Review the example applications in the repository
-3. Report issues at https://github.com/assistant-ui/assistant-ui/issues
+- File issues at https://github.com/assistant-ui/assistant-ui/issues
+- See the [deprecation policy](/docs/migrations/deprecation-policy) for the support window