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

package/.docs/organized/code-examples/with-tanstack.md

@@ -65,11 +65,11 @@
     "@assistant-ui/react": "workspace:*",
     "@assistant-ui/react-markdown": "workspace:*",
     "@tailwindcss/vite": "^4.3.3",
-    "@tanstack/react-router": "^1.170.21",
-    "@tanstack/react-start": "^1.168.38",
+    "@tanstack/react-router": "^1.170.27",
+    "@tanstack/react-start": "^1.168.44",
     "class-variance-authority": "^0.7.1",
     "clsx": "^2.1.1",
-    "lucide-react": "^1.29.0",
+    "lucide-react": "^1.31.0",
     "nitro": "^3.0.260311-beta",
     "openai": "^7.4.0",
     "react": "^19.2.8",
@@ -81,7 +81,7 @@
   },
   "devDependencies": {
     "@assistant-ui/x-buildutils": "workspace:*",
-    "@types/node": "^26.1.2",
+    "@types/node": "^26.2.0",
     "@types/react": "^19.2.18",
     "@types/react-dom": "^19.2.4",
     "@vitejs/plugin-react": "^6.0.5",
@@ -463,7 +463,7 @@ export const chatStream = createServerFn({ method: "POST" })
     });
 
     const stream = await openai.chat.completions.create({
-      model: "gpt-5.4-nano",
+      model: "gpt-5.6-luna",
       messages: data.messages,
       stream: true,
     });

package/.docs/organized/code-examples/with-tap-runtime.md

@@ -600,7 +600,7 @@ export default withAui(nextConfig);
     "@assistant-ui/ui": "workspace:*",
     "class-variance-authority": "^0.7.1",
     "clsx": "^2.1.1",
-    "lucide-react": "^1.29.0",
+    "lucide-react": "^1.31.0",
     "next": "^16.3.0",
     "react": "^19.2.8",
     "react-dom": "^19.2.8",
@@ -610,7 +610,7 @@ export default withAui(nextConfig);
     "@assistant-ui/next": "workspace:*",
     "@assistant-ui/x-buildutils": "workspace:*",
     "@tailwindcss/postcss": "^4.3.3",
-    "@types/node": "^26.1.2",
+    "@types/node": "^26.2.0",
     "@types/react": "^19.2.18",
     "@types/react-dom": "^19.2.4",
     "postcss": "^8.5.26",

package/.docs/organized/code-examples/with-virtualized-thread.md

@@ -600,7 +600,7 @@ export default withAui(nextConfig);
     "@tanstack/react-virtual": "^3.14.9",
     "class-variance-authority": "^0.7.1",
     "clsx": "^2.1.1",
-    "lucide-react": "^1.29.0",
+    "lucide-react": "^1.31.0",
     "next": "^16.3.0",
     "react": "^19.2.8",
     "react-dom": "^19.2.8",
@@ -610,7 +610,7 @@ export default withAui(nextConfig);
     "@assistant-ui/next": "workspace:*",
     "@assistant-ui/x-buildutils": "workspace:*",
     "@tailwindcss/postcss": "^4.3.3",
-    "@types/node": "^26.1.2",
+    "@types/node": "^26.2.0",
     "@types/react": "^19.2.18",
     "@types/react-dom": "^19.2.4",
     "postcss": "^8.5.26",

package/.docs/organized/code-examples/with-vue.md

@@ -18,7 +18,7 @@
     "@assistant-ui/store": "workspace:*",
     "@assistant-ui/tap": "workspace:*",
     "@assistant-ui/vue": "workspace:*",
-    "@lucide/vue": "^1.29.0",
+    "@lucide/vue": "^1.31.0",
     "vue": "^3.5.41"
   },
   "devDependencies": {

package/.docs/raw/docs/(docs)/cli.mdx

@@ -78,6 +78,7 @@ Use `--example` to create a project from one of the monorepo examples with full
 | `with-chain-of-thought` | Chain-of-thought reasoning, tool calls, and source citations | `npx assistant-ui create my-app -e with-chain-of-thought` |
 | `with-external-store` | External message store | `npx assistant-ui create my-app -e with-external-store` |
 | `with-interactables` | AI-driven interactive UI components | `npx assistant-ui create my-app -e with-interactables` |
+| `with-openui` | [OpenUI](/docs/tools/openui) generative UI integration | `npx assistant-ui create my-app -e with-openui` |
 | `with-custom-thread-list` | Custom thread list UI | `npx assistant-ui create my-app -e with-custom-thread-list` |
 | `with-react-hook-form` | React Hook Form integration | `npx assistant-ui create my-app -e with-react-hook-form` |
 | `with-ffmpeg` | FFmpeg video processing tool | `npx assistant-ui create my-app -e with-ffmpeg` |
@@ -233,11 +234,15 @@ This command:
 - Prompts to install new packages
 
 **What it does:**
-- Applies all available codemods sequentially
+- Applies the current bundled codemods sequentially
 - Shows progress bar with file count
 - Reports any transformation errors
 - Automatically detects and offers to install new dependencies
 
+The latest upgrade excludes the historical v0.8 UI package split because its
+`@assistant-ui/react-ui` destination is incompatible with current runtime versions.
+Do not run `codemod v0-8/ui-package-split` as part of a v0.15 upgrade.
+
 **Example output:**
 
 ```bash

package/.docs/raw/docs/(docs)/installation.mdx

@@ -467,8 +467,8 @@ export default function MyApp() {
   />
   <Card
     title="Generative UI"
-    description="Create rich UI components for tool executions"
-    href="/docs/tools/tool-ui"
+    description="Let the model compose UI from a component vocabulary you ship"
+    href="/docs/tools/generative-ui"
   />
   <Card
     title="Add Persistence"

package/.docs/raw/docs/(reference)/api-reference/generative-ui/slack.mdx

@@ -63,7 +63,11 @@ The blocks and non-fatal warnings produced by Slack conversion.
 
 ### SlackConversionWarning
 
-A non-fatal downgrade reported during Slack conversion.
+A non-fatal note reported during Slack conversion.
+
+`clamped` removed content to fit a limit, `dropped` discarded a node or one
+of its props and may leave a placeholder note behind, and `fallback` emitted
+the node in a different form than requested.
 
 <ParametersTable {...SlackConversionWarning} />
 

package/.docs/raw/docs/(reference)/api-reference/generative-ui/teams.mdx

@@ -50,14 +50,21 @@ The attachments and non-fatal warnings produced by [toTeamsAttachments](/docs/ap
 
 ### TeamsConversionWarning
 
-A non-fatal downgrade reported during Teams conversion.
+A non-fatal note reported during Teams conversion.
+
+`clamped` removed content to fit a limit, `dropped` discarded a node or one
+of its props and may leave a placeholder note behind, and `fallback`
+emitted the node in a different form than requested. `advisory` changed
+nothing at all and notes content Teams may still render poorly or refuse,
+such as a payload over the byte budget or a `Row` past the recommended
+column count.
 
 <ParametersTable {...TeamsConversionWarning} />
 
 ### toAdaptiveCard
 
 Converts a generative-ui tree into a Microsoft Teams Adaptive Card and
-non-fatal downgrade warnings. Sizes, weights, and colors map to Adaptive
+non-fatal conversion warnings. Sizes, weights, and colors map to Adaptive
 Card's semantic enums rather than raw values. An Input/Select/RadioGroup/
 Checkbox/DatePicker whose id would be the reserved RESERVED_INPUT_ID
 is renamed with a warning (see `decodeSubmitData`). Never throws: an

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

@@ -33,7 +33,7 @@ function QuoteBlock() {
 ```
 
 ```ts
-const useMessageQuote: () => QuoteInfo;
+const useMessageQuote: () => QuoteInfo | undefined;
 ```
 
 ### useMessageTiming
@@ -51,7 +51,7 @@ function MessageStats() {
 ```
 
 ```ts
-const useMessageTiming: () => MessageTiming;
+const useMessageTiming: () => MessageTiming | undefined;
 ```
 
 ### useRuntimeAdapters

package/.docs/raw/docs/(reference)/api-reference/integrations/eve.mdx

@@ -36,7 +36,7 @@ Converts an assistant-ui append message into the message payload accepted by
 Eve's `send` API.
 
 ```ts
-const getEveMessageContent: (message: AppendMessage) => NonNullable<SendTurnPayload["message"]>;
+const getEveMessageContent: (message: AppendMessage) => EveMessageContent;
 ```
 
 ### toEveInputResponse
@@ -56,4 +56,42 @@ session, supports cancellation, and maps Eve input requests to assistant-ui
 tool approval UI.
 
 <ParametersTable {...eve_useEveAgentRuntime} />
+
+### useEveError
+
+Read the last Eve session error from the runtime extras.
+
+```ts
+const useEveError: () => Error | undefined;
+```
+
+### useEveEvents
+
+Read the authoritative Eve server event stream from the runtime extras.
+Defaults to an empty array outside an Eve runtime.
+
+```ts
+const useEveEvents: () => EveRuntimeExtras["events"];
+```
+
+### useEveReset
+
+Returns a function that resets the Eve session: aborts any in-flight turn,
+recreates the owned session, and clears events and projected data. Pending
+staged messages and tool execution state are discarded. Safe to render
+outside an Eve runtime; invoking the returned function there throws.
+
+```ts
+const useEveReset: () => () => void;
+```
+
+### useEveSession
+
+Read the current Eve session cursor from the runtime extras. Persist it to
+resume the session later via `initialSession`. `undefined` when no session
+exists yet or outside an Eve runtime.
+
+```ts
+const useEveSession: () => EveRuntimeExtras["session"] | undefined;
+```
 {/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/integrations/react-ai-sdk.mdx

@@ -3,7 +3,7 @@ title: "@assistant-ui/react-ai-sdk"
 description: Vercel AI SDK runtime hooks, chat transports, and message conversion utilities for assistant-ui React applications.
 ---
 
-import { reactAiSdk_AISDKToolkit, reactAiSdk_AssistantChatTransport, reactAiSdk_createResumableSessionStorage, reactAiSdk_getThreadMessageTokenUsage, reactAiSdk_injectQuoteContext, reactAiSdk_unstable_injectInteractableContext, reactAiSdk_useAISDKRuntime, reactAiSdk_useChatRuntime } from "@/generated/integrationTypeDocs";
+import { reactAiSdk_AISDKChat, reactAiSdk_AISDKThreads, reactAiSdk_AISDKToolkit, reactAiSdk_AssistantChatTransport, reactAiSdk_createResumableSessionStorage, reactAiSdk_getThreadMessageTokenUsage, reactAiSdk_injectQuoteContext, reactAiSdk_unstable_injectInteractableContext, reactAiSdk_useAISDKRuntime, reactAiSdk_useChatRuntime } from "@/generated/integrationTypeDocs";
 
 {/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
 {/* Do not edit manually. */}
@@ -14,6 +14,31 @@ import { reactAiSdk_AISDKToolkit, reactAiSdk_AssistantChatTransport, reactAiSdk_
 
 ## API Reference
 
+### AISDKChat
+
+`AuiConfig` entry that runs the AI SDK chat as the `threads` scope. Hosts the
+same orchestration as `useChatRuntime` inside the client's own resource tree,
+so it works with any `AssistantClient` host, React or not. Single thread; the
+multi-thread and assistant-cloud surface is [AISDKThreads](/docs/api-reference/integrations/react-ai-sdk#aisdkthreads). The chat
+id is captured when the entry mounts, so a later `id` change in the options
+has no effect.
+
+<ParametersTable {...reactAiSdk_AISDKChat} />
+
+### AISDKThreads
+
+`AuiConfig` entry that runs one AI SDK chat per thread. Hosts the same
+per-thread orchestration as [AISDKChat](/docs/api-reference/integrations/react-ai-sdk#aisdkchat) inside the client's own
+resource tree, so it works with any `AssistantClient` host, React or not.
+Without `cloud`, threads live in memory for the client's lifetime and keep
+their history across switches; each thread's chat id is its thread id.
+With `cloud`, the list is a `RemoteThreadList` and the factory is keyed so
+cloud history reloads on a switch. The store entry mounts only the visible
+thread, so a switch cancels an in-flight run. Model context is
+registered on the visible thread only.
+
+<ParametersTable {...reactAiSdk_AISDKThreads} />
+
 ### AISDKToolkit
 
 <ParametersTable {...reactAiSdk_AISDKToolkit} />
@@ -109,7 +134,7 @@ runtime hook. `undefined` when the current thread is not backed by the AI
 SDK runtime.
 
 ```ts
-const useAISDKChat: <UI_MESSAGE extends UIMessage = UIMessage<unknown, UIDataTypes, UITools>>() => UseChatHelpers<UI_MESSAGE>;
+const useAISDKChat: <UI_MESSAGE extends UIMessage = UIMessage<unknown, UIDataTypes, UITools>>() => UseChatHelpers<UI_MESSAGE> | undefined;
 ```
 
 ### useAISDKError
@@ -119,7 +144,7 @@ Read the last AI SDK chat error object from the runtime extras.
 the AI SDK runtime.
 
 ```ts
-const useAISDKError: () => Error;
+const useAISDKError: () => Error | undefined;
 ```
 
 ### useAISDKRuntime
@@ -133,7 +158,7 @@ const useAISDKError: () => Error;
 ### useThreadTokenUsage
 
 ```ts
-function useThreadTokenUsage(): ThreadTokenUsage;
+function useThreadTokenUsage(): ThreadTokenUsage | undefined;
 ```
 
 ### generativeTools

package/.docs/raw/docs/(reference)/api-reference/tools/status.mdx

@@ -57,6 +57,6 @@ function ToolDuration() {
 ```
 
 ```ts
-const useToolCallElapsed: () => number;
+const useToolCallElapsed: () => number | undefined;
 ```
 {/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/utilities/miscellaneous.mdx

@@ -3,7 +3,7 @@ title: Utilities
 description: Miscellaneous @assistant-ui/react utilities for custom rendering, composition, and advanced assistant UI behavior.
 ---
 
-import { AssistantCloud, AuiConfig, ChainOfThoughtClient, DevToolsHooks, InMemoryThreadList, SingleThreadList, Suggestions, useSmooth } from "@/generated/typeDocs";
+import { AssistantCloud, AuiConfig, ChainOfThoughtClient, DevToolsHooks, InMemoryThreadList, MessageNotSentError, RemoteThreadList, SingleThreadList, Suggestions, useSmooth } from "@/generated/typeDocs";
 
 {/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
 {/* Do not edit manually. */}
@@ -59,6 +59,34 @@ const createMessageQueue: (driver: MessageQueueDriver) => MessageQueueController
 
 <ParametersTable {...InMemoryThreadList} />
 
+### isMessageNotSentError
+
+```ts
+const isMessageNotSentError: (error: unknown) => error is MessageNotSentError;
+```
+
+### MessageNotSentError
+
+Rejection reason for a send that never reached the backend, so nothing ran
+and nothing is recoverable from the thread. A runtime adapter throws it from
+`onNew` to hand the message back to the thread composer, which restores the
+draft it cleared at dispatch time when nothing has claimed the composer
+since. An edit composer closes at dispatch, so a rejected edit is not
+restored.
+
+<ParametersTable {...MessageNotSentError} />
+
+### RemoteThreadList
+
+`AuiConfig` `threads` entry backed by a `RemoteThreadListAdapter`. Thread
+bodies are born from the `thread` factory inside the client tree, so any
+`AssistantClient` host can run a remote or cloud list. Per-thread history
+and attachments come from `unstable_useAdapters`. `useRemoteThreadListRuntime`
+uses the same hook when `unstable_Provider` is omitted. Key the factory
+with `withKey` so history reloads when the visible thread changes.
+
+<ParametersTable {...RemoteThreadList} />
+
 ### SingleThreadList
 
 <ParametersTable {...SingleThreadList} />

package/.docs/raw/docs/(reference)/api-reference/voice/session.mdx

@@ -31,7 +31,7 @@ const useVoiceControls: () => { connect: () => void; disconnect: () => void; mut
 ### useVoiceState
 
 ```ts
-const useVoiceState: () => VoiceSessionState;
+const useVoiceState: () => VoiceSessionState | undefined;
 ```
 
 ### useVoiceVolume

package/.docs/raw/docs/cloud/ai-sdk-assistant-ui.mdx

@@ -19,7 +19,7 @@ This integration provides:
 
 ## How It Works
 
-The `useChatRuntime` hook from `@assistant-ui/react-ai-sdk` wraps AI SDK's `useChat` and adds cloud persistence via the `cloud` parameter. The runtime automatically:
+The `useChatRuntime` hook from `@assistant-ui/react-ai-sdk` wraps AI SDK's `useChat` and adds cloud persistence via the `cloud` parameter. `AISDKThreads({ cloud })` is the store-entry list for `AuiConfig` / `createAssistantClient` hosts. That host mounts only the visible thread, so a switch cancels an in-flight run. The runtime automatically:
 
 1. Creates a cloud thread on the first user message
 2. Persists messages as they complete streaming

package/.docs/raw/docs/cloud/ai-sdk.mdx

@@ -332,7 +332,7 @@ Plus all other properties from AI SDK's [`UseChatHelpers`](https://sdk.vercel.ai
 | Value | Type | Description |
 |-------|------|-------------|
 | `threads.cloud` | `AssistantCloud` | The cloud instance used for thread operations |
-| `threads.threads` | `CloudThread[]` | Active threads sorted by recency |
+| `threads.threads` | `CloudThread[]` | Threads sorted by recency; includes archived threads when supplied by `useThreads({ includeArchived: true })` |
 | `threads.threadId` | `string \| null` | Current thread ID (`null` for a new unsaved chat) |
 | `threads.selectThread` | `(id: string \| null) => void` | Switch threads or pass `null` for a new chat |
 | `threads.isLoading` | `boolean` | `true` during initial load or refresh |
@@ -378,7 +378,7 @@ The `useCloudChat` hook automatically reports run telemetry to Assistant Cloud a
 **Requires route configuration:**
 - `model_id` — The model used for the response
 - `input_tokens` / `output_tokens` — Token usage statistics
-- `reasoning_tokens` — Tokens used for chain-of-thought reasoning (e.g. GPT-5.4 Mini or GPT-5.5 models)
+- `reasoning_tokens` — Tokens used for chain-of-thought reasoning (e.g. GPT-5.6 Luna or other reasoning models)
 - `cached_input_tokens` — Input tokens served from the provider's prompt cache
 
 To capture model and usage data, configure the `messageMetadata` callback in your AI SDK route:

package/.docs/raw/docs/cloud/index.mdx

@@ -16,7 +16,7 @@ Assistant Cloud is a hosted service that adds thread management, message persist
 
 | Backend | Standalone Mode | With assistant-ui |
 |---------|----------------|-------------------|
-| AI SDK | [`useCloudChat`](/docs/cloud/ai-sdk) | [`useChatRuntime`](/docs/cloud/ai-sdk-assistant-ui) |
+| AI SDK | [`useCloudChat`](/docs/cloud/ai-sdk) | [`useChatRuntime`](/docs/cloud/ai-sdk-assistant-ui) / `AISDKThreads` |
 | LangGraph | — | [`useLangGraphRuntime`](/docs/cloud/langgraph) |
 | Custom | — | Local Runtime |
 

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

@@ -118,7 +118,7 @@ Build your own adapters for specialized file handling. Below are complete exampl
 
 ### Vision-Capable Image Adapter
 
-Send images to vision-capable LLMs like GPT-5.4, Claude Sonnet 4.6, or Gemini Pro Vision:
+Send images to vision-capable LLMs like GPT-5.6, Claude Sonnet 4.6, or Gemini Pro Vision:
 
 ```tsx
 import {
@@ -276,7 +276,7 @@ const MyModelAdapter: ChatModelAdapter = {
         msg.role === "user" &&
         msg.content.some((part) => part.type === "image")
       ) {
-        // Format for GPT-5.4 or similar vision models
+        // Format for GPT-5.6 or similar vision models
         return {
           role: "user",
           content: msg.content.map((part) => {

package/.docs/raw/docs/guides/context-api.mdx

@@ -519,34 +519,32 @@ The table below covers the most commonly used actions. For the full catalog, see
 
 ### Events vs State Observation
 
-`useAuiEvent` is the escape hatch for **transient occurrences that are not derivable from state**. State-derivable transitions (attachment list changing, run progress, thread switching) should be observed with `useAuiState`, not subscribed via events.
+Use `useAuiState` to render the current value of something; use `useAuiEvent` to react to the moment something happens. Both are supported: many events mark a transition you could also observe in state, and subscribing to the event is the intended way to run a side effect at that transition.
 
 The rule of thumb:
 
-1. Can you read the new value from state right now? → use `useAuiState`.
+1. Rendering a value? → use `useAuiState`.
 2. Are you the caller and want immediate feedback? → catch the rejection / read the return value.
-3. Did something happen that has no representation in state at all? → use `useAuiEvent`.
+3. Running a side effect when something happens? → use `useAuiEvent`.
 
-Most existing events are kept for backward compatibility but duplicate state. They are marked `@deprecated` in the type definitions; new code should follow the rule above.
-
-#### Currently Recommended (Truly Transient)
+#### Available Events
 
 | Event                         | When It Fires                                                                |
 | ----------------------------- | ---------------------------------------------------------------------------- |
-| `composer.attachmentAddError` | An `addAttachment()` call failed. Payload `reason` discriminates `no-adapter` / `not-accepted` / `adapter-error`. `no-adapter` and `not-accepted` are non-state-derivable. `adapter-error` is partially state-derivable: if the adapter produced any attachment before failing, the errored attachment also appears in `composer.attachments` with `status.reason === "error"`. The event additionally surfaces a human-readable `message` (and the underlying `Error` instance via the low-level `runtime.unstable_on("attachmentAddError")` API; `useAuiEvent` payloads omit it because raw `Error` objects are not store-serializable). |
+| `threads.selectionChanged`    | The main thread selection changed. Payload carries `threadId` (newly selected) and `previousThreadId`. Does not fire for the initially selected thread on mount. |
+| `thread.runStart` / `runEnd`  | A run started / ended on the thread (also visible as `isRunning` flipping)   |
+| `thread.initialize`           | The thread transitioned from new to initialized, before the first message is added |
 | `thread.modelContextUpdate`   | The model context provider notified a change. The model context lives in a provider, not in thread state, so this event has no state-derivable equivalent. |
+| `composer.send`               | The user sent the composer contents; `messageId` is set for edit-composer sends |
+| `composer.attachmentAdd`      | An attachment was added to the composer                                      |
+| `composer.attachmentAddError` | An `addAttachment()` call failed. Payload `reason` discriminates `no-adapter` / `not-accepted` / `adapter-error`. The event additionally surfaces a human-readable `message` (and the underlying `Error` instance via the low-level `runtime.unstable_on("attachmentAddError")` API; `useAuiEvent` payloads omit it because raw `Error` objects are not store-serializable). |
 
-#### Legacy (State-Derivable, Prefer `useAuiState`)
-
-These events fire at the same transition you can observe via state. They are kept for backward compatibility but new code should observe state instead.
+#### Deprecated Events
 
-| Legacy Event                                 | Observe Instead                                                |
-| -------------------------------------------- | -------------------------------------------------------------- |
-| `composer.send`                              | composer `text` clearing                                       |
-| `composer.attachmentAdd`                     | composer `attachments`                                         |
-| `thread.runStart` / `runEnd`                 | thread `isRunning` flipping to `true` / `false`                |
-| `thread.initialize`                          | thread `messages` becoming non-empty (or `isEmpty` flipping)   |
-| `threadListItem.switchedTo` / `switchedAway` | compare `s.threads.mainThreadId` against `s.threadListItem.id` |
+| Deprecated Event              | Use Instead                                                                  |
+| ----------------------------- | ---------------------------------------------------------------------------- |
+| `threadListItem.switchedTo`   | `threads.selectionChanged` — its `threadId` is the newly selected thread     |
+| `threadListItem.switchedAway` | `threads.selectionChanged` — its `previousThreadId` is the thread switched away from |
 
 ## Troubleshooting
 

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

@@ -283,7 +283,7 @@ This pattern records until the user stops dictation, then commits a single final
 
 ## Custom realtime providers
 
-You can implement `DictationAdapter` against any streaming STT service. [ElevenLabs Scribe](https://elevenlabs.io/docs/capabilities/speech-to-text) is one option for low-latency WebSocket transcription; scaffold a full example with:
+You can implement `DictationAdapter` against any streaming STT service. [ElevenLabs Scribe](https://elevenlabs.io/docs/overview/capabilities/speech-to-text) is one option for low-latency WebSocket transcription; scaffold a full example with:
 
 ```bash
 npx assistant-ui create my-app -e with-elevenlabs-scribe

package/.docs/raw/docs/guides/mentions.mdx

@@ -82,6 +82,8 @@ const myAdapter: Unstable_TriggerAdapter = {
 
 The built-in `unstable_useLiveCompletionAdapter` wraps an async fetcher with debouncing, stale-request cancellation (results for an outdated query are dropped), and a single-entry cache. Its `search` returns the last results synchronously and schedules a debounced fetch when the query changes; when results arrive the returned `adapter` re-creates, which re-runs the popover lookup so the fresh items render. It also reports `isLoading`, which you pass to the popover to show a loading state.
 
+When the fetcher reads from an account- or workspace-specific source, pass that source ID as `cacheKey`. Changing the key clears cached results and cancels any pending result from the previous source.
+
 ```tsx
 import {
   unstable_useLiveCompletionAdapter,

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

@@ -138,7 +138,7 @@ The primitives available for rendering suggestions are `ThreadPrimitive.Suggesti
 
 ## Runtime driven suggestions
 
-The static `Suggestions(...)` API covers welcome screens. For follow up prompts that depend on the conversation, a tool result, or your backend, push suggestions through the runtime itself. They land on `thread.suggestions` rather than the static `suggestions` scope, so they render through a different component.
+The static `Suggestions(...)` API covers welcome screens. For follow up prompts that depend on the conversation, a tool result, or your backend, push suggestions through the runtime itself. They land on `thread.suggestions`, and when no static `Suggestions(...)` configuration is set, the `suggestions` scope derives from them, so `ThreadPrimitive.Suggestions` renders them as well. Runtime suggestions use the `ThreadSuggestion` shape: a required `prompt` plus optional `title` and `label`. When `title` is omitted it falls back to the prompt, and an omitted `label` renders as empty, so a prompt-only runtime suggestion looks exactly like a plain string suggestion.
 
 ### Local runtime: `SuggestionAdapter`
 
@@ -263,7 +263,7 @@ The local runtime clears its suggestions when a new run starts. External store r
 
 ### Rendering runtime suggestions
 
-Static suggestions go through `ThreadPrimitive.Suggestions`; runtime suggestions go through `thread.suggestions`. The shadcn registry ships `ThreadFollowupSuggestions` for the common single line pill layout. For a custom layout, read the array yourself:
+Runtime suggestions land on `thread.suggestions`, and `ThreadPrimitive.Suggestions` picks them up unless a static `Suggestions(...)` configuration overrides the scope. The shadcn registry ships `ThreadFollowupSuggestions` for the common single line pill layout. For a custom layout, read the array yourself:
 
 ```tsx
 import { useAuiState, ThreadPrimitive, AuiIf } from "@assistant-ui/react";
@@ -280,7 +280,10 @@ function FollowUps() {
             method="replace"
             autoSend
           >
-            {s.prompt}
+            {s.title ?? s.prompt}
+            {s.label && (
+              <span className="text-muted-foreground ms-1">{s.label}</span>
+            )}
           </ThreadPrimitive.Suggestion>
         ))}
       </div>

package/.docs/raw/docs/ink/primitives.mdx

@@ -1217,7 +1217,7 @@ Container `Box` for the status bar. Forwards all `Box` props; pass `gap` to spac
 ```tsx
 <StatusBarPrimitive.Root gap={1}>
   <StatusBarPrimitive.Status />
-  <StatusBarPrimitive.ModelName name="gpt-5" />
+  <StatusBarPrimitive.ModelName name="gpt-5.6-luna" />
   <StatusBarPrimitive.MessageCount />
   <StatusBarPrimitive.TokenCount />
   <StatusBarPrimitive.Latency />