Release history

The event now carries { reason, message, attachmentId?, error? } so subscribers can branch on the failure mode (no-adapter / not-accepted / adapter-error). The bridge no longer relies on a findLast heuristic to recover the failed attachment id.

Several state-derivable events are now annotated @deprecated because they duplicate state observation: composer.send, composer.attachmentAdd, thread.runStart, thread.runEnd, thread.initialize, threadListItem.switchedTo, threadListItem.switchedAway. They continue to fire for backward compatibility; new code should observe state via useAuiState instead.

Introduces a new primitive that coalesces adjacent parts into groups via a user-supplied groupBy(part) → "group-…" | readonly "group-…"[] | null. Adjacent parts sharing a key-path prefix coalesce up to that prefix; ungrouped parts render as direct leaves.

The render function takes { part, children } and dispatches on a single switch (part.type). "group-…" cases wrap children (the recursively-rendered subtree); real part types ("text", "tool-call", "reasoning", …) render the part directly with the same EnrichedPartState enrichments (toolUI, addResult, resume, dataRendererUI) that <MessagePrimitive.Parts> provides.

GroupPart is intentionally minimal: { type, status, indices }. The render function is invoked once per group node and once per individual leaf part, so users never have to nest a <MessagePrimitive.Parts> call.

The groupBy return type is constrained to `group-${string}` so the unified switch can never collide with a real part type. The component infers a literal TKey per call site, so part.type narrows to the exact union of group keys plus part types.

For leaf parts, children is a sentinel that throws if rendered — accidental fall-through like default: return children; errors loudly instead of silently rendering nothing. Returning null from a leaf case is fine.

Deprecates the legacy components.ToolGroup, components.ReasoningGroup, and components.ChainOfThought props on <Parts>, and <MessagePrimitive.Unstable_PartsGrouped> for adjacent grouping — all still work for backwards compatibility.

Users with moduleResolution: node in their tsconfig were seeing Property 'message' does not exist on type 'AssistantState' because the exports map sub-paths (e.g. @assistant-ui/core/react) are ignored by legacy node module resolution. Adding typesVersions makes TypeScript resolve sub-path types correctly under all moduleResolution modes.

The ./* wildcard in exports was exposing the entire dist tree as importable subpaths, which inadvertently leaked internal modules (e.g. @assistant-ui/core/tests/*, @assistant-ui/core/types/*) as public API. Removing it.

Two attachment status types that were previously only reachable through the wildcard (PendingAttachmentStatus, CompleteAttachmentStatus) are now re-exported from the package root so that consumers' inferred types remain portable.

Introduces a new primitive that coalesces adjacent parts into groups via a user-supplied groupBy(part) → "group-…" | readonly "group-…"[] | null. Adjacent parts sharing a key-path prefix coalesce up to that prefix; ungrouped parts render as direct leaves.

The render function takes { part, children } and dispatches on a single switch (part.type). "group-…" cases wrap children (the recursively-rendered subtree); real part types ("text", "tool-call", "reasoning", …) render the part directly with the same EnrichedPartState enrichments (toolUI, addResult, resume, dataRendererUI) that <MessagePrimitive.Parts> provides.

GroupPart is intentionally minimal: { type, status, indices }. The render function is invoked once per group node and once per individual leaf part, so users never have to nest a <MessagePrimitive.Parts> call.

The groupBy return type is constrained to `group-${string}` so the unified switch can never collide with a real part type. The component infers a literal TKey per call site, so part.type narrows to the exact union of group keys plus part types.

For leaf parts, children is a sentinel that throws if rendered — accidental fall-through like default: return children; errors loudly instead of silently rendering nothing. Returning null from a leaf case is fine.

Deprecates the legacy components.ToolGroup, components.ReasoningGroup, and components.ChainOfThought props on <Parts>, and <MessagePrimitive.Unstable_PartsGrouped> for adjacent grouping — all still work for backwards compatibility.

• @assistant-ui/[email protected]

Introduces a new primitive that coalesces adjacent parts into groups via a user-supplied groupBy(part) → "group-…" | readonly "group-…"[] | null. Adjacent parts sharing a key-path prefix coalesce up to that prefix; ungrouped parts render as direct leaves.

The render function takes { part, children } and dispatches on a single switch (part.type). "group-…" cases wrap children (the recursively-rendered subtree); real part types ("text", "tool-call", "reasoning", …) render the part directly with the same EnrichedPartState enrichments (toolUI, addResult, resume, dataRendererUI) that <MessagePrimitive.Parts> provides.

GroupPart is intentionally minimal: { type, status, indices }. The render function is invoked once per group node and once per individual leaf part, so users never have to nest a <MessagePrimitive.Parts> call.

The groupBy return type is constrained to `group-${string}` so the unified switch can never collide with a real part type. The component infers a literal TKey per call site, so part.type narrows to the exact union of group keys plus part types.

For leaf parts, children is a sentinel that throws if rendered — accidental fall-through like default: return children; errors loudly instead of silently rendering nothing. Returning null from a leaf case is fine.

Deprecates the legacy components.ToolGroup, components.ReasoningGroup, and components.ChainOfThought props on <Parts>, and <MessagePrimitive.Unstable_PartsGrouped> for adjacent grouping — all still work for backwards compatibility.

• @assistant-ui/[email protected]

allows adapter authors to carry arbitrary backend session data through list() / fetch() and surface it on the thread list item state. matches the existing custom: Record<string, unknown> convention used on ThreadMessage, RunConfig, and ChatModelRunResult. consumers can intersect a typed shape at their own boundary, e.g. RemoteThreadMetadata & { custom: { workspaceId: string } }.

• @assistant-ui/[email protected]
• @assistant-ui/[email protected]

composer.addAttachment previously bypassed the configured AttachmentAdapter for CreateAttachment descriptors, including the adapter.accept content-type check. It now validates the descriptor's contentType (or filename extension) against adapter.accept when an adapter is configured, throwing and emitting composer.attachmentAddError on mismatch. Without an adapter, external attachments are still added as-is, preserving the existing "no adapter required" guarantee for external sources.

RemoteThreadListAdapter.unstable_Provider is now allowed to render any subtree it likes; the runtime binding (composer state, __internal_setGetInitializePromise, runEnd → generateTitle listener) executes outside it. This fixes EMPTY_THREAD_ERROR when the Provider defers children (e.g. behind a history-loading state) and avoids the history-switch regression seen when only the binder, but not the init listeners, were hoisted. Adds a dev-mode warning when the Provider does not render children within ~100ms.

useAdkRuntime.getMessageContent previously collapsed file message parts into a [File: <name>] text marker before sending to ADK, dropping the base64 payload entirely. new file and file_url variants on AdkMessageContentPart carry the binary through AdkClient and useAdkMessages.contentToParts, which serialize them as inlineData and fileData on the wire. inbound, AdkEventAccumulator sniffs MIME type so non-image inlineData produces a file part (rather than being silently coerced into image), and explicitly non-image fileData produces file_url; fileData with no MIME type falls back to image_url to preserve the legacy round-trip. convertAdkMessage maps file to a core FileMessagePart and file_url to a data part named "file_url".

• @assistant-ui/[email protected]
• @assistant-ui/[email protected]

Add uiComponents option to useLangGraphRuntime for registering static data renderers by name and a fallback renderer for dynamic loading (e.g. LangSmith's LoadExternalComponent), directly from the runtime hook.

Core DataRenderers scope also gains a fallbacks stack (plus setFallbackDataUI method) that the adapter registers into; resolution is renderers[name][0] → fallbacks[0] → inline Fallback.

Add uiComponents option to useLangGraphRuntime for registering static data renderers by name and a fallback renderer for dynamic loading (e.g. LangSmith's LoadExternalComponent), directly from the runtime hook.

Core DataRenderers scope also gains a fallbacks stack (plus setFallbackDataUI method) that the adapter registers into; resolution is renderers[name][0] → fallbacks[0] → inline Fallback.

• toAgUiMessages() previously called extractText() for user messages, silently dropping image and file attachments
• User messages with attachments now emit AG-UI InputContent[]: images map to the image variant with a data or url source, files map to the binary variant preserving filename
• Falls back to plain string content when no binary parts are present, preserving backward compatibility

AdkEventAccumulator.processEvent previously routed author: "user" events through getOrCreateAiMessage, producing type: "ai" messages that convertAdkMessage mapped to role: "assistant" — so user text rendered as assistant bubbles. With Workflow agents this caused full multi-turn conversations to merge into a single assistant block. User events now create type: "human" messages, preserving text, inline images, and file references.

• useAdkRuntime.onNew now filters pending tool calls whose id is tracked in long_running_tool_ids, so ADK HITL interrupts (adk_request_input, adk_request_confirmation, adk_request_credential) are no longer overwritten with {cancelled: true} when the user types a new message
• Add useAdkSubmitInput(toolCallId, result) to submit the user's answer as a {result} FunctionResponse, matching ADK's unwrap_response contract so Workflow RequestInput nodes resume with the unwrapped value
• AdkEventAccumulator unions long_running_tool_ids across events instead of replacing, so multiple HITL interrupts in the same turn are all tracked
• onEdit / onReload / session load paths now reset derived HITL state (longRunningToolIds, toolConfirmations, authRequests, escalated) via a new replaceMessages helper on useAdkMessages, so stale interrupt markers don't leak into the next turn

Behavior change: HITL interrupts must now be answered through a tool UI using the dedicated submit helpers (useAdkSubmitInput, useAdkConfirmTool, useAdkSubmitAuth). Typing in the composer while an interrupt is pending no longer sends a spurious cancellation.

• Translate UI messages into DataMessageParts on the associated assistant message, rendered via the existing makeAssistantDataUI({ name, render }) API
• Accumulate UI messages from both custom stream events (raw {type:"ui"} / {type:"remove-ui"}) and the values.ui state snapshot
• Key UI entries by ui.id, shallow-merge props when metadata.merge === true, delete on type:"remove-ui"
• Expose uiStateKey config option for graphs that customize the typedUi state key
• Extend the load callback return type with uiMessages so persisted UI state can be restored on thread switch
• Expose useLangGraphUIMessages() for accessing the raw UI message list
• Export UIMessage, RemoveUIMessage, and UseLangGraphRuntimeOptions types

Behavior change: {type:"ui"} / {type:"remove-ui"} payloads received on the custom stream channel are now intercepted by the adapter before reaching eventHandlers.onCustomEvent. Other custom events still reach the handler unchanged.

• Add SendOptions with startRun flag to composer.send()
• Expose parentId and sourceId on EditComposerState
• Add EditComposerRuntimeCore interface extending ComposerRuntimeCore
• Bypass text-unchanged guard when startRun is explicitly set
• ComposerSendOptions extends SendOptions for consistent layering

• Introduce ComposerInputPlugin protocol to decouple ComposerInput from mention-specific code

• Extract generic TriggerPopoverResource from MentionResource supporting multiple trigger characters

• Add Unstable_TriggerItem, Unstable_TriggerCategory, Unstable_TriggerAdapter generic types

• Add Unstable_SlashCommandAdapter, Unstable_SlashCommandItem types

• Add ComposerPrimitive.Unstable_TriggerPopoverRoot and related primitives

• Add ComposerPrimitive.Unstable_SlashCommandRoot and related primitives

• Add unstable_useSlashCommandAdapter hook for building slash command adapters

• Refactor MentionResource as thin wrapper around TriggerPopoverResource

• Alias Unstable_MentionItem/Unstable_MentionAdapter to generic trigger types

• Update react-lexical KeyboardPlugin to use plugin protocol

• All existing Unstable_Mention* APIs remain unchanged

• [email protected]

• @assistant-ui/[email protected]

• @assistant-ui/[email protected]

• Add SendOptions with startRun flag to composer.send()
• Expose parentId and sourceId on EditComposerState
• Add EditComposerRuntimeCore interface extending ComposerRuntimeCore
• Bypass text-unchanged guard when startRun is explicitly set
• ComposerSendOptions extends SendOptions for consistent layering

• Introduce ComposerInputPlugin protocol to decouple ComposerInput from mention-specific code

• Extract generic TriggerPopoverResource from MentionResource supporting multiple trigger characters

• Add Unstable_TriggerItem, Unstable_TriggerCategory, Unstable_TriggerAdapter generic types

• Add Unstable_SlashCommandAdapter, Unstable_SlashCommandItem types

• Add ComposerPrimitive.Unstable_TriggerPopoverRoot and related primitives

• Add ComposerPrimitive.Unstable_SlashCommandRoot and related primitives

• Add unstable_useSlashCommandAdapter hook for building slash command adapters

• Refactor MentionResource as thin wrapper around TriggerPopoverResource

• Alias Unstable_MentionItem/Unstable_MentionAdapter to generic trigger types

• Update react-lexical KeyboardPlugin to use plugin protocol

• All existing Unstable_Mention* APIs remain unchanged

• @assistant-ui/[email protected]

• [email protected]

• @assistant-ui/[email protected]

• Introduce ComposerInputPlugin protocol to decouple ComposerInput from mention-specific code

• Extract generic TriggerPopoverResource from MentionResource supporting multiple trigger characters

• Add Unstable_TriggerItem, Unstable_TriggerCategory, Unstable_TriggerAdapter generic types

• Add Unstable_SlashCommandAdapter, Unstable_SlashCommandItem types

• Add ComposerPrimitive.Unstable_TriggerPopoverRoot and related primitives

• Add ComposerPrimitive.Unstable_SlashCommandRoot and related primitives

• Add unstable_useSlashCommandAdapter hook for building slash command adapters

• Refactor MentionResource as thin wrapper around TriggerPopoverResource

• Alias Unstable_MentionItem/Unstable_MentionAdapter to generic trigger types

• Update react-lexical KeyboardPlugin to use plugin protocol

• All existing Unstable_Mention* APIs remain unchanged

• @assistant-ui/[email protected]

• @assistant-ui/[email protected]

• @assistant-ui/[email protected]

• Rename useInteractable to useAssistantInteractable (registration only, returns id)
• Add useInteractableState hook for reading/writing interactable state
• Remove makeInteractable and related types
• Rename UseInteractableConfig to AssistantInteractableProps
• Extract buildInteractableModelContext from Interactables resource
• Add with-interactables example to CLI

Add a convenience hook that derives per-property streaming completion status from tool call args using structural partial JSON analysis.

• [email protected]
• [email protected]
• @assistant-ui/[email protected]
• @assistant-ui/[email protected]

• Rename useInteractable to useAssistantInteractable (registration only, returns id)
• Add useInteractableState hook for reading/writing interactable state
• Remove makeInteractable and related types
• Rename UseInteractableConfig to AssistantInteractableProps
• Extract buildInteractableModelContext from Interactables resource
• Add with-interactables example to CLI

Add a convenience hook that derives per-property streaming completion status from tool call args using structural partial JSON analysis.

• [email protected]
• @assistant-ui/[email protected]
• [email protected]
• @assistant-ui/[email protected]
• @assistant-ui/[email protected]

• Rename useInteractable to useAssistantInteractable (registration only, returns id)
• Add useInteractableState hook for reading/writing interactable state
• Remove makeInteractable and related types
• Rename UseInteractableConfig to AssistantInteractableProps
• Extract buildInteractableModelContext from Interactables resource
• Add with-interactables example to CLI

Add a convenience hook that derives per-property streaming completion status from tool call args using structural partial JSON analysis.

• [email protected]
• @assistant-ui/[email protected]
• @assistant-ui/[email protected]
• @assistant-ui/[email protected]

• Rename useInteractable to useAssistantInteractable (registration only, returns id)
• Add useInteractableState hook for reading/writing interactable state
• Remove makeInteractable and related types
• Rename UseInteractableConfig to AssistantInteractableProps
• Extract buildInteractableModelContext from Interactables resource
• Add with-interactables example to CLI

Add a convenience hook that derives per-property streaming completion status from tool call args using structural partial JSON analysis.

• [email protected]
• @assistant-ui/[email protected]
• @assistant-ui/[email protected]
• @assistant-ui/[email protected]

• Rename useInteractable to useAssistantInteractable (registration only, returns id)

• Add useInteractableState hook for reading/writing interactable state

• Remove makeInteractable and related types

• Rename UseInteractableConfig to AssistantInteractableProps

• Extract buildInteractableModelContext from Interactables resource

• Add with-interactables example to CLI

• @assistant-ui/[email protected]

• useInteractable(name, config) hook and makeInteractable factory for registering AI-controllable UI
• Interactables() scope resource with auto-generated update tools and system prompt injection
• Partial updates — auto-generated tools use partial schemas so AI only sends changed fields
• Multi-instance support — same name with different IDs get separate update_{name}_{id} tools
• Selection — setSelected(true) marks an interactable as focused, surfaced as (SELECTED) in system prompt

• useInteractable(name, config) hook and makeInteractable factory for registering AI-controllable UI
• Interactables() scope resource with auto-generated update tools and system prompt injection
• Partial updates — auto-generated tools use partial schemas so AI only sends changed fields
• Multi-instance support — same name with different IDs get separate update_{name}_{id} tools
• Selection — setSelected(true) marks an interactable as focused, surfaced as (SELECTED) in system prompt

• useInteractable(name, config) hook and makeInteractable factory for registering AI-controllable UI
• Interactables() scope resource with auto-generated update tools and system prompt injection
• Partial updates — auto-generated tools use partial schemas so AI only sends changed fields
• Multi-instance support — same name with different IDs get separate update_{name}_{id} tools
• Selection — setSelected(true) marks an interactable as focused, surfaced as (SELECTED) in system prompt

• useInteractable(name, config) hook and makeInteractable factory for registering AI-controllable UI
• Interactables() scope resource with auto-generated update tools and system prompt injection
• Partial updates — auto-generated tools use partial schemas so AI only sends changed fields
• Multi-instance support — same name with different IDs get separate update_{name}_{id} tools
• Selection — setSelected(true) marks an interactable as focused, surfaced as (SELECTED) in system prompt

• Add queue adapter to ExternalThreadProps for runtimes that support message queuing

• Add QueueItemPrimitive.Text, .Steer, .Remove primitives for rendering queue items

• Add ComposerPrimitive.Queue for rendering the queue list within the composer

• Add ComposerSendOptions with steer flag to composer.send()

• Add capabilities.queue to RuntimeCapabilities

• ComposerPrimitive.Send stays enabled during runs when queue is supported

• Cmd/Ctrl+Shift+Enter hotkey sends with steer: true (interrupt current run)

• Add queueItem scope to ScopeRegistry

• Add queue field to ComposerState and queueItem() method to ComposerMethods

• @assistant-ui/[email protected]

• [email protected]

• @assistant-ui/[email protected]

• Add clear(reason: "edit" | "reload" | "cancel-run") to ExternalThreadQueueAdapter
• thread.append() now routes through queue.enqueue when a queue adapter is present
• Cancel, edit, and reload operations call queue.clear with the appropriate reason

• Add queue adapter to ExternalThreadProps for runtimes that support message queuing
• Add QueueItemPrimitive.Text, .Steer, .Remove primitives for rendering queue items
• Add ComposerPrimitive.Queue for rendering the queue list within the composer
• Add ComposerSendOptions with steer flag to composer.send()
• Add capabilities.queue to RuntimeCapabilities
• ComposerPrimitive.Send stays enabled during runs when queue is supported
• Cmd/Ctrl+Shift+Enter hotkey sends with steer: true (interrupt current run)
• Add queueItem scope to ScopeRegistry
• Add queue field to ComposerState and queueItem() method to ComposerMethods

• ReadonlyThreadProvider and MessagePartPrimitive.Messages for rendering sub-agent messages
• assistant-stream: add messages field to tool-result chunks, ToolResponseLike, and ToolCallPart types, enabling sub-agent messages to flow through the streaming protocol