@assistant-ui/react#

0.15.30#

Patch Changes#

• #9862 1a3359e - Add a Resume control for interrupted runs. useComposerResume from @assistant-ui/core/react and ComposerPrimitive.Resume resume a run whose adapter reports canResume; the control is disabled while the draft is not empty or the thread is busy. (@okisdev)

• #9789 479d267 - fix: call a directive trigger's onInserted under the Lexical composer once the directive is in the composer text; onDirectiveSelect now fires at the same point (@bnb)

• #9776 32a1b79 - useAuiState and aui.composer.getState() now see composer text as soon as setText returns, so an input that keeps its own state, such as react-mentions, no longer moves the caret to the end. (@okisdev)

• #9891 545836d - feat: ModelContext() takes maxSystemLength to cap the merged system prompt, trimming the lowest-priority parts first, or mergeSystem to combine the prioritized SystemParts yourself (@Yonom)

• #9865 727a02d - run the thread viewport on the shared auto-scroll controller, so a viewport footer's height counts toward the bottom of the thread (@okisdev)

• Updated dependencies [69bf91a, ed0d969, 1a3359e, 2dc72a8, 32869e0, 6966821, 118dedb, 79e10db, 32a1b79, d7fb0ee, 545836d, e21ce83, ca0a1be, d420f42, 9f673a3, ab3454d, e99250f, 1808265, 1960f3c, 506aba9, 2d17e77, 45e3d22, a587b28, 50fb79b, e6cace0, 54e2e9b, be30245, 727a02d, 0c049eb]:

  • @assistant-ui/core@0.3.30
  • @assistant-ui/store@0.3.22
  • assistant-stream@0.3.53
  • @assistant-ui/tap@0.9.24

0.15.29#

Patch Changes#

• #9613 6e17b3a - fix: preserve pending attachment selections when unrelated assistant scopes change (@Kinfe123)

• #9602 c696c16 - fix: ignore an attachment picker's selection after the active thread changes, keeping files out of the replacement conversation. (@Kinfe123)

• #9753 14eec8a - A run that starts while focus is in a field outside the thread no longer moves focus into the composer, and a composer that already has focus keeps its selection. (@okisdev)

• #9586 2eb0447 - feat: add OpenAIRealtimeVoiceAdapter for direct browser voice sessions with streamed transcripts, typed input, mute controls, and cancellable WebRTC setup. (@Kinfe123)

• #9768 c71326f - Clear frame tools and pending calls when the iframe document changes or reloads. (@okisdev)

• #9747 b4558a5 - useAssistantFrameHost disposes the host when its iframe is removed from the page, so the frame's tools leave the model context and its pending calls reject right away, and it serves a new iframe mounted into the same ref. (@okisdev)

• #9252 1371e4f - Handle sparse MCP Apps message content without scanning array holes. (@rupic-app)

• Updated dependencies [b78a043, fe13206, 8289dd1, e09563a, b88d62d, 5588bfb, d6e8a0c, fe7179d, c71326f, 55d065c, 61aaccf, 43c9c7c, 75abfbe, 12dfc85, 1091bbc, 01225b9, d2f04ca, 6537c5f, 2217804, 7ba7c54, cd5fd6c, 5197671, 04c5d36]:

  • @assistant-ui/core@0.3.29
  • assistant-stream@0.3.52
  • @assistant-ui/store@0.3.21

0.15.28#

Patch Changes#

• #9323 2be98de - fix(react): render an inert composer's inert attribute on React 18, so the cancel focus loop skips it as it does on React 19 (@okisdev)
• Updated dependencies [c157aee, 2c1963a, afb9ad2, efbf028, 8b49f28, 4e86339, 28dc601]:
  • @assistant-ui/core@0.3.27
  • safe-content-frame@0.0.34
  • assistant-stream@0.3.50
  • @assistant-ui/tap@0.9.23

0.15.27#

Patch Changes#

• #9171 6528ee3 - Guard the composer input example against IME confirmation Enter. (@rupic-app)

• #9166 b86d6cd - Block typing, attachments, sends, and message editing while a thread is disabled. (@rupic-app)

• #9247 664f2df - fix(react): pass an MCP App's ui/initialize params to onInitialized as McpAppInitializeParams, including the display modes the app declares (@rupic-app)

• Updated dependencies [2c10bb1, 16afd50, b86d6cd, 96fd2a2, 2b3e0d3]:

  • assistant-cloud@0.2.7
  • @assistant-ui/core@0.3.26
  • @assistant-ui/store@0.3.19

0.15.26#

Patch Changes#

• #8483 7b7c782 - Restore focus to the thread composer after cancelling a message edit with Escape or keyboard/assistive-technology activation of the Cancel button. Pointer activation preserves the existing focus behavior. (@akim136)

• #8259 0f740cc - fix: show the selection toolbar after a window blur (@rupic-app)

• #8258 7530834 - fix(react): recognize user scrolls coalesced with programmatic bottom scrolling (@rupic-app)

• #8777 658a1a3 - Avoid React 18 server-render warnings from layout effects while keeping client layout timing. (@rupic-app)

• #9082 ae487aa - feat: mark every experimental API @deprecated Experimental since <date>, so editors strike it through as experimental rather than scheduled for removal; @typescript-eslint/no-deprecated reports these APIs too (@okisdev)

• #8924 23a4677 - fix: AssistantFrameProvider.dispose() now tells the parent it is gone, so AssistantFrameHost rejects tool calls still waiting on the frame right away instead of after the 30 s timeout (@kr1shna-exe)

• #8833 0a3ca24 - chore: update dependencies (@Yonom)

• #8877 98f9ed7 - render MessagePrimitive.Unstable_PartsGrouped leaves through core's part renderer instead of a copy (@okisdev)

• #8482 051813b - Show the selection toolbar when a selection ends at offset zero at the start of the next message without selecting its content. (@akim136)

• #8859 8551135 - Keep thread viewport event listeners stable across unrelated renders. (@rupic-app)

• #8577 73b3ea3 - fix: enforce MCP App resource CSP metadata inside widget frames (@Kinfe123)

• #8811 6144fa3 - fix: show the scroll-to-bottom control after a wheel interrupts smooth scrolling (@Kinfe123)

• #9003 116424f - Keep thread viewport observers stable and preserve scheduled scroll behavior. (@rupic-app)

• #7901 cb20f13 - fix: render MCP Apps through ToolUIDisplay on Parts, grouped, native, and ink (@Kinfe123)

• #9082 ae487aa - fix(react): strike through the deprecated ComposerPrimitive.Unstable_TriggerPopover* aliases, whose notices sat above their export statements where TypeScript ignores them (@okisdev)

• #8903 df2ab0a - the thread viewport follows content that grows without a DOM change (an expanding collapsible, a loading image, an autosizing textarea) and updates isAtBottom so the scroll-to-bottom button shows; the React viewport now shares observeContentResize with Vue and Svelte (@kr1shna-exe)

• #8946 6de3446 - stop following the bottom of the thread viewport when the user expands a disclosure inside a message, so a card opened mid-stream stays in view (@okisdev)

• Updated dependencies [3ad209c, fc73a27, 5a67c85, e45b97b, c2b93b1, 9201447, 7e78ca4, 2e5432f, 840ac3a, 20f0e5b, 14ceafa, 3baba6f, 7855706, d40092c, a32e7a8, 1002313, 606bc2d, 7886e77, 34fa2b6, d19b547, 3926f8f, c5a635a, 4fbf441, dc72a0e, be19872, 40da737, 2252059, 2abd1e0, 2ed2043, 987ffe1, 3ffa474, 5bb65a3, 836432d, 93d04cb, ae487aa, 59d42c1, ca4ec1f, 184b083, 8a21038, 7321036, bf65f81, 4d5070d, 3ef6e7c, 9125e30, 4ac25b9, 23a4677, 7aa5bdd, afe32c6, 01ac83d, 30c2480, ef5a1e2, 5a09ea3, b578c02, 4709edf, 820ab5f, 63df0e4, 2307752, 5bd5de3, 14ba56e, b03f90e, 8c32dea, 0a3ca24, f6d1489, b4b56fe, a6ca3f9, 7f7d512, 0d74a05, 1cabbbd, 9121416, 429a26d, 2356e80, 194c0e2, fae89b1, 708bf2c, 4b44723, 92e7ab1, a1caaa8, ee517fb, 7842639, 116424f, 399621e, 79867bd, f306b40, 081a239, 542d871, 039d048, 0967886, e7534a2, 361d590, c04f09d, efb83eb, 1cd8911, 79e9a5a, 9aff121, 0d72f48, e79cdd4, 01b5e06, 06c3fef, 41344cb, cebaed5, 2a1a788, e8620c1, b9a5d38, 3b7b337, cb20f13, 1d550c0, 9dfd037, ef87d70, 4f2ad45, dc72a0e, df2ab0a, 8831c76, 2d37f82, 2bc6e49, b257f49, 7a3e496]:

  • @assistant-ui/store@0.3.18
  • @assistant-ui/core@0.3.25
  • assistant-cloud@0.2.6
  • assistant-stream@0.3.49
  • @assistant-ui/tap@0.9.22

0.15.25#

Patch Changes#

• #8796 fd444e4 - a tool approval can ask several questions at once, or let one question take several answers: display: "questions" with approval.questions, answered through respondToApproval({ answers }) keyed by question id, validated before it reaches onRespondToToolApproval and recorded on approval.answers; the AI SDK converter reads questions and answers from the approval descriptor when a response handler is set, and the cloud format keeps them (@okisdev)

• #7212 9f40133 - fix: clean up cancelled and pre-load failed sandbox frame renders (@Kinfe123)

• #7189 d2782af - feat: allow visible component action settle delays to be configured (@Kinfe123)

• #7155 5484ca4 - feat: support message-scoped converter metadata invalidation (@Kinfe123)

• #8798 ec48da2 - a thread can open on its latest page and load older messages on demand: the external store adapter takes hasEarlier and onLoadEarlier, the runtime surfaces them as thread.hasEarlier, thread.isLoadingEarlier and aui.thread.loadEarlier() with one load in flight at a time, ThreadPrimitive.LoadEarlier loads the next page, ThreadPrimitive.Viewport keeps the visible messages in place when it lands above them, and the React Native ThreadPrimitive.MessagesFlatList pages through the runtime when it gets no history prop (@okisdev)

• #8760 2e4d6a9 - streaming text, running tool durations, and message stall detection read no wall clock during render, so a cacheComponents prerender no longer fails on them. (@okisdev)

• #8794 451a76c - reasoning parts carry an optional timing with their start and end times, typed as the new MessagePartTiming that ToolCallTiming now aliases, so a host can show how long its agent thought; the assistant-stream accumulator stamps it while reasoning streams, joined reasoning parts and the cloud format keep it, and a MessagePrimitive.GroupedParts group reports the span of its timed parts as timing (@okisdev)

• #8795 1f77d04 - the composer trigger popover primitives and their adapter, item, category and directive formatter types get stable names; the Unstable_ names stay as deprecated aliases, and the trigger popover hooks stay unstable (@okisdev)

• #8799 aecb5eb - a long thread can be virtualized per part instead of per message: createThreadRowsSelector flattens the thread for useAuiState into stable rows (a user message, each top-level part group of an assistant message, a turn end) that keep their identity while tokens stream, and ThreadPrimitive.Row renders one row with only the scopes it needs; a turn-end row carries the turn's start time and, once the turn completes, the latest end its messages record, so a turn footer can show how long the agent worked (@okisdev)

• Updated dependencies [c883dc0, fd444e4, 64277e2, 9f40133, 791d240, ed84b12, 2bc1edb, 0284a07, 5484ca4, ec48da2, 46133cd, 3effee5, 451a76c, 16439da, 1f77d04, aecb5eb, 77a98c1]:

  • @assistant-ui/core@0.3.24
  • assistant-stream@0.3.48
  • safe-content-frame@0.0.33

0.15.24#

Patch Changes#

• #8148 b400b75 - fix(react): ignore the Enter or Escape that ends an IME composition, so committing a conversion in Safari no longer sends the message, and cancelling one no longer cancels the run or stops read-aloud (@samdickson22)

• #8507 098c140 - chore: update dependencies (@Yonom)

• #8684 5b65868 - key message parts by their id when no other part of the same type in the message shares it, so a replaced or reordered part no longer keeps another part's component state (@okisdev)

• Updated dependencies [f7eae39, 63233dc, 241b5f1, 5b65868, 6b7df95, 098c140, 351b8cd, 3ea546a, d33ad09, 4290eac]:

  • @assistant-ui/core@0.3.23
  • assistant-stream@0.3.47
  • assistant-cloud@0.2.5
  • safe-content-frame@0.0.32
  • @assistant-ui/store@0.3.17
  • @assistant-ui/tap@0.9.21

0.15.23#

Patch Changes#

• #8082 3104efa - fix: honor user={false}, assistant={false} and system={false} on MessagePrimitive.If, and migrate them to the matching AuiIf inequality (@ShobhitPatra)

• #8394 c3a2646 - fix: publish committed WebMCP tool implementations before layout effects (@Kinfe123)

• #8489 19eb2eb - fix: leave modified arrow keys available to application shortcuts while preserving ordinary thread-list focus navigation. (@Kinfe123)

• #8495 aaed14b - fix: scope Escape speech cancellation to the targeted thread (@Kinfe123)

• Updated dependencies [2e066e2, f77dbea, 98f3dbd, 7a41e54, f054d07, b1a3211, ce5b7ed, d7d3d2e, bb6122a, cec9fd4, ac91c4c, f0a0488, c66cc10, c978a22, 038cd9f, fa460c6, 5df393f, 9eba158, e72ac92, 1e9493f, f6374de, cf19d4b, d7d3d2e, e79b815, 1b49876, e971918, 73c7de7, fda7946, a5208c1, 2b6597a, e73db99, a4f6ce9, c980b36, fd28612, 9946dc1, 3e33ac2]:

  • @assistant-ui/store@0.3.16
  • @assistant-ui/core@0.3.22
  • assistant-stream@0.3.46
  • assistant-cloud@0.2.4
  • @assistant-ui/tap@0.9.20

0.15.22#

Patch Changes#

• #8032 d096801 - fix: type the assistant transport request body that prepareSendCommandsRequest receives; its fields are no longer unknown in @assistant-ui/react, and threadId is an optional string, absent when a resume has no remote id, instead of string | null (@rupic-app)

• #8342 aa0f338 - feat: useAssistantTransportRuntime accepts cloud: Assistant Cloud backs the thread list and every request carries the cloud thread id; without cloud, NEXT_PUBLIC_ASSISTANT_BASE_URL selects Assistant Cloud, as it does for useLocalRuntime. adapters.history, which this runtime never read, is deprecated (@okisdev)

• #7731 455e2ac - fix: lock the current scroll container after reasoning content or its ancestor chain changes (@Kinfe123)

• #7730 af49e91 - fix: prevent stale message hover updates after unmount (@Kinfe123)

• #7737 6cc0bee - fix: scope selection toolbars to their owning thread (@Kinfe123)

• #8339 967de5d - feat: CloudRendererHost draws a stored conversation in the Assistant Cloud dashboard's As shown view with the app's own components; a read only thread now reports itself disabled, so its composer renders disabled, and ignores composer input instead of throwing (@okisdev)

• #8030 e8fac8d - feat: show a message with uploading attachments in the thread while it is being sent (@okisdev)

  MessagePrimitive.Attachments now hands its render function Attachment rather than CompleteAttachment, because the row of a message that is still being sent shows attachments that are still uploading. a render function that reads attachment.content should check attachment.status.type === "complete" first.

• #7877 83f5354 - fix: honor registered data-part fallbacks on native MessageContent and grouped parts (@Kinfe123)

• #7760 84e0cf4 - fix: emit declarations from one TypeScript program so two builds of the same commit produce the same .d.ts (@okisdev)

  aui-build now emits the unbundled .d.ts output in one TypeScript pass over the whole package, so two builds of the same commit produce identical declarations; the per-module emit it replaced followed the bundler's load order and let union member order, alias visibility and import specifiers move between builds. Declarations import barrels as the source does and keep import type; the exported types are unchanged. A /// <reference> directive that must reach the published declarations now carries preserve="true" in the source.

• #7838 3d01501 - fix: every distribution re-exports the same shared surface from @assistant-ui/core. @assistant-ui/react-ink gains ReadonlyThreadProvider, ToolCallMessagePartStatus, groupPartByType, GroupByContext, VoiceSessionState, the external store runtime (useExternalStoreRuntime, useExternalMessageConverter, their adapters and options), the message queue, the tool approval types, the generative UI renderer and the cloud thread list hooks; @assistant-ui/react-native gains VoiceSessionState, the cloud thread list hooks, the generative UI renderer and the runtime state and adapter types the web package already carried; @assistant-ui/react gains MessageRole, RunConfig, RuntimeCapabilities, RemoteThreadListOptions, ThreadsState, JoinStrategy, TitleGenerationAdapter, createSimpleTitleAdapter and ChainOfThoughtPartByIndexProvider. (@okisdev)

• #7520 2171a8e - fix(react): attach the ExportMarkdown download anchor to the document so Firefox starts the download (@Kinfe123)

• #8010 1c86c4c - fix: prevent disabled attachment dropzones from navigating to dropped files. (@Kinfe123)

• #7733 e2f1306 - fix: clear attachment drag state when the dropzone is disabled (@Kinfe123)

• #7897 16ef5b3 - fix(react): stop a pending bottom scroll from hijacking keyboard-driven content growth (@Kinfe123)

• #7762 4928364 - fix: resolve component registries by own keys only, so a component, tool or data part name that only Object.prototype has (toString, constructor, __proto__) takes the Fallback or GenerativeUIRenderError path instead of rendering the inherited built-in (@okisdev)

• #7725 258ad13 - fix: expose feedback submission state to assistive technology (@rupic-app)

• #7981 0252c69 - feat: name the runtime state types ThreadRuntimeState, MessageRuntimeState, ComposerRuntimeState, AttachmentRuntimeState and ThreadListItemRuntimeState (@okisdev)

  these are the states ThreadRuntime, MessageRuntime, ComposerRuntime, AttachmentRuntime and ThreadListItemRuntime return from getState(), now exported by all three distributions; @assistant-ui/react-native and @assistant-ui/react-ink had no name for them. in @assistant-ui/react, ThreadState, MessageState, ComposerState, AttachmentState and ThreadListItemState still name these runtime states but are deprecated: from 0.16 they name the store states useAuiState reads, as they already do in @assistant-ui/react-native and @assistant-ui/react-ink. code that annotates a runtime's getState() result should move to the new names.

• #8149 1b1ff55 - fix(react): keep the selection toolbar in sync after a right-click, so a context menu that swallows the mouseup no longer leaves it showing (and quoting) the previous selection (@samdickson22)

• #8065 2caacad - feat: a tool UI can record what the user did on its tool call with unstable_recordInteraction, kept on the part as unstable_interactions and stored in cloud history; the answer to a human input request is recorded once the runtime accepts it, the local runtime persists records and keeps them out of model input, external stores receive them through unstable_onRecordToolInteraction, and readonly threads ignore them (@okisdev)

• #7068 4b069f9 - fix: Use successful Standard Schema output for tool execution and model output. Keep the original arguments for validation errors and stored tool calls. (@ephraimduncan)

• #7777 c51ba8f - feat(core): let typed text enter a connected voice session through sendText (@okisdev)

  a RealtimeVoiceAdapter.Session (and the VoiceSessionControls returned to createVoiceSession) can implement sendText(text). while a running session takes typed text, VoiceSessionState.canSendText is true, the thread composer can send, and thread.append with a plain text user message hands the text to the session and commits it once as a typed turn (no metadata.modality) through the same path as a finalized transcript: the local runtime writes it to the repository and history, an external store receives it through onVoiceTranscript. the session must not echo the typed text through onTranscript. a session without sendText keeps rejecting typed sends as before. while a session is connected the send button and the Enter key follow canSend alone, so a reply being spoken no longer blocks them. the ai-sdk runtime keeps the message's own modality when it persists a voice session message, so a typed turn is no longer marked as spoken.

• #7716 3f4369b - fix: respond to touch and programmatic text selection changes (@Kinfe123)

• #6338 88143c2 - fix: restore the pre-clamp viewport position after a layout-induced scroll clamp on WebKit (@Kinfe123)

• Updated dependencies [b4f5153, aa83d87, d096801, 9b902fa, aa0f338, d8394bc, 63f3236, 6b93933, eb034f6, 5a8ff94, 2e3fd9e, 9f286dc, 920422c, 02043de, 9cb7aa4, 40ba7f0, 967de5d, b649669, 0ce62a8, 5d33fca, 92d16d7, a88fa97, 96e11d9, 3af3b61, e8fac8d, d403574, f71c285, 0ad784f, bbd01b5, 84e0cf4, fc3aa3e, 9eafe31, d97af06, e0b7805, 1c58865, 9619b42, 5496fce, f04c7f0, a4a2739, fdf5706, 443b0a5, 178e340, 1afdc46, dea2462, c45ae5a, 7face86, 0a9ed7b, 6407760, 4bed51f, 819c065, 21f8bdf, 8e1508a, e9c1ccd, 4928364, 5c5eb45, 11f9648, c5b5d3a, 7725cbd, 777df32, dcd43fd, a486a13, 0ee58d8, 0252c69, 75bd488, 7260270, 0cfd31e, c2e125e, 1790780, 662b607, f270950, 84cdbb0, 92e991a, 534e11f, 9da3697, e046327, 2caacad, e525f14, c171588, a5c9c5a, 4b069f9, d9e4086, 89c0f55, c51ba8f, e6aa5df]:

  • @assistant-ui/core@0.3.21
  • assistant-cloud@0.2.3
  • assistant-stream@0.3.45
  • @assistant-ui/store@0.3.15
  • @assistant-ui/tap@0.9.19

0.15.21#

Patch Changes#

• #7692 dbb1496 - fix: resume bottom following when auto-scroll is enabled at runtime (@Kinfe123)

• #7370 b7f9a96 - chore: update dependencies (@Yonom)

• #7518 d99c80e - fix: cancel the selection toolbar's pending animation frame on teardown and between selection events (@Kinfe123)

• Updated dependencies [43b587d, 5428610, 562e495, ddb7201, 69c3d0f, c046153, 4788b61, 99c9988, 37a5a95, 2caa1ce, bd77c46, e8cf372, 4e08ba6, b7f9a96, 50d65c0, 11969a2, 408d5f4, bc84250, f513bc7, b712ee8, e02bf06, 5c55222, 479d6a3, 44248e0, 70b633f]:

  • @assistant-ui/core@0.3.20
  • assistant-stream@0.3.44
  • assistant-cloud@0.2.2
  • safe-content-frame@0.0.31
  • @assistant-ui/store@0.3.14
  • @assistant-ui/tap@0.9.18

0.15.20#

Patch Changes#

• #7414 00cff0b - feat: add an opt-in cache to convertExternalMessages so a source message that has not changed keeps its ThreadMessage object across calls (createExternalMessageConversionCache, exported as unstable_createExternalMessageConversionCache from react and react-native); react-langchain uses it for subagent transcripts, so a streamed token no longer rebuilds every message of the nested transcript (@rupic-app)

• #7185 2c22f5d - fix: settle pending frame tool calls when cancellation fails (@Kinfe123)

• #7359 75b3bd3 - feat: derive thread.tasks from tool calls that carry nested conversations, with a task scope (@okisdev)

• #7213 cd42d1c - fix: keep notifying thread viewport scroll listeners after a listener fails (@Kinfe123)

• #7351 f6b7ba9 - feat: mark voice transcript messages with metadata.modality (@okisdev)

• Updated dependencies [628df88, ed77e95, 00cff0b, b821506, 79c2219, f0bbcec, c41d93a, 4cc817d, 4619335, 4e5fde6, e54bf9a, e54bf9a, c083236, 3cd7700, 617bbf9, 5fb3235, 83ede73, 49ee689, 49ee689, a8e0ff7, 050d915, d49ff90, e7bdef5, 69cbf47, 37bd676, be818db, ff1c692, b4b0081, 6b29e7d, de6d6b7, f6f52cd, ab97a41, 790217b, 8530b17, 063b9ec, 063b9ec, 2c22f5d, d7aa090, dacfcec, 7af9101, 63ae5b8, 97bd4b3, c0d6150, 275eeb9, e57c33f, e63d2e4, 75b3bd3, f03be0c, 06bdf1f, e533f6b, 28691a5, 3cfddfd, f6b7ba9]:

  • assistant-stream@0.3.43
  • @assistant-ui/core@0.3.19
  • assistant-cloud@0.2.1

0.15.19#

Patch Changes#

• #6971 9247ae3 - fix: honor message part text render elements with an explicit component. (@rupic-app)

• #6738 3c17a5f - fix: prevent queued live completion requests from starting after unmount (@Kinfe123)

• #7115 4767a92 - feat: align the cloud SDK with Assistant Cloud 0.2 (@okisdev)

  • run reports now carry provider, outcome_type (aborted, disconnected, length, content_filter), error_code and error, message_id, first_token_ms, duration_ms, a finish_reason per step from useCloudChat and trace_id, plus environment, release and tags from the telemetry config; one createRunReport builder in assistant-cloud assembles the body for the assistant-ui runtime and for @assistant-ui/cloud-ai-sdk, and provider_type and metadata stay on the wire for older self hosted clouds
  • assistant-cloud/telemetry (server side): createAssistantCloudTraceExporter, createAssistantCloudSpanProcessor, assistantCloudTraceMetadata and withAssistantCloudTraceMetadata send AI SDK GenAI spans to POST /v1/traces and hand the trace id to the browser, so a client report and its server spans merge into one run; the OpenTelemetry packages are optional peers of the subpath only
  • engagement events: sends, edits, stops, regenerates, copies, branch switches, suggestions, attachments, thread switches, speech, voice and shown errors are batched to POST /v1/events without any message content; telemetry.events: false opts out
  • cloud.scores.create for custom scores, and message feedback through useCloudChat().feedback next to the assistant-ui FeedbackAdapter
  • cloud.files.generatePresignedDownloadUrl and the object key on upload responses
  • CloudAPIError.code and details, including plan_limit_reached on a 402
  • @assistant-ui/core requires assistant-cloud@^0.2.0, and its store emits the composer, message and thread events the engagement reporter reads

• #6987 b8c5e68 - fix: compare arrays with indexed loops so sparse-array holes cannot read as equal; a sparse suggestions list now compacts to a dense one before it reaches the per-suggestion lookup (@Kinfe123)

• #6961 98010f1 - fix: notify controlled and uncontrolled modal owners when a run opens a closed modal (@ephraimduncan)

• #6985 7a82c22 - fix: keep parent IDs separate from ungrouped message parts (@ephraimduncan)

• #6843 24a288e - feat(cloud): claim anonymous threads into a signed-in workspace by exposing the browser's anonymous refresh token and moving its threads into an authenticated Assistant Cloud workspace after sign-in. (@okisdev)

• #6956 5e42b61 - fix: ignore flat mention items when categories is an empty list (@ephraimduncan)

• #6993 91689ab - chore: update dependencies (@Yonom)

• #6911 0d09f05 - Handle prototype-named tool and remote thread keys safely. (@rupic-app)

• #7014 03fe35b - fix: support WebMCP tool cancellation below AbortSignal.any's browser floor and with a non-native caller signal (@rupic-app)

• #7036 bb099f6 - refactor: extract the render-element Slot composition into one helper (@okisdev)

• #6893 b0a03ce - fix: apply tool allowlist changes to mounted MCP app frames (@ephraimduncan)

• #7159 e7a2ad0 - fix: reset message stall detection after equal-length content changes (@Kinfe123)

• #6888 34af371 - fix: preserve the requested scroll behavior across nested viewport providers (@ephraimduncan)

• #6960 4b88b57 - fix: render message part text inside the supplied render element. (@ephraimduncan)

• #6876 912f5c5 - fix: reject quote selections that cross excluded content (@ephraimduncan)

• #7186 6a3e11b - fix: finish sandbox teardown after bridge cleanup errors (@Kinfe123)

• #6931 5febc06 - refactor: adjust state during render where an effect only mirrored a prop (@okisdev)

  The composer trigger's keyboard and navigation resources, and the devtools panel and thread tab, reset their state during render instead of scheduling a second pass from an effect, so a prop change settles in one render. Effects that genuinely synchronize with an external system (a clock, a subscription catch-up, an async load, a registry write undone on unmount) keep their setState.

• #7121 94c3fd5 - fix: cancel WebMCP tools while asynchronous validation is pending (@Kinfe123)

• #7177 3257a47 - fix: stop MCP App bridge messages after disposal (@Kinfe123)

• #6983 bb8249d - fix: forward every part renderer option through MessagePrimitive.Parts, so data renderers survive ChainOfThought (@ephraimduncan)

• #6837 191bd97 - fix(react): keep the page from shifting sideways when a collapsible opens (@okisdev)

  useScrollLock hides the scrollbar for the length of the animation and pads the scroll container to keep its width, but it measured the bar as offsetWidth - clientWidth minus borders. A root element's offsetWidth already excludes the viewport scrollbar, so that reported zero whenever the scroll had propagated to the viewport, no padding was added, and every centered element jumped sideways as the collapsible opened and back as it closed. A root scroller now falls back to measuring against innerWidth, but only when the element formula reports nothing, so a body that scrolls in its own right is still padded by its own gutter.

• Updated dependencies [a360dda, bf2cbbc, 931b808, 318e4da, 57ce984, 0ab9b12, 3bcd6db, 93d1526, 0b1c5a1, 7f6e012, 4767a92, c9e03ef, 71cc3ff, b8c5e68, 24a288e, 91689ab, a16b990, 571cd7c, 96f011a, f044254, a19db37, 18c12e6, 253c80d, 0d09f05, e6158c8, 623d5ff, ddb7503, 73b24d5, 71c5416, 07eeb54, 2c1e65e, d4fbb2a, a9efcfa, 12c5447, 6c85699, 9b9d5e9, 4802e15, 071a879, 0529e2d, 27a3442, d777777, 5630967, 40f0978, ce22d18, 928c580, 9a882be, afac9e0, 4cdcabb, 73a1e76, 5febc06, 56f13b5, 23d2865, 08088b4, b505555, 7ea4669, b2d12e7, 01fdd4b, 59a8251, a05828f, ef584ea, 84b6ae2, 6f0d7af, 441168d, f756047, 306bed1, 1f80dd0]:

  • @assistant-ui/core@0.3.18
  • @assistant-ui/tap@0.9.17
  • safe-content-frame@0.0.30
  • assistant-stream@0.3.42
  • assistant-cloud@0.2.0
  • @assistant-ui/store@0.3.13

0.15.18#

Patch Changes#

• #6723 8cc962e - feat: let a tool approval request describe itself and report its outcome (@okisdev)

  an approval carries prompt, display, and allowFreeform, so a renderer can tell a question from a permission gate without reading provider metadata, and ToolApprovalResponse gains a text answer that resolves the request as answered rather than approved. respondToToolApproval now returns a promise that rejects when the runtime could not record the response, instead of the external-store runtime logging the rejection away, so a refused response leaves the request retryable.

• #6762 39c99b5 - fix(react): keep trigger callbacks commit-safe (@Kinfe123)

• #6640 79c1465 - fix: load newly mounted MCP Apps through the committed host (@Kinfe123)

• #6580 dc2cab3 - chore: drop a superseded internal hook and a dead plugin-registry variant (@okisdev)

• #6710 a83be6b - fix(react): accept spec-shaped MCP App messages (@rupic-app)

  the default sendMessage handler now reads the MCP Apps { role, content } params and appends each text block in order, alongside the existing string, { prompt }, { text }, and { message } forms. rejections now also carry the spec's isError: true, and the legacy ok and reason fields stay on the result so widgets already reading them keep working.

• #6706 6194f3e - fix(react): keep model-context mentions current and honor explicit tool categories without requiring custom categories (@Kinfe123)

• #6528 152a35d - chore: update dependencies (@okisdev)

• #6629 98b7213 - feat: resolve MCP App renderer options per part (@okisdev)

  McpAppRenderer served every MCP app in a thread from one static options snapshot, so a host could not give one app its own displayMode and could not tell which app called requestDisplayMode. Renderer options now reach each part through the renderer store, and a new forPart resolver overrides hostContext, maxHeight, sandbox, hostInfo, and the fallbacks for a single part. handlers merges per key instead, so adding a per-part requestDisplayMode keeps the thread-wide handlers for that app. Host context changes are compared structurally before they are pushed over the bridge, so a resolver may rebuild its result on every render.

• #6586 9f08bdc - chore: reuse the shared viewport math and callback invoker (@okisdev)

• #6639 05e3e6d - chore: update dependencies (@Yonom)

• #6615 e7bcf83 - fix: report a sandboxed frame that never finishes loading through onError, and re-export the ShimLoadError and ShimLoadErrorCode types it is reported with (@okisdev)

• #6714 0f3140d - refactor(react): extract a shared model-context snapshot hook for the mention adapter and the webmcp provider (@okisdev)

• #6540 99db167 - feat: unstable_useWebMcpProvider, publishing frontend tools to a WebMCP-capable browser (@samdickson22)

• #6703 21cbb78 - refactor: collapse the three trigger-item query predicates onto one shared helper (@Kinfe123)

• #6614 1b25b22 - refactor: dispose WebMCP registrations through the abort signal alone (@okisdev)

• Updated dependencies [8cc962e, 2a31285, 6083062, 205acf5, 740a573, 65d449b, 79283c5, 9ec29e1, 14fc938, 3f7af8b, 46fad14, 5511057, dc2cab3, d75944b, 99fd86e, 6bd1570, 7f7bd54, 60ae973, 9f08bdc, 0fb5390, dc2cab3, f0d0aa2, 1fa3e09, 5972a5e, 0f17ba5, 152a35d, 0c5c574, ddaac94, 0c68179, 250f69c, c22a3dc, aca6e30, 5bdd416, 6fdfc23, 136bbf5, e53299b, 69d8e1b, dabe8f2, 8d128af, 9f08bdc, e7bcf83, 47a46db, 8135d16, 07fed43, fa9c0dc, fa9c0dc, 4ca7de9, 65d449b, 49e727b, 49e727b, d9eae73, d56a66a, 96a2df8, 8206d8f]:

  • @assistant-ui/core@0.3.17
  • safe-content-frame@0.0.29
  • assistant-stream@0.3.41
  • assistant-cloud@0.1.43
  • @assistant-ui/store@0.3.12
  • @assistant-ui/tap@0.9.16

0.15.17#

Patch Changes#

• #6404 6bb1c8b - fix: keep MCP App server routing scoped to committed renders (@Kinfe123)

• #6389 bac7cd6 - fix: keep sandbox bridge options scoped to committed renders (@Kinfe123)

• #6335 1d2e68b - chore: drop unreachable legacy forwarding sources. (@okisdev)

• #6207 36edccb - feat: export createSuggestionAdapter and its option types from the distribution packages (@Kinfe123)

• #6458 465a7a6 - fix: default assistant frame messaging to the current origin (@Kinfe123)

• #6370 16eb703 - fix: keep committed MCP App host options active during interrupted renders (@Kinfe123)

• #6239 8aa3022 - fix: expose MCP App renderer handlers (@rupic-app)

• #6406 95ed44d - fix: keep slash commands scoped to committed renders. search now matches the displayed label, so a command with no explicit label is matched on its /id fallback rather than only on id and description. (@Kinfe123)

• #6192 08611a0 - chore: import Radix internals from radix-ui/internal and drop the individual @radix-ui/* dependencies (@Yonom)

• #6305 e96d3de - chore: update dependencies (@okisdev)

• #6390 13c5997 - fix: keep live completion fetchers scoped to committed renders (@Kinfe123)

• #6284 1424afb - feat: allow trigger popovers to override query matching (@dawNotPoi)

• Updated dependencies [c70c911, e0fa1e6, b2f148e, 9dabbce, 0f0ebb6, 5a3e9f7, d24bcb2, 7adf047, 43d52ad, cdfc34d, 8626c1f, 4000eed, 8217a6e, 3fcf338, 4802d23, c3fd2b3, 231d148, 7e03b66, 1743d19, 1263c1f, 465a7a6, 531f61a, 5355528, e97f7c6, a6d2da5, 6b797ca, bea47ed, dfaa94f, a4bc54a, 546dae8, a06be56, 96d4ddf, fd471e9, c8db434, bc55058, 0221348, c415384, 5bba723, 0188899, ac7ec15, e96d3de, 027f5e2, ebabca4, f96e22f, fc7f72f, bfc8bef, 2cd5cbc, 105af3e, 4c3194a, 0064d1e]:

  • @assistant-ui/core@0.3.16
  • assistant-cloud@0.1.42
  • assistant-stream@0.3.40
  • safe-content-frame@0.0.28
  • @assistant-ui/store@0.3.11
  • @assistant-ui/tap@0.9.15

0.15.16#

Patch Changes#

• #6136 f7bd2d9 - fix: keep DevTools updates flowing when a subscriber throws (@Kinfe123)

• #6055 1f3eaa7 - fix: contain SandboxHost render failures after teardown (@Kinfe123)

• #6110 48f95b1 - chore: delete the dead ensureBinding and useRuntimeState utilities (@samdickson22)

  src/context/react/utils/ensureBinding.ts and
  src/context/react/utils/useRuntimeState.ts imported only each other. Nothing
  else in the repo referenced them, neither appears in the package barrel or the
  api-surface snapshot, and the "."-only exports map made them unreachable to
  consumers. ensureBinding was an external caller of __internal_bindMethods
  that no longer had a caller of its own; the runtime classes bind themselves in
  their constructors, so nothing changes at runtime. The public API surface is
  unchanged and every other emitted file is byte-identical.

• #6156 9c65b51 - deprecate leftover Primitive.If and Empty wrappers on react-native and react-ink, and point them at AuiIf (@okisdev)

  ThreadIf now reads thread.isEmpty instead of messages.length === 0, matching the loading-aware field already used by ThreadEmpty and AuiIf. First-party examples and docs samples that still called the leftover wrappers now use AuiIf directly.

• #6084 ca9e72c - fix: resync trigger popover cursor after selection (@rupic-app)

• #6054 59e9a08 - fix: handle rejected asynchronous Markdown exports (@Kinfe123)

• #6098 b9b9dad - fix: drain unrevealed smooth text when a message completes before any frame (@rupic-app)

• #6061 75dfbe3 - docs: document Escape-to-stop-speaking on ThreadPrimitive.Root (@samdickson22)

• #6124 06b04a7 - chore: update dependencies (@okisdev)

• Updated dependencies [fa30915, b355aef, f7bd2d9, 4947ef4, 332f736, ef9254d, 9c65b51, 5845ba7, 1b30bfd, 365e763, d19921d, 996aa57, 21d6e87, cd247e5, f2b3ef8, 1bf263b, 19e52c4, 06b04a7, a614b5e, 07b51db, 92e52bd]:

  • @assistant-ui/core@0.3.15
  • @assistant-ui/tap@0.9.14
  • assistant-stream@0.3.39

0.15.15#

Patch Changes#

• #6071 c3fd447 - feat: host assistant-cloud thread lists on AISDKThreads via RemoteThreadList (@okisdev)

  AISDKThreads({ cloud }) uses RemoteThreadList and remounts each thread like useChatRuntime. Cloud history withFormat resolves persistence per call so one adapter can serve many threads. useExternalHistory waits for threadListItem.remoteId instead of latching on the first empty paint.

• #5872 f9529bf - feat: move useAssistantTransportRuntime into core/react (@okisdev)

• #5872 f9529bf - fix: persist data message parts in aui/v0 cloud history (@okisdev)

• #5839 24a1af7 - fix: validate MCP App resource responses (@Kinfe123)

• #5817 dab7b7a - fix: dispose sandbox frames when bridge setup fails (@Kinfe123)

• #6005 4326079 - feat: move useCloudThreadListRuntime into core/react and drop the unused react copy of the aui/v0 codec (@okisdev)

• #5952 3e2fa6e - fix: await assistant transport response callbacks and cancel unfinished responses when they fail (@Kinfe123)

• #5990 f439663 - fix: keep bottom follow through a content-growth undershoot (@okisdev)

• #5891 a20c2ef - fix: refresh live completion results after their data source changes (@Kinfe123)

• #5406 f2c37ec - fix: keep MCP App error replies reliable when error callbacks throw (@Kinfe123)

• #5981 f28ffae - fix: isolate MCP App notification callback errors (@rupic-app)

• #5942 285392a - fix: isolate assistant transport lifecycle callback failures (@Kinfe123)

• #5959 9d920cc - fix: InMemoryThreadList restarts with a fresh thread when the last one is deleted, notifies the new onDelete callback, and applies deletes batch-safely; the export is now sourced from the core store entry (@okisdev)

• #5618 82e2bde - fix: top-anchor turn clears skip turns that are still valid (@Yonom)

• #6037 f5b39d4 - feat: add RemoteThreadListAdapter.unstable_useAdapters so the RemoteThreadList store entry can load per-thread history without rendering unstable_Provider (@okisdev)

• #6020 26f40c1 - feat: add a RemoteThreadList store entry so any AssistantClient host can run a remote thread list from a RemoteThreadListAdapter and a thread factory (@okisdev)

• #5992 adcfe01 - fix: preserve bottom follow through viewport clicks and cancel stale auto-scroll frames (@rupic-app)

• #5499 5dff06c - fix: keep Escape-to-stop-speaking active when message action bars are hidden by moving the shortcut to ThreadPrimitive.Root; custom compositions must mount the root to enable it (@Kinfe123)

• #6058 837ef1b - fix: render system messages safely when editing components are omitted (@rupic-app)

• #5914 0d2e23f - feat: new threads.selectionChanged event carrying threadId and previousThreadId; deprecate threadListItem.switchedTo/switchedAway in its favor. Un-deprecate the semantically meaningful events (thread.runStart, thread.runEnd, thread.initialize, composer.send, composer.attachmentAdd). (@Yonom)

  The new event fires in situations where the deprecated pair did not, so the selection-driven defaults (scrollToBottomOnThreadSwitch, unstable_focusOnThreadSwitched) now engage there too: InMemoryThreadList emits on selection changes (it previously emitted no switch events at all), switchToNewThread() emits for the newly created thread, and runtimes that resolve a deep-linked threadId/initialThreadId after mount (useRemoteThreadListRuntime) emit when the deep link resolves, with the initial placeholder thread as previousThreadId.

• #5838 2a512eb - fix: handle synchronous live completion failures (@Kinfe123)

• #5774 61d29f4 - chore: update dependencies (@Yonom)

• #5631 7ea9de1 - feat: runtime suggestions can carry a display title and label (@samdickson22)

  ThreadSuggestion gains optional title and label, so an adapter can show a
  short pill while still sending the full prompt. useThreadSuggestions now
  passes them through instead of hardcoding title: prompt, falling back to
  title ?? prompt and label ?? "" so prompt-only suggestions render exactly as
  before. SuggestionConfig is unchanged; the change is additive.

• Updated dependencies [99c5302, ac0c836, c3fd447, f9529bf, f9529bf, bd01e8b, 05b94bd, cef671d, ef7f70d, 4a2a76f, 04e967c, 39db2ff, 0e91e27, c5bc8ed, a2a753b, 2b0fec7, bec0753, 4326079, 3d68b16, 98795aa, 9d920cc, 1b9c33d, d68918e, 74dca03, 87bf950, 5a01343, 0f6e9e9, f0d1d48, b80a6be, 01580e3, ab7f49f, e8c53e9, 53ae80f, 5f4dee5, d79b87d, 645c56b, 61d29f4, 2da61a3, 0131fc7, a934d03, b6d7b2b, bc337af, dc6eb2f, ce57458, ab7ead9, 067ef52, f44163f, e5bf0ef, a2ab997, fc9dd90, 0e2a230, d800f8b, f5b39d4, 26f40c1, f618ab6, d80e988, 7f944be, f37f595, 74dca03, 1b9c33d, 82e2bde, 52df42d, 6c9e7dd, 837ef1b, 5c092ef, 2f3c638, 8e77515, d9c355d, 74dca03, a14b347, e999f5d, 44d98d7, 4320fc6, d4b8845, 74dca03, a279301, d7322c0, 8b0a836, 20efa42, 833fbe8, 94a39ad, 74dca03, 74dca03, 7748e15, 72705c3, 0d2e23f, 4446d45, e8997d9, bfe47b6, ceb8c16, 61d29f4, 7ea9de1, 72a6272, 51886b2, 3053195, 44e574f, 14c3b5a]:

  • @assistant-ui/tap@0.9.13
  • @assistant-ui/core@0.3.14
  • @assistant-ui/store@0.3.10
  • assistant-cloud@0.1.41
  • assistant-stream@0.3.38

0.15.14#

Patch Changes#

• #5760 a4ac7dd - fix: release replay response readers after completion, cancellation, and errors (@Kinfe123)

• #5764 47b9256 - fix: generate unique in-memory thread IDs (@Kinfe123)

• #5789 d3fece3 - feat: give the composer its draft back when a send never reached the backend. a runtime that rejects onNew with the new MessageNotSentError restores the text, quote, and attachments the composer cleared at dispatch time, as long as nothing has claimed the composer since. that guard and that outcome are the ones cancelRun already applies to a trailing user message, so whichever fires first keeps the composer, and of several drafts queued behind one turn only the most recent is still restorable. an edit composer closes at dispatch, so a rejected edit is not restored. (@okisdev)

• #5828 685a069 - feat: wire threads.reloadMainThread() through the tap ExternalThread path via a new onRefetchThread callback, with the refetchThread capability derived from its presence (@okisdev)

• #5757 092585b - fix: derive the suggestions scope from the thread so runtime-provided suggestions render through ThreadPrimitive.Suggestions (#5529) (@okisdev)

• Updated dependencies [a90db30, cfb5fab, 65e03a6, d3fece3, 4b75b8f, 1e98bcf, 82cbc15, e28a62d, 8bba3aa, 48af3c5, 22fa20f, 00a630a, 417efee, 1e1d52b, c98699d, 685a069, f59d24b, 092585b]:

  • @assistant-ui/core@0.3.13
  • @assistant-ui/store@0.3.9
  • assistant-cloud@0.1.40
  • @assistant-ui/tap@0.9.12

0.15.13#

Patch Changes#

• #5745 1df4327 - refactor: move ExternalThread, SingleThreadList, and the Assistant augmentation namespace into @assistant-ui/core (@Yonom)

• Updated dependencies [1df4327]:

  • @assistant-ui/core@0.3.12

0.15.12#

Patch Changes#

• #5730 6c9560d - chore: drop dependencies that are never imported (@okisdev)

• Updated dependencies [f551562, dc7b77d, 0ae51a8, d1b7097, e319574]:

  • @assistant-ui/core@0.3.11
  • assistant-stream@0.3.37

0.15.11#

Patch Changes#

• #5723 94dc3e5 - chore: update dependencies (@okisdev)

• #5722 7faf0fb - fix: ExternalThread edit composer reads editing state live, so a same-tick beginEdit + setText + send dispatches the edit; send before beginEdit and double beginEdit now throw (legacy runtime parity) (@Yonom)

• Updated dependencies [94dc3e5, ab57969]:

  • assistant-stream@0.3.36
  • assistant-cloud@0.1.39
  • @assistant-ui/core@0.3.10
  • safe-content-frame@0.0.27
  • @assistant-ui/store@0.3.8
  • @assistant-ui/tap@0.9.11

0.15.10#

Patch Changes#

• #5720 ab9e765 - fix: route sourceId-carrying edit sends to onEdit instead of the queue adapter, and fail fast on beginEdit without an edit handler (@Yonom)

• Updated dependencies [ab9e765]:

  • @assistant-ui/core@0.3.9

0.15.9#

Patch Changes#

• #5717 99d09c8 - Edit composer send always emits: an unchanged edit re-sends the message on a new branch instead of silently closing the composer. (@Yonom)

• #5713 f105884 - feat: feedback adapter support in ExternalThread (@Yonom)

• #5712 44f6a94 - feat: speech synthesis adapter support in ExternalThread (@Yonom)

• #5702 7d0265e - fix: allow failed live completion searches to be retried (@Kinfe123)

• #5639 79253f2 - feat: preserve app-authored reasoning summaries on message parts (@rupic-app)

• #5701 ca49427 - fix: clear dropped assistant transport resume requests (@Kinfe123)

• Updated dependencies [456b056, 99d09c8, a88751d, 79253f2, 4e99deb, 2af514c]:

  • assistant-stream@0.3.35
  • @assistant-ui/core@0.3.8
  • @assistant-ui/store@0.3.7

0.15.8#

Patch Changes#

• Republish of 0.15.6 (registry staged-version conflicts blocked 0.15.6 and 0.15.7; contents identical).

0.15.6#

Patch Changes#

• #5664 3b0d778 - fix: gate ComposerPrimitive.AttachmentDropzone on file drags and the attachments capability (@ShobhitPatra)

• #5666 366da2b - fix(react): route only thread-composer sends into the queue adapter (@Yonom)

• Updated dependencies [bd4c0ad, 4aa1b1d, bd4c0ad]:

  • @assistant-ui/core@0.3.7
  • @assistant-ui/store@0.3.5

0.15.5#

Patch Changes#

• #5476 02b9dc1 - fix: allow callers to override the default type="button" on action button primitives (@ephraimduncan)

• #5564 31a427a - fix: hydrate assistant transport resumes from their retained initial state (@Kinfe123)

• #5415 271d85d - fix: AttachmentPrimitive.Thumb now renders custom children and supports asChild instead of always overriding them with the automatic label (@ephraimduncan)

• #5421 e7a696c - fix: AttachmentPrimitive.Thumb no longer renders a bare "." for extension-less filenames; falls back to the attachment type (@ephraimduncan)

• #5430 dcacd9b - feat: AuiProvider extends/config grammar. config={AuiConfig({...})} alone creates a top-level root client; nested providers must pass extends — a client to extend, or null to isolate (dev-enforced). An empty config creates a client extending the extends client; ref exposes the resulting client. The config prop only accepts configs built with AuiConfig(...) (branded type). AssistantRuntimeProvider gains an optional config prop whose scopes are provided alongside the runtime scope. The useAui({...}) extension overload and the AuiProvider value prop are deprecated; value={client} now exposes a client extending the given one (same scopes, new identity) rather than the exact instance. useAui({}) with an empty scope object now mounts a rooted host (so the scope set can grow across renders) instead of a passthrough derived-only client. useAuiState state enumeration (Object.keys/spread) now includes scopes inherited from parent clients, matching in-operator behavior. Clients derived from a hand-built parent (a plain object with subscribe/on) forward scoped on(...) listeners to the parent's on instead of throwing for scopes the parent does not expose. (@Yonom)

• #5416 c5b88f1 - fix: ignore Escape during IME composition in ComposerPrimitiveInput so dismissing a composition candidate no longer cancels the composer (@ephraimduncan)

• #5420 129d0c1 - fix: defer blob URL revocation in ActionBarPrimitive.ExportMarkdown so the download fetch can start before the URL is revoked (@ephraimduncan)

• #5585 1160d8b - fix: settle assistant transport runs when finish callbacks fail (@Kinfe123)

• #5418 cc85bf4 - fix: compose SelectionToolbarRoot onMouseDown with composeEventHandlers so user handlers run before preventDefault (@ephraimduncan)

• #5650 34cec64 - feat: two-lane, placement-aware message queue with steer-by-default mid-run sends (@Yonom)

  ExternalThreadQueueAdapter is reshaped: enqueue(message, { steer }) splits into
  enqueue(message) / steer(message), steer(queueItemId) becomes
  move(queueItemId, { lane: "steer", insertAfter: null }), clear(reason) is dropped
  (queue clear policy is now host-owned), and steerItems / move / edit and
  QueueItemState.parts are required.

• Updated dependencies [dcacd9b, d52928d, d8a59ad, e70da91, aac3a8c, aa302ee, aa302ee, 71cf74e, 34cec64]:

  • @assistant-ui/store@0.3.4
  • @assistant-ui/core@0.3.6
  • assistant-stream@0.3.34
  • @assistant-ui/tap@0.9.10

0.15.4#

Patch Changes#

• #5566 7528465 - fix: skip add-message commands with no supported parts in assistant transport runtime (@Yonom)

• #5565 78943a3 - feat: add opt-in strict: false mode that reconciles malformed stream input instead of throwing (decoders, state accumulator); assistant-transport resume runs always decode leniently (@Yonom)

• Updated dependencies [7f7f8a2, 6c062f1, 78943a3]:

  • @assistant-ui/core@0.3.5
  • assistant-cloud@0.1.38
  • assistant-stream@0.3.33

0.15.3#

Patch Changes#

• #5432 8ca9930 - fix: refresh MCP App resources when the host changes (@Kinfe123)

  Custom McpAppsHost resources must now return a stable object identity (for
  example, with useMemo); an unstable host keeps the widget in
  loadingFallback and refetches on every re-render.

• #5447 8c99934 - docs: deprecate Unstable_AudioMessagePart in favour of file parts (@okisdev)

  Audio belongs on a file part with an audio/* mime type. file is a member of both the user and assistant unions and carries a filename, neither of which the audio part can express. The payload form a file part needs is still adapter specific; the message primitive docs enumerate it. The audio part and the Unstable_Audio slot stay honored everywhere they are accepted and will not gain fields.

• #5439 ece5a54 - feat: sourceType opt-in on file message parts so attachment adapters can send url/id file references (@ShobhitPatra)

• #5542 55b2824 - feat: expose threadListItem.isRunning so a thread list row can show its own run (@okisdev)

  a thread list row had no supported way to tell whether its thread was running: thread.isRunning describes the open thread, and the item state carried no run state at all, so a run continuing on a thread the user had switched away from was invisible.

  threadListItem.isRunning now reports it, and stays true for a background run. runtimes that keep background threads alive answer it through the new optional ThreadListRuntimeCore.unstable_isThreadRunning; the rest report the open thread's run state, which they already track.

  InMemoryThreadList also renames threads for real instead of dropping the new title.

• #5537 c868710 - fix: keep a settled tool call distinguishable from an unfinished one, so a tool returning false, 0, "" or null no longer loses its result on the cloud round trip and no longer reads as never completed (@okisdev)

• #5522 f913c21 - feat: add threads.reloadMainThread() to refetch the open thread's remote state in place (@taoche)

• #5417 5bb2573 - fix: suggestion trigger with send no longer overwrites the composer draft while a run is in progress; on runtimes without queue support it now renders disabled mid-run, matching ComposerPrimitive.Send (@ephraimduncan)

• Updated dependencies [b19c2f5, 01140bd, 8c99934, ece5a54, 2fdff87, 90b3003, 4c313cf, 55b2824, 22b05a4, f913c21, c868710, 011e275, da32fe0, f913c21, 5bb2573, 71231d3, 5ececc1]:

  • @assistant-ui/core@0.3.4
  • assistant-stream@0.3.32
  • @assistant-ui/store@0.3.3
  • safe-content-frame@0.0.26

0.15.2#

Patch Changes#

• #5419 aa74b0d - fix: enumerate the attachment content fields the aui/v0 encoder persists so per-part status stays out of the stored shape (@okisdev)

• #5403 6e5c450 - refactor: share the part status derivation with core (@okisdev)

• Updated dependencies [aa74b0d, 6e5c450, 59ec21b, 4fd698b, b8daa96]:

  • @assistant-ui/core@0.3.3
  • @assistant-ui/tap@0.9.9

0.15.1#

Patch Changes#

• #5304 1bbaa46 - refactor: internal selectors read optional scopes via s.optional.part instead of guarding on aui.part.source (@Yonom)

• Updated dependencies [1bbaa46, 3a762ed, 9aac054, a8cd1c9]:

  • @assistant-ui/core@0.3.1
  • @assistant-ui/store@0.3.1
  • assistant-stream@0.3.30

0.15.0#

Minor Changes#

• #5275 9a7e776 - feat: property API for aui — nullary scope accessors are now properties (aui.thread.getState() instead of aui.thread().getState()); calling them still works but is deprecated. Accessors keep source/query/name selection metadata as properties; these are reserved names for scope methods. An unavailable scope's accessor no longer throws at selection time: aui.thread always succeeds and is always truthy, .source is null, and any other property read (or a call) throws — check availability via aui.thread.source != null. Accessor identity is binding-keyed: stable across renders without structural change, new on structural change — memoization keyed on an accessor now invalidates exactly when its binding changes. (@Yonom)

• #5281 2f5d0d4 - feat: drop APIs deprecated in v0.12/v0.14 — the legacy context hooks (useAssistantRuntime, useThreadRuntime, useThread, useMessageRuntime, useMessage, useComposerRuntime, useComposer, useMessagePartRuntime, useMessagePart, useAttachmentRuntime, useAttachment, useThreadListItemRuntime, useThreadListItem, useThreadList, useEditComposer and their attachment variants; use useAui / useAuiState), the component-only ToolsState.tools map (use toolUIs), and the "mcp-app" group key in groupPartByType (use "standalone-tool-call"). See the v0.15 migration guide. (@Yonom)

Patch Changes#

• Updated dependencies [9a7e776, ae5f831, a196711, f78e579, dcc41bb, d72c2b6, 2f5d0d4]:
  • @assistant-ui/store@0.3.0
  • @assistant-ui/core@0.3.0
  • assistant-stream@0.3.29
  • @assistant-ui/tap@0.9.7

0.14.29#

Patch Changes#

• #5241 c2b7a29 - fix(assistant-transport): a follow-up run that finds an empty command queue no-ops instead of erroring "No commands to send" (@Yonom)

• #5238 cc763a5 - fix: assistant-transport marks in-transit commands delivered when a run completes successfully without state chunks, instead of leaving them pending forever (@Yonom)

• #5242 72f65dc - fix(assistant-transport): onError reads the live in-transit commands at error time instead of a stale render snapshot (@Yonom)

• #5240 98ac314 - fix: assistant-transport consumes parentId once per run; later unrelated runs no longer re-send the last append's parentId (@Yonom)

• #5249 525ab84 - fix(assistant-transport): commands enqueued during a resume run are flushed in a follow-up run instead of starving in the queue (@Yonom)

• #5243 468a713 - fix(assistant-transport): abort the in-flight run on unmount instead of leaking the fetch (@Yonom)

• #5219 3ca19cf - fix: stop logging attachment-add rejections to the console from ComposerPrimitive.AttachmentDropzone and ComposerPrimitive.Input; the rejection is already surfaced via the structured composer.attachmentAddError event, so the per-file console.error produced unopt-outable duplicate noise for apps handling the event (@rupic-app)

• #5208 a0ddc86 - Adopt erasableSyntaxOnly; public enums are now as const objects. (@Yonom)

• #5256 cee74f1 - fix: ExternalThread validates the adapter accept string on every addAttachment entry point (@Yonom)

• #5237 cf839ff - feat: ExternalThread props for assistant-transport (isLoading, state, extras, onResume, onAddToolResult, onLoadExternalState, onResumeToolCall, attachmentAdapter; importExternalState); export ToolInvocationTracker from core internal; composer parentId, draft-restore, and part-status fixes (@Yonom)

• #5257 1a875ab - fix: ExternalThread clearAttachments/reset call adapter.remove for pending attachments (@Yonom)

• #5258 7ecf87a - fix: ExternalThread edit composers receive the attachmentAdapter (@Yonom)

• #5261 fedcb05 - fix: ExternalThread merges a failed send back into the draft (text prepended, attachments and quote preserved) (@Yonom)

• #5259 b549575 - fix: ExternalThread queue-adapter sends stamp the thread head as parentId (@Yonom)

• #5260 8988d44 - fix: ExternalThread throws a capability error when an unset optional callback is invoked (@Yonom)

• #5116 396ea1f - fix(core): persist LocalRuntime runs paused for tool approval (@serhiizghama)

• #5227 2260850 - fix: handle rejected file picker attachment additions (@Kinfe123)

• #5262 801781c - ExternalThread: dedupe duplicate message ids with a warning (last occurrence wins) instead of throwing on duplicate resource keys. (@Yonom)

• #5231 e1f27d8 - fix(core): preserve thread-list position when switchToThread's on-demand fetch settles after a concurrent list() (@rupic-app)

• Updated dependencies [f9c1b0f, 235c17e, 6225d6a, 801781c, d4bdf2c, a0ddc86, cee74f1, cf839ff, 396ea1f, e1f27d8, 3e8f59e, 8c97501, 7e871ef, 06f5266, d319637]:

  • assistant-stream@0.3.28
  • @assistant-ui/core@0.2.23
  • @assistant-ui/store@0.2.22
  • @assistant-ui/tap@0.9.6
  • assistant-cloud@0.1.37
  • safe-content-frame@0.0.25

0.14.28#

Patch Changes#

• #5059 fd83a3a - fix: prevent instant auto-scroll from interrupting active top-anchored runs (@Gujiassh)

• #5083 cbe5f4e - feat: focus composer input when clicking blank space in ComposerPrimitive.Root (@AVGVSTVS96)

• #5119 70347f0 - fix: tolerate a transient part-type mismatch in the part hooks so a thread switch can't throw inside useSyncExternalStore and unmount the app (@rupic-app)

• #5168 69969f6 - fix: keep controlled assistant-visible inputs in sync after edits (@Kinfe123)

• #5097 039b75f - fix: support attachments without relying on a global File constructor (@Kinfe123)

• #5133 3b50540 - Warn against throwing from part selectors and keep React Ink part rendering stable during transient part-type mismatches. (@Gujiassh)

• #5085 9b99189 - fix: preserve the top-anchor reserve between turns (@Gujiassh)

• #5079 390e417 - chore: update dependencies (@Yonom)

• Updated dependencies [8630186, 908ec91, 0d0834d, 3355098, 3f90440, 79034bb, 7207b19, 446a118, a081656, 25a5be0, b17d392, 7492368, 20643e2, 47562fd, ccebbf9, 85d7c25, 23a9925, 7fde141, afacb10, af6c945, 33924df, 19cfdcd, 044def8, 039b75f, 5e4dd9f, 5da0d93, 85d4976, 5135400, fc6b4ad, 121ee83, 2b2587a, ca80153, e4ce1a2, f2f5e83, ec8ee6a, 9a343db, 666aaab, c1b1750, f263c9e, 475fca3, 8faad07, 61518b9, ecd2280, 83d7b42, 5c54141, 5412099, 99da4af, 1eb7275, c47bdf4, ba948d8, de54334, 44aac58, 9402648, 4651ea5, 2f69f68, 390e417, 2bc6798]:

  • assistant-stream@0.3.27
  • @assistant-ui/core@0.2.22
  • assistant-cloud@0.1.36
  • safe-content-frame@0.0.24
  • @assistant-ui/tap@0.9.5
  • @assistant-ui/store@0.2.21

0.14.27#

Patch Changes#

• #4818 b967668 - feat: render prop support for AssistantModalPrimitive Trigger, Anchor, and Content (@okisdev)

• #4754 438ecd3 - fix: preserve user attachments in Cloud history (@Kinfe123)

• #4701 7577c9a - feat: add compact mode to ComposerPrimitive.Root (@ephraimduncan)

• #4971 5dbbac4 - refactor: host the shared JSON type guards in @assistant-ui/core/internal (@okisdev)

• #4723 7310d8d - fix: add MCP App host request error context (@Kinfe123)

• #4675 c814c9c - feat: support prefixed MCP toolkit tool names (@Kinfe123)

• #4665 6be3b67 - feat: support disabled MCP toolkit entries (@Kinfe123)

• #4667 c590a21 - feat: support disabled MCP toolkit tools (@Kinfe123)

• #4746 0686f4e - chore: update dependencies (@Yonom)

• #4898 a84cf6d - feat: plumb an optional serverId through MCP Apps metadata and host calls for multi-MCP routing (@okisdev)

• #4806 9f99c46 - feat: preserve providerMetadata on text, reasoning, and tool-call message parts (@DLOVRIC2)

  The AI SDK message converter already kept providerMetadata on source parts but
  dropped it on text, reasoning, and tool-call parts (where the AI SDK surfaces it
  as callProviderMetadata). Provider- or app-scoped metadata such as agent
  attribution now survives the conversion to assistant-ui messages.

• #4863 0034c02 - feat: support data-aui-quote-selectable="false" exclusions (@okisdev)

• #4710 f1c7833 - feat: support opt-in quote regions for the selection toolbar (@Kinfe123)

• #4887 d03e5cf - chore: update dependencies (@Yonom)

• #4815 5325f09 - chore: update dependencies (@okisdev)

• Updated dependencies [43b8ce8, 1e926b6, d6c7571, 4d7a447, ca751f4, 2aca5e0, 908af6d, 0ea628f, 1b46551, 7865f67, 7cf5acc, 7a85307, 438ecd3, e4da8c5, 5a34e8c, 5dbbac4, d3bd0ed, 84e8ddf, 8282269, 03ffe44, 38bf104, 19b2a00, 77c7b26, 026a7ae, 160b0af, c814c9c, 6be3b67, c590a21, 0686f4e, a84cf6d, 9f99c46, c2d2271, e3aba86, 25f9eb2, 84e8ddf, d03e5cf, e02b21b, 7e28a72, ef81c86, 5ade3a5, 1f284ac, 65ba32a, 5325f09]:

  • assistant-stream@0.3.26
  • @assistant-ui/core@0.2.21
  • assistant-cloud@0.1.35
  • safe-content-frame@0.0.23
  • @assistant-ui/tap@0.9.4
  • @assistant-ui/store@0.2.20

0.14.26#

Patch Changes#

• #4627 266657d - Thread list accessibility improvements, focused on keyboard and focus handling: (@AVGVSTVS96)

  • Arrow-key navigation: Up/Down between items, Right to an item's "More" button
    (mirrored in RTL); every item stays a Tab stop.
  • Continuous focus: opening and closing a menu keeps focus on the row, so the
    focus-visible highlight never breaks.
  • New sharedFocusGroup on ThreadListItemMorePrimitive.Root extends this to the
    menu (Right opens, Left/Escape close and restore focus) and forces it non-modal;
    without it, menus are unchanged.

• Updated dependencies [523e0b5, f833bc1]:

  • @assistant-ui/core@0.2.20
  • assistant-stream@0.3.25

0.14.25#

Patch Changes#

• #4562 942931d - fix: disable smooth text streaming under prefers-reduced-motion (@ephraimduncan)

• Updated dependencies [a7b06f7]:

  • safe-content-frame@0.0.22

0.14.24#

Patch Changes#

• #4543 d0987a3 - external-store: add unstable_onBranchChange adapter callback that fires on explicit switchToBranch, emitting the canonical (persisted) head and visible message ids, deduped by head (@AVGVSTVS96)

• #4517 cefcf27 - chore: update dependencies (@okisdev)

• #4545 4550578 - add unstable_useComposerInput headless bridge (value/setText/send/isDisabled/canSend) and unstable_useTriggerPopoverAriaProps for building a custom composer input without ComposerPrimitive.Input (@AVGVSTVS96)

• #4310 0c51b90 - feat: add unstable_ interactables API; restore and deprecate the previous interactables API (@AVGVSTVS96)

  The redesigned interactables API is now available as an additive unstable_* surface for building editable, in-message UI while preserving the existing stable API for compatibility.

  • unstable_useInteractable(name, config) registers an interactable and returns its state plus methods in one hook.
  • Each unstable interactable name gets one stable update_{name} tool. When multiple instances share a name, the tool targets an instance by id.
  • Thread-scoped interactables rendered inside message parts expose version, including the state for that message, whether it is the latest tool-driven version, and restore().
  • Added unstable_interactableTool(...) for defining a creating tool and its in-message render UI together.
  • Added unstable_useInteractableVersions(id, name) for version history UIs.
  • Persistence adapters can now provide load() and be passed directly to unstable_Interactables({ persistence }).

  The previous useAssistantInteractable / useInteractableState / Interactables API remains available unchanged and is marked deprecated. Existing apps do not need to migrate immediately.

  Migration notes for the unstable API:

  ⧉

  - const id = useAssistantInteractable("taskBoard", config);
  - const [state, { setState }] = useInteractableState(id, initialState);
  + const [state, { id, setState }] = unstable_useInteractable("taskBoard", config);
  

  • Use unstable_interactables: unstable_Interactables() when registering the unstable scope.
  • unstable_useInteractableState(id) is intended for secondary readers and returns undefined until the owner registers.
  • The unstable API uses per-name update tools (update_{name}) with an id parameter instead of legacy per-instance tools (update_{name}_{id}).
  • A top-level id field in stateSchema is reserved for instance addressing. Rename domain state fields to itemId, recordId, etc. if the model should edit them.
  • Model selection should be represented as ordinary state in the unstable API; the legacy selected registration prop and setSelected method remain available on the deprecated stable API.

• #4591 f582f09 - feat: honor startRun false across staged-message-capable runtimes (@Yonom)

• #4542 4acd4c0 - add unstable id-keyed thread message rendering APIs for virtualized and custom message lists. unstable_useThreadMessageIds() returns the thread's message ids (stable array identity across content-only updates), and ThreadPrimitive.Unstable_MessageById renders a single message by id with the same component surface as MessageByIndex. A missing or removed id renders null instead of throwing. (@AVGVSTVS96)

• Updated dependencies [ddc40b7, ea52de0, 29c6fdb, d0987a3, cefcf27, 0c51b90, 3a8f685, ec6adf4, 4acd4c0]:

  • @assistant-ui/core@0.2.19
  • assistant-stream@0.3.24
  • assistant-cloud@0.1.34
  • @assistant-ui/store@0.2.19
  • @assistant-ui/tap@0.9.3

0.14.23#

Patch Changes#

• #4426 68dfbaa - chore: mark generateId and fromThreadMessageLike as experimental (@okisdev)

  these two utilities became public in #4414. they now carry an @deprecated JSDoc noting the API is experimental and may change without notice, matching how the other unstable public utilities (e.g. bindExternalStoreMessage) are flagged. the distribution packages (@assistant-ui/react, @assistant-ui/react-native, @assistant-ui/react-ink) re-export them, so the annotation lands in their published types too.

• Updated dependencies [68dfbaa, fe24ad6]:

  • @assistant-ui/core@0.2.18

0.14.22#

Patch Changes#

• #4414 344f737 - feat: export fromThreadMessageLike and generateId from the public API (@okisdev)

  these two utilities were only reachable via @assistant-ui/core/internal, so materializing a ThreadMessageLike into a ThreadMessage, or generating an id for a hand-built message, meant reaching into internals (the first-party ag-ui and a2a runtimes already did). they are now exported from @assistant-ui/core, @assistant-ui/react, @assistant-ui/react-native, and @assistant-ui/react-ink. also removes the now-redundant duplicate listing of both from the unstable INTERNAL namespace (the one in-repo consumer, the with-ffmpeg example, now uses the public export).

• #4419 3cef745 - feat(react): add minCommitMs to SmoothOptions to throttle committed reveal updates (@okisdev)

  useSmooth keeps advancing the typewriter reveal every frame, but with minCommitMs the visible text (and the downstream re-render and markdown re-parse it triggers) is committed at most once per interval. The final frame always commits, so no characters are lost. Defaults to 0, which commits every frame and preserves the previous behavior.

• #4411 d76a922 - feat: add unstable_useLiveCompletionAdapter for async trigger completions (@okisdev)

  bridges an async completion source (a server search, a gateway RPC) into the synchronous Unstable_TriggerAdapter. search returns cached items synchronously and schedules a debounced fetch with stale-request cancellation; when results land the adapter re-creates so the popover re-renders. also adds an isLoading prop on ComposerPrimitive.Unstable_TriggerPopover (surfaced on the popover scope) so async sources can render a loading state.

• Updated dependencies [344f737, a2e21ee]:

  • @assistant-ui/core@0.2.17

0.14.21#

Patch Changes#

• #4403 9f59d69 - fix: prevent compiled context store hooks from skipping subscriptions (@Yonom)

• Updated dependencies [8d3b0e8]:

  • @assistant-ui/tap@0.9.2

0.14.20#

Patch Changes#

• #4393 434bba5 - fix: resolve typecheck regressions (@Yonom)

• #4390 bb38d08 - chore: update dependencies (@Yonom)

• #4392 4cc7eaa - chore: update peer and dependency ranges for @assistant-ui/tap 0.9 (@Yonom)

• Updated dependencies [434bba5, bb38d08, 4cc7eaa, 4cc7eaa]:

  • assistant-stream@0.3.23
  • @assistant-ui/core@0.2.16
  • assistant-cloud@0.1.33
  • @assistant-ui/tap@0.9.1
  • @assistant-ui/store@0.2.18

0.14.19#

Patch Changes#

• #4385 ae59baf - feat: precompile packages with React Compiler (@Yonom)

  • aui-build runs React Compiler over packages that depend on tap and remaps react/compiler-runtime to the tap shim subpath, so compiled hooks and components work both in React components and inside tap resource renders
  • @assistant-ui/tap/react-shim exports useMemoCache (tap inside a resource render, React.__COMPILER_RUNTIME.c otherwise, with a React 18 polyfill); new @assistant-ui/tap/react-shim/compiler-runtime subpath mirrors react/compiler-runtime's c export
  • tap implements useSyncExternalStore and a no-op useDebugValue; useSubscribable now builds on useSyncExternalStore so its store reads stay visible to the compiler
  • AssistantProviderBase opts out via "use no memo" because the runtime receives options through an effect inside a re-rendered child element

• #4378 4583ca7 - feat: approval options vocabulary on tool approvals. ToolCallMessagePart.approval gains request-supplied options (machine-readable kinds allow-once / allow-always / reject-once / reject-always, open to _-prefixed custom kinds), a recorded optionId, and a terminal resolution ("cancelled" | "expired") for non-decision outcomes. respondToApproval additionally accepts { optionId }, resolved in core against the option's kind; custom kinds require an explicit approved. ExternalThread gains an onRespondToToolApproval callback. The kit approval bar renders supplied options with an opt-in confirmation step showing the grants an option would persist. Persistence stays host-owned. (@okisdev)

• #4379 94cc028 - feat: per-tool-call timing and stall detection. ToolCallMessagePart gains a timing field ({ startedAt, completedAt? } in epoch ms), auto-populated by the assistant-stream accumulator at part start and result, and accepted on ThreadMessageLike for external-store hosts. New useToolCallElapsed() hook returns the call's elapsed milliseconds, ticking once per second while running; unstable_useMessageStallDetection({ thresholdMs }) reports mid-run output stalls by watching a message content fingerprint. The kit ToolFallback trigger renders the duration when timing is present. (@okisdev)

• Updated dependencies [c207bcd, ae59baf, 9f13fdb, 4583ca7, 94cc028]:

  • @assistant-ui/core@0.2.15
  • @assistant-ui/tap@0.8.1
  • @assistant-ui/store@0.2.17
  • assistant-stream@0.3.22

0.14.18#

Patch Changes#

• #4352 14aa2ac - feat: unstable_useComposerInputHistory (@okisdev)

  terminal-style input history for the thread composer: ArrowUp on an empty draft recalls previously sent user messages (newest first, derived live from thread state), ArrowDown steps back and finally restores the in-progress draft. spread the returned { onKeyDown } bundle onto ComposerPrimitive.Input. yields to open trigger popovers, IME composition, modifiers, selections, and consumer handlers that already prevented the event; inert on edit composers.

• #4340 ab8e5bc - fix: exclude reasoning parts from copied message text (@serhiizghama)

  getCopyText filtered parts with "text" in part, which also matched reasoning parts (they carry a text field), leaking the model's chain-of-thought into the clipboard. Both copy paths now delegate to the canonical getThreadMessageText, so copy returns only type: "text" content — consistent with the rest of the runtime.

• #4359 59d252f - feat: branch switching for the ExternalThread client (@okisdev)

  ExternalThread accepts an optional branches adapter (ExternalThreadBranchAdapter in @assistant-ui/core, re-exported from @assistant-ui/react): getBranches(messageId) returns ordered sibling branch ids and switchToBranch(branchId) makes a sibling visible by swapping the messages array. messages with more than one sibling get real branchNumber/branchCount, which is what shows the branch picker; capabilities.switchToBranch is set for parity with the legacy external store. without the adapter, behavior is unchanged.

• #4329 2b96cb5 - fix: emit the GroupedParts streaming indicator for empty running messages, so the assistant slot shows a loading affordance immediately after sending instead of staying blank (@okisdev)

• #4329 2b96cb5 - fix: compensate scrollbar gutter in useScrollLock so collapsible animations don't shift centered content horizontally on classic scrollbars (@okisdev)

• #4350 42fd04f - feat: public, tunable useSmooth (@okisdev)

  useSmooth and a new SmoothOptions type are now exported from @assistant-ui/react (previously internal-only with a hard-coded reveal rate). the smooth prop on MessagePartPrimitive.Text and MarkdownTextPrimitive widens to boolean | SmoothOptions, with drainMs (backlog drain target, default 250), maxCharIntervalMs (slowest reveal interval, default 5), and maxCharsPerFrame (per-frame cap, default unlimited). the hook also now preserves the part type for reasoning parts instead of always returning type: "text". react-markdown's @assistant-ui/react peer floor moves to the release that ships SmoothOptions.

• #4325 5a4f20e - chore: update @assistant-ui/tap dependency ranges to ^0.7.0 (@Yonom)

• #4329 2b96cb5 - fix: clear pending viewport bottom-scroll intent on pointer interaction, preventing collapsible expand/collapse from yanking the thread to the bottom (@okisdev)

• Updated dependencies [ab8e5bc, 59d252f, feecac3, 3e58253, 12b016b, 3e58253, 5a4f20e, f10b8ae, 1fb5862]:

  • @assistant-ui/core@0.2.14
  • @assistant-ui/store@0.2.16
  • @assistant-ui/tap@0.7.1

0.14.17#

Patch Changes#

• #4315 60ef0e9 - feat: add runtime support for deleting messages (@Yonom)

• #4318 1b6a0d6 - feat(tap): resources carry all hook arguments; elements are { hook, args } (@Yonom)

  A ResourceElement is now { hook, args } (was { type, props }): the underlying hook plus the full tuple of arguments to call it with. This lets a resource take multiple positional arguments, exactly like a hook, and makes hosting just hook(...args):

  ⧉

  const usePair = (a: number, b: string) => ({ a, b });
  const Pair = resource(usePair);
  const element = Pair(1, "hi"); // { hook: usePair, args: [1, "hi"] }
  

  The single-object case is unchanged ergonomically (Counter({ initialValue: 0 }) still works; its args is just [{ initialValue: 0 }]), so existing resources and call sites are unaffected. resource()'s overloads collapse into one variadic signature, and the fnSymbol / callResourceFn indirection is gone (the element holds the hook directly; renderResourceFiber calls fiber.hook(...args)).

  Breaking (internal/advanced):

  • The second type parameter of Resource / ResourceElement / ContravariantResource now means the argument tuple A extends readonly unknown[] rather than a single payload P. Explicit two-arg annotations must wrap the payload in a tuple (e.g. ResourceElement<R, [Props]>).
  • A resource's identity is now its hook. Reading element.props becomes element.args[0]; reading element.type becomes element.hook. attachTransformScopes is now keyed by (and called with) the hook rather than the factory.
  • useResource(element, deps)'s second arg is unchanged in behavior (renamed argsDeps).

• #4318 1b6a0d6 - refactor: adopt the extracted-hook convention for resources (@Yonom)

  A resource body is a hook, so resources are now authored as a use-prefixed hook
  wrapped with resource():

  ⧉

  const useCounter = () => { ... };
  const Counter = resource(useCounter);
  

  resource() turns a hook into a Resource; useResource(Counter(props)) turns it
  back into a hook call. Extracting the body to a use-prefixed hook lets React's
  stock rules-of-hooks and exhaustive-deps lint resource bodies directly. No
  public API or runtime behavior changes.

• Updated dependencies [60ef0e9, 1b6a0d6, 1b6a0d6, 1b6a0d6, 1b6a0d6]:

  • @assistant-ui/core@0.2.13
  • @assistant-ui/tap@0.6.2
  • @assistant-ui/store@0.2.15

0.14.16#

Patch Changes#

• Updated dependencies:
  • @assistant-ui/core@0.2.12
  • @assistant-ui/tap@0.6.1

0.14.15#

Patch Changes#

• #4260 19c5b5f - fix: make defineToolkit usable for plain runtime toolkits (@Yonom)

• #4246 dbdfb15 - feat: message queuing for external-store, langgraph, and local runtimes (@okisdev)

  the composer can now stay usable while a run is in progress: a message sent during a run is held in composer.queue (rendered via ComposerPrimitive.Queue / QueueItemPrimitive.*) and processed once the run settles. external-store adapters opt in by providing a queue adapter (typically built with the new createMessageQueue helper); useLangGraphRuntime and useLocalRuntime opt in via unstable_enableMessageQueue. ExternalThreadQueueAdapter now lives in @assistant-ui/core (still re-exported from @assistant-ui/react).

• #4249 ca191dc - feat: add externalTool for render-only generative toolkit entries (@Yonom)

• #4306 15878d8 - chore: update dependencies (@Yonom)

• #4280 e7f1aa0 - fix(mcp-apps): send the 2026-01-26 dialect on host→app messages so widgets built with @modelcontextprotocol/ext-apps initialize and receive tool results (@okisdev)

  the bridge already normalized inbound ui/* method names, but every outbound message (the ui/initialize result and the tool input/result/host context notifications) stayed in the pre-spec dialect. spec widgets zod-validate the initialize result and require hostInfo + hostCapabilities, so they failed init; tool results were posted as notifications/tools/call/result, a method the official SDK never listens for, so a patched widget still rendered empty. the bridge now additively dual-sends both dialects (the initialize result carries host/capabilities and hostInfo/hostCapabilities, echoes the app's requested protocolVersion, and each notification posts its ui/notifications/* counterpart with the spec param shapes). unknown methods and fields are ignored by either SDK, so legacy widgets are unaffected.

• #4256 44ff4bf - feat: rename hitlTool to humanTool while keeping deprecated compatibility aliases (@Yonom)

• #4298 72494e7 - refactor: extract a shared sandbox host (SafeContentFrame lifecycle, the single cross-origin guarded message listener, auto-resize) and reuse it for the MCP app frame, with no behavior change (@okisdev)

• Updated dependencies [2a84174, a0a0769, 19c5b5f, dbdfb15, ca191dc, 15878d8, 44ff4bf, 01cf957, 01cf957, 26a365b]:

  • @assistant-ui/core@0.2.11
  • assistant-stream@0.3.21
  • assistant-cloud@0.1.32
  • safe-content-frame@0.0.21
  • @assistant-ui/store@0.2.14
  • @assistant-ui/tap@0.6.0

0.14.14#

Patch Changes#

• #4212 5fe118d - feat: add MCP server support to generative toolkits (@Yonom)

• #4213 dcd5897 - feat: add provider-executed tool support to generative toolkits (@Yonom)

• #4127 606c9d4 - feat(assistant-transport): honour Aui-Replay-Content-Length to split sync-server replay from live bytes (@Yonom)

  useAssistantTransportRuntime now reads the Aui-Replay-Content-Length response header on resume and gates the body at that byte boundary. The replay prefix is decoded while isLoading: true has rendered through React, then the reader pauses until isLoading: false has rendered before releasing live bytes. Tool calls in the replayed portion are recorded as historical and skip streamCall / execute, while tool calls that begin after the replay boundary fire normally. Responses without the header behave as today.

• #4208 0558db2 - feat: add updateCustom to thread list runtimes, adapters, and clients (@okisdev)

• #4214 69540af - feat: add renderText helpers for tool call status text (@Yonom)

• #4199 d9b3119 - feat: a defineToolkit entry may now be an already-formed ToolDefinition (carrying its own type), not only an inline definition whose type the compiler infers. This is what lets a factory like new JSONGenerativeUI({ library }).present() be used directly as a tool. (@Yonom)

  Renames the authoring types to match defineToolkit: ToolkitDeclaration → ToolkitDefinition, and adds ToolkitDefinitionEntry (the union of an inline tool definition and a pre-formed ToolDefinition). The per-tool inline type is now an internal ToolkitDefinitionInput and is no longer exported.

• #4236 ae54c55 - feat: add stubTool() and experimental useAuiToolOverrides() for locally executed generative toolkit tools (@Yonom)

• #4235 7640b31 - Deprecate component tool registration APIs in favor of toolkit registrations. (@Yonom)

• Updated dependencies [cba2b42, 4145caa, 58f80e0, 78ff336, 5fe118d, dcd5897, 0558db2, 69540af, d9b3119, ae54c55, 7640b31]:

  • assistant-stream@0.3.20
  • @assistant-ui/core@0.2.10
  • assistant-cloud@0.1.31

0.14.13#

Patch Changes#

• #4176 27ae936 - feat: add the ToolkitDeclaration / ToolkitDeclarationDefinition types for authoring a toolkit permissively (a backend tool may declare description/parameters/execute); the canonical Toolkit keeps those fields erased. Author with defineToolkit() from @assistant-ui/react, which the "use generative" compiler strips per build. (@Yonom)

• #4176 27ae936 - feat: move the defineToolkit and hitl use-generative markers from @assistant-ui/next into @assistant-ui/core/react, so they ship once from every distribution (@assistant-ui/react, @assistant-ui/react-native, @assistant-ui/react-ink) and stay portable across build targets. Import them from @assistant-ui/react instead of @assistant-ui/next; they remain no-op markers stripped at build time by a "use generative" compiler. (@Yonom)

• Updated dependencies [27ae936, 27ae936]:

  • assistant-stream@0.3.19
  • @assistant-ui/core@0.2.9

0.14.12#

Patch Changes#

• #4172 1315789 - feat: add the ToolkitDeclaration / ToolkitDeclarationDefinition types for authoring a toolkit permissively (a backend tool may declare description/parameters/execute); the canonical Toolkit keeps those fields erased. Author with defineToolkit() from @assistant-ui/next, which the "use generative" compiler strips per build. (@Yonom)

• #4151 299d448 - chore: drop stale biome-ignore pragmas now that the repo lints with oxlint (@okisdev)

• #4136 4429aa3 - centralize thread-level shared options forwarding across runtime wrapper hooks. follow-up to #4135. (@okisdev)

  new public exports from @assistant-ui/core (re-exported from @assistant-ui/react):

  • ExternalStoreSharedOptions, a typed Pick over ExternalStoreAdapter covering the four thread-level optional fields every wrapper forwards: isDisabled, isSendDisabled, unstable_capabilities, suggestions.
  • pickExternalStoreSharedOptions(options), plucks those four fields from a wider options object. the body uses satisfies Required<...> so adding a key to the type without copying it in the function is a compile error rather than a silent missing-field bug.
  • useExternalStoreSharedOptions(options) (from @assistant-ui/core/react), a memoized variant for wrappers that wrap their store in useMemo. lets the wrapper list a single stable shared reference as a dep instead of enumerating the four fields. same satisfies guard internally so the destructure stays in sync with the type.

  internal: every runtime wrapper hook (useChatRuntime, useAISDKRuntime, useLangGraphRuntime, useA2ARuntime, useAgUiRuntime, useAdkRuntime, useStreamRuntime, useOpenCodeRuntime) now uses these helpers instead of inlining the conditional spreads added in #4135. each wrapper sheds 20 to 40 lines of duplicated declarations and conditional spreads; future additions to the shared option set propagate through a single edit in pickExternalStoreSharedOptions instead of touching every wrapper. no user-facing behavior change.

• #4141 0b99959 - fix(react): stop subtree mutations from snapping a scrolled-up viewport back to bottom; loosen at-bottom threshold for high-DPR displays (@vaniyokk)

  useThreadViewportAutoScroll had two related bugs surfaced on Chrome macOS at devicePixelRatio: 2:

  1. subtree mutations snapped the viewport back to bottom after the user scrolled away. scrollingToBottomBehaviorRef was planted on thread.runStart / useOnScrollToBottom / initialize / thread switch and only cleared in handleScroll once newIsAtBottom became true. while the ref stayed set, every non-style subtree mutation (a Radix data-state flip, a markdown re-render, an image lazy-load, an attribute toggle on a child) re-entered useOnResizeContent's callback and called scrollToBottom(scrollBehavior), locking the viewport to the bottom until reload.
  2. isAtBottom never registered as true on high-DPR displays. Math.abs(scrollHeight - scrollTop - clientHeight) < 1 is strict-less-than, and Chrome macOS at devicePixelRatio: 2 clips scrollTop one pixel short of scrollHeight - clientHeight (Math.abs(1) < 1 === false), so the store never updated and ScrollToBottom never moved into its disabled state.

  the fix combines two layers. handleScroll now tracks lastScrollHeight alongside lastScrollTop and releases the auto-stick intent when the user scrolls up with content size unchanged, ruling out content-driven scrollTop shifts. the resize callback also bails when neither scrollHeight nor clientHeight has changed since the last fire, so mutations that don't move layout never re-enter the snap path. at-bottom auto-follow during streaming is preserved (verified by appending a synthetic 600px child while scrolled to bottom; viewport follows to new bottom). the threshold becomes <= 1 to absorb the 1px sub-pixel clip.

  closes #4140.

• #4160 e76611f - feat: add indicator support to MessagePrimitive.GroupedParts. (@Yonom)

  Restores loading-state handling that was dropped from the grouped renderer. GroupedParts now emits a synthetic { part: { type: "indicator" } } render call you handle with case "indicator" in your switch (part.type) — render a "thinking…" dot or any loading affordance.

  • The indicator is only ever emitted while the message is running, so its presence alone means "render loading UI here" — there's no status to branch on.
  • New indicator prop restricts which running states qualify: "never", "empty" (no parts yet), "no-text" (default — last part isn't text/reasoning, e.g. the model ended on a tool call), or "always" (any running state).

• #4162 eef724e - fix: drop phantom sibling messages when an external store swaps an optimistic message id mid-run (#4037). (@Yonom)

  Messages can now be flagged metadata.isOptimistic. Optimistic messages are treated as ephemeral: they only ever live on the current head branch (the repository evicts off-branch optimistic messages whenever the head moves) and they are never written to persisted state (export() omits them). The AI SDK v6 adapter flags the streaming assistant message as optimistic, so when its client-generated id is replaced by a server-provided one mid-run, the stale placeholder no longer lingers as a phantom branch (e.g. BranchPicker showing 2/2 on a turn the user never branched). Unlike the reverted blanket id-diff (#4040), only explicitly-optimistic messages are affected, so legitimate onEdit / onReload / switchToBranch branches are preserved.

• #4175 2dec3ae - chore: update dependencies (@Yonom)

• #4148 2d9595e - revert: roll back #4040 (drop phantom siblings on external-store id swap). the _lastSyncedMessageIds diff was deleting legitimate sibling branches created by onEdit / onReload / switchToBranch, causing BranchPicker to disappear on edits and reloads (#4131). this revert restores the additive sync behavior; the AI SDK v6 mid-stream id swap (#4037) regresses and will be addressed in the AI SDK adapter instead. (@okisdev)

• #4167 fcb6baf - feat: add a display presentation hint to tools and a "standalone-tool-call" key to groupPartByType. (@Yonom)

  Tool UIs fall into three buckets: prompting the user (human-in-the-loop), informing the user (generative UI), and traces of what the model is doing (routine frontend/backend tool calls). The first two should be surfaced on their own; the last belongs folded into the chain-of-thought trace. The new display field on a tool lets you place a tool in the right bucket without overloading type:

  ⧉

  const toolkit = {
    ask_user: { type: "human", render: AskUI }, // standalone (forced — can't opt out)
    search_web: { type: "frontend", render: SearchUI }, // inline trace (default)
    checkout: {
      type: "frontend",
      render: CheckoutUI,
      display: "standalone", // opt in
    },
  } satisfies Toolkit;
  

  • display?: "standalone" | "inline" is a client-only presentation hint (it never reaches the model). Defaults to "inline".
  • human tools are always "standalone" and cannot opt out (the type only allows "standalone"). MCP-app tool calls and the built-in generative-UI tool are standalone too. Every other tool defaults to inline and opts in explicitly.
  • groupPartByType gains a synthetic "standalone-tool-call" key that matches all of the above. MessagePrimitive.GroupedParts passes the live tool-UI registry to the groupBy function as a second context argument ({ toolUIs }), and the helper reads it to resolve the registry-driven cases; MCP-app calls are detected from the part alone.
  • The "mcp-app" key on groupPartByType is deprecated in favor of "standalone-tool-call" (a superset). It still works for back-compat.

  The shadcn thread.tsx template is updated to use "standalone-tool-call": [] in place of "mcp-app": [].

• Updated dependencies [1315789, 299d448, 4429aa3, e76611f, 76f7d16, eef724e, 2dec3ae, fcb6baf, c4d3eea, 331f2f7]:

  • assistant-stream@0.3.18
  • @assistant-ui/core@0.2.8
  • @assistant-ui/store@0.2.13
  • @assistant-ui/tap@0.5.14
  • assistant-cloud@0.1.30

0.14.11#

Patch Changes#

• #4125 e639a11 - chore: drop tracker-behaviour explainer comments left behind in satellite runtimes (@Yonom)

0.14.10#

Patch Changes#

• #4118 a6e0653 - feat(core): build a client-side tool-invocations pipeline directly into useExternalStoreRuntime. Tool-call parts in messages now fire streamCall / execute automatically for any external-store runtime that opts in. Opt in per-adapter via unstable_enableToolInvocations: true (off by default — most external-store runtimes either run tools server-side or already wire their own client-side dispatch path; double-firing is the risk). The _store.isLoading flag signals when initial history is loaded: snapshots observed while isLoading === true are treated as historical (no fire), matching the contract that callers like importExternalState already rely on. Six in-tree runtimes (useAssistantTransportRuntime, useAISDKRuntime, useLangGraphRuntime, useStreamRuntime, useAgUiRuntime, useAdkRuntime) are migrated to the embedded tracker; the standalone useToolInvocations React hook is removed. Adds ExternalStoreAdapter.setToolStatuses so adapters can mirror the tracker's per-tool-call status into local React state for converter metadata. Auto-aborts in-flight tool calls on new turns (append() with startRun, startRun()) so a tool that finishes after the user moves on can no longer feed a stale result into the next turn. (@Yonom)

• Updated dependencies [7395092, a6e0653, cabfc71]:

  • @assistant-ui/core@0.2.7
  • @assistant-ui/tap@0.5.13

0.14.9#

Patch Changes#

• #4120 372d4f0 - feat: simplify MessagePrimitive.GroupedParts API and add groupPartByType helper. (@Yonom)

  • New groupPartByType({ ... }) helper builds a groupBy from a part.type → group-key path lookup. The map keys are typed against PartState["type"] (autocomplete + typo rejection), missing keys leave the part ungrouped, and the returned function carries an internal memo fingerprint so the tree survives unrelated re-renders even when reconstructed inline.
  • Special map key "mcp-app" matches tool-call parts that point at an assistant-ui MCP app resource (ui://...). It takes precedence over the "tool-call" entry for those parts, so MCP apps can be routed separately (e.g. rendered outside a chain-of-thought wrapper).
  • groupBy signature simplified from (part, index, parts) => string | string[] | null | undefined to (part) => readonly \group-${string}`[] | null. The 2nd/3rd args were unused in practice. Arrays are required (no bare-string shorthand); nullis accepted as an alias for[]` to soften the migration.
  • Internal memoization now uses the helper's memo fingerprint when present, otherwise rebuilds the tree per render (O(n), cheap). The previous "pass a stable reference" advice is dropped — inline groupBy is fine.
  • Docs and examples updated to lead with groupPartByType. The getMcpAppFromToolPart branch in packages/ui switches to "mcp-app": [] via the helper.

• #4107 32ae846 - feat: surface AI SDK v6 tool approvals as a first-class respondToApproval prop on tool components. tool-call parts in the approval-requested state now carry part.approval = { id, isAutomatic? }; tool components call respondToApproval({ approved, reason? }) to ack the gate without threading chatHelpers through application context. also fixes a transient requires-action flicker for the approval-responded state and tightens the external-message converter so interrupt vs pending tool calls are distinguished by an actual interrupt/approval field rather than by result === undefined. (@okisdev)

• Updated dependencies [372d4f0, d4f1db4, 32ae846]:

  • @assistant-ui/core@0.2.6
  • assistant-stream@0.3.17

0.14.8#

Patch Changes#

• #4093 b02b701 - feat(react): unstable_insertNewlineOnTouchEnter on ComposerPrimitive.Input (@okisdev)

  When set, plain Enter on a touch-primary device — detected via the (pointer: coarse) and (not (any-pointer: fine)) media query — inserts a newline instead of submitting. Messages then dispatch only via the explicit Send button, matching the chat-input convention used by WhatsApp, Slack, Discord, iMessage, ChatGPT, and Claude.ai, and avoiding the consumer-side caret-aware re-insertion dance the previous workaround required.

  Orthogonal to submitMode: only takes effect when submitMode resolves to "enter" (the default). A tablet paired with a hardware keyboard can still submit via submitMode="ctrlEnter" (Cmd/Ctrl+Enter), and submitMode="none" is unchanged.

  ⧉

  <ComposerPrimitive.Input
    placeholder="Ask anything..."
    unstable_insertNewlineOnTouchEnter
  />
  

  Stays unstable_ until we have enough field signal to flip the behavior on by default.

• #3967 0a0c306 - feat(core, react): add MessagePrimitive.GenerativeUI primitive (@samdickson22)

  A new first-class primitive for rendering agent-described React UI from a JSON
  spec, with a consumer-provided component allowlist as the security boundary.

  The agent emits a new generative-ui message part containing a tree of
  components by name; MessagePrimitive.GenerativeUI walks the spec and resolves
  each name against the registry you pass in. Unknown names throw a typed
  GenerativeUIRenderError (or invoke the optional Fallback). Composes with
  MessagePrimitive.Parts via the new components.generativeUI option, and
  supports streaming partial specs.

  ⧉

  <MessagePrimitive.Parts
    components={{
      generativeUI: { components: { Card, Button } },
    }}
  />
  

• #4085 01244a5 - chore: update dependencies (@Yonom)

• #4099 f2ec01c - feat(core, react): opt-out of auto-unarchive when switching threads (@adityamohta)

  switchToThread (and ThreadListItemRuntime.switchTo) now accept an optional { unarchive?: boolean } argument. The default remains true, preserving the existing behavior of auto-unarchiving an archived thread when it becomes the main thread. Pass unarchive: false to keep the thread archived after switching — useful when the UI lets users preview an archived conversation without restoring it.

  ⧉

  // existing behavior — archived thread becomes regular
  await threadList.switchToThread(threadId);
  
  // new — keep status as archived
  await threadList.switchToThread(threadId, { unarchive: false });
  
  // same option on the item runtime
  await threadListItem.switchTo({ unarchive: false });
  

• Updated dependencies [13a12c4, 0a0c306, 6a0ecb2, e4634a5, 325de4c, 01244a5, f2ec01c, 1e21076]:

  • assistant-stream@0.3.16
  • @assistant-ui/core@0.2.5
  • assistant-cloud@0.1.29
  • safe-content-frame@0.0.20
  • @assistant-ui/store@0.2.12
  • @assistant-ui/tap@0.5.12

0.14.7#

Patch Changes#

• #4073 44ac459 - fix(react|useSmooth): render-phase resync of displayed text on part change (@Yonom)

  Drop one frame of stale text after a thread switch by resyncing
  displayedText in render when the part instance flips or text
  breaks its streaming-append continuity, instead of waiting for
  the post-commit effect.

• Updated dependencies [221d320]:

  • @assistant-ui/core@0.2.4

0.14.6#

Patch Changes#

• #4023 94548fa - docs: add React JSDoc and deprecation notices for primitive and tool APIs (@AVGVSTVS96)

• #3513 8b6fc88 - fix: guard navigator.clipboard availability and swallow write rejections in ActionBarPrimitive.Copy. Previously, copy clicks in SSR, non-HTTPS contexts, or older browsers without the Clipboard API threw a ReferenceError, and permission-denied rejections surfaced as unhandled promise rejections. The web copyToClipboard implementation in @assistant-ui/react now early-rejects when the API is unavailable, and useActionBarCopy in @assistant-ui/core silently absorbs the rejection so the rest of the UI is unaffected. (@JustAnOkapi)

• #4040 b481ec5 - fix: useExternalStoreRuntime no longer leaves phantom assistant siblings when the external store swaps a message id between syncs (e.g. AI SDK v6 useChat replacing a client-generated id with a server-provided id mid-stream, surfacing as BranchPicker showing 2/2 on a turn the user never branched). The messages-array sync path now diffs against the previous sync and removes ids that disappeared, matching the messageRepository path's snapshot semantics. Closes #4037. (@okisdev)

• #4063 8f0dbb8 - fix thread initialization timing race which caused scrollToBottomOnInitialize to fail in useLocalRuntime (@AVGVSTVS96)

• #3958 7a8bf26 - refactor: hoist MessagePartPrimitiveInProgress to @assistant-ui/core/react so @assistant-ui/react, @assistant-ui/react-ink, and other distributions can share the same implementation. @assistant-ui/react's MessagePartPrimitive.InProgress is unchanged for callers; it now re-exports from core. (@ShobhitPatra)

• #4050 693922b - fix(x-buildutils): include local types/ in typeRoots so x-buildutils itself can resolve its ambient browser-process types (@Yonom)

  feat(react): re-export Unstable_DirectiveFormatter, Unstable_DirectiveSegment, Unstable_TriggerItem, and unstable_defaultDirectiveFormatter from @assistant-ui/core so downstream packages don't need to depend on @assistant-ui/core directly

• Updated dependencies [845c7c1, db721df, 94548fa, 94548fa, 94548fa, 8b6fc88, 179895f, 7a8bf26, 3b2bbce]:

  • assistant-cloud@0.1.28
  • @assistant-ui/store@0.2.11
  • assistant-stream@0.3.15
  • @assistant-ui/core@0.2.3

0.14.5#

Patch Changes#

• Accept the MCP-UI 2026-01-26 method names in the MCP App bridge (e.g. ui/notifications/size-changed, ui/request-display-mode, ui/open-link, ui/message). Widgets built with the current xmcp host-bridge emit these names; previously the host silently ignored them, leaving features like auto-resize broken (iframe never received a height change from onSizeChange).

0.14.4#

Patch Changes#

• #4033 552ffb0 - feat(react): export getMcpAppFromToolPart so hosts can detect MCP-app tool parts (@Yonom)

• Updated dependencies []:

  • safe-content-frame@0.0.19

0.14.3#

Patch Changes#

• #4031 30f0357 - feat(react): clamp MCP app auto-resize height to a configurable max (default 800px) (@Yonom)

0.14.2#

Patch Changes#

• #4024 19d4d94 - feat: add native MCP Apps renderer — McpAppRenderer composes into Tools to render MCP UI resources inline in chat over a JSON-RPC postMessage bridge on SafeContentFrame. Adds an mcp field to ToolCallMessagePart and forwards callProviderMetadata.mcp.app through the AI SDK message converter. (@Yonom)

• #4022 4c3eaa1 - fix(composer): apply WAI-ARIA combobox attributes to the textarea while a trigger popover is open (@okisdev)

  Unstable_TriggerPopover rendered the listbox half of the WAI-ARIA editable combobox pattern, but the focused element (the textarea) lacked the corresponding combobox attributes. screen readers had no way to announce that an autocomplete was open or which item was highlighted.

  ComposerPrimitive.Input now reads the active popover descriptor from TriggerPopoverRoot and applies aria-controls, aria-expanded, aria-haspopup="listbox", and aria-activedescendant to the textarea while a popover is open. attributes are removed when the popover closes. consumers using ComposerPrimitive.Input outside a TriggerPopoverRoot are unaffected.

• #4020 03694bd - fix(composer): select highlighted item on Tab in trigger popover (@serhiizghama)

  ComposerPrimitive.Unstable_TriggerPopover only accepted the highlighted entry on Enter. Tab fell through to the underlying textarea, moving focus out of the composer or inserting a tab character. This diverged from the autocomplete convention used in CLIs, IDEs, command palettes, GitHub, Slack, Discord, and Notion, where Tab accepts the highlighted suggestion.

  Tab now mirrors Enter and selects the highlighted item or category. Shift+Tab still passes through so native focus traversal keeps working.

• Updated dependencies [19d4d94]:

  • @assistant-ui/core@0.2.2

0.14.1#

Patch Changes#

• #3984 35d0146 - feat(composer): expose canSend state and isSendDisabled adapter input (@okisdev)

  ComposerState.canSend (read-only) is now derivable via useAuiState((s) => s.composer.canSend) and <AuiIf condition={(s) => s.composer.canSend}/>. it reflects whether the composer is in a state where send is permitted; cross-thread gating (isRunning, capabilities.queue) continues to be layered on top by useComposerSend.

  ExternalStoreAdapter.isSendDisabled is a new optional input alongside isDisabled. when true, the thread composer's input remains usable but send() becomes a no-op and canSend is false. use this to gate sending on external React state (e.g. while tool config is loading) without disabling the input itself. edit composers (saving in-progress message edits) intentionally ignore this flag, since it is a thread-scoped gate.

  BaseComposerRuntimeCore.send() now early-returns when !canSend, so the Cmd/Ctrl+Shift+Enter steer hotkey, form-requestSubmit(), and direct aui.composer().send() calls are all gated by the same flag. the same gating is wired through the tap-based ExternalThread client via a new isSendDisabled prop on ExternalThreadProps.

• #4008 fa4510a - feat: support multi-modal tool results via toModelOutput (@okisdev)

  frontend tools can now project their execution output into multi-modal model content (text + image / pdf / arbitrary file parts), aligning with the AI SDK v6 toModelOutput callback. previously, tool results were always serialized as a single JSON value, so a "read pdf" style tool had no way to send the PDF back to a multi-modal model.

  • assistant-stream exports a new ToolModelContentPart type ({ type: "text", text } | { type: "file", data, mediaType, filename? }) and a ToolModelOutputFunction<TArgs, TResult> callback type. Tool.toModelOutput is wired through unstable_runPendingTools and ToolExecutionStream, attaching the resulting modelContent to the tool-call part on the assistant message.
  • @assistant-ui/core re-exports ToolModelContentPart and adds an optional modelContent?: readonly ToolModelContentPart[] field on ToolCallMessagePart. existing tools and renderers are unchanged.
  • @assistant-ui/react-ai-sdk's frontendTools(...) helper now also registers a toModelOutput on each forwarded tool. it transparently unwraps an envelope that useAISDKRuntime writes when a frontend-executed tool produced modelContent, turning it into AI SDK's { type: "content", value: [...] } output. plain (non-envelope) outputs fall back to the existing { type: "text" | "json", value } shape, so behavior for tools without toModelOutput is unchanged.

  route handlers that adopt toModelOutput also need to pass tools to convertToModelMessages (this is the AI SDK's documented pattern):

  ⧉

  const aiSDKTools = { ...frontendTools(tools ?? {}) };
  streamText({
    messages: await convertToModelMessages(messages, { tools: aiSDKTools }),
    tools: aiSDKTools,
  });
  

  templates and existing examples are unchanged. they keep the simpler convertToModelMessages(messages) form because none of the tools they ship with use toModelOutput. the new tools guide page documents how to opt in.

  reserved key. when a frontend tool defines toModelOutput, its result is persisted in the AI SDK chat as { __aui_modelContent: ToolModelContentPart[], value: <your result> }. tools must not return objects whose top-level key is literally __aui_modelContent, or convertMessage will misread the result. the prefix is namespaced for this reason.

  read/write compatibility for persisted threads. the envelope is recognized by @assistant-ui/react-ai-sdk from this version onward. if you persist UI messages and read them from multiple environments, upgrade every reader before any writer starts producing toModelOutput; otherwise older readers will treat the envelope object as the result and break the affected tool render functions.

• #3634 9c3d24d - Support AI SDK source-document parts by preserving them as assistant-ui (@sicko7947)
  document source message parts across conversion and cloud serialization,
  including the legacy React cloud encoder.

• Updated dependencies [9ecda1d, 35d0146, fa4510a, c9dd16c, dea8bc7, 9c3d24d]:

  • assistant-stream@0.3.14
  • @assistant-ui/core@0.2.1

0.14.0#

Minor Changes#

• #3970 040d469 - chore: drop APIs deprecated in v0.11/v0.12 (@Yonom)

  See the v0.14 migration guide for the full removal list and replacements.

  • useAssistantApi / useAssistantState / useAssistantEvent / AssistantIf removed (use useAui / useAuiState / useAuiEvent / AuiIf).
  • getExternalStoreMessage (singular) removed (use getExternalStoreMessages).
  • MessageState.submittedFeedback removed (use message.metadata.submittedFeedback).
  • ThreadRuntime.startRun(parentId) positional overload removed (pass { parentId }).
  • ThreadRuntime.unstable_loadExternalState removed (use importExternalState).
  • ThreadRuntime.unstable_resumeRun removed (use resumeRun).
  • ThreadRuntime.getModelConfig removed (use getModelContext).
  • AssistantRuntime.threadList / switchToNewThread / switchToThread / registerModelConfigProvider / reset removed (use threads / threads.switchToNewThread / threads.switchToThread / registerModelContextProvider / thread.reset).
  • ChatModelRunOptions.config removed (use context).
  • useLocalThreadRuntime alias removed (use useLocalRuntime).
  • unstable_useRemoteThreadListRuntime / unstable_useCloudThreadListAdapter / unstable_RemoteThreadListAdapter / unstable_InMemoryThreadListAdapter aliases removed (drop the unstable_ prefix).
  • react-langgraph onSwitchToThread removed (use load).
  • toAISDKTools / getEnabledTools removed (use toToolsJSONSchema from assistant-stream).

Patch Changes#

• Updated dependencies [040d469]:
  • @assistant-ui/core@0.2.0

0.13.0#

Minor Changes#

• #3908 d864d07 - fix: robust top-turn anchoring with viewport-owned reserve (@AVGVSTVS96)

  Migration:

  • Remove ThreadPrimitive.ViewportSlack from your tree. It has been removed from the public API because top-anchor target registration is now handled automatically by MessagePrimitive.Root when turnAnchor="top".
  • If you customized fillClampThreshold / fillClampOffset on ThreadPrimitive.ViewportSlack or MessagePrimitive.Root, replace them with topAnchorMessageClamp on ThreadPrimitive.Viewport:
  ⧉

  // Before, either:
  <MessagePrimitive.Root fillClampThreshold="10em" fillClampOffset="6em" />
  
  // or:
  <ThreadPrimitive.ViewportSlack fillClampThreshold="10em" fillClampOffset="6em">
    ...
  </ThreadPrimitive.ViewportSlack>
  
  // After
  <ThreadPrimitive.Viewport
    turnAnchor="top"
    topAnchorMessageClamp={{ tallerThan: "10em", visibleHeight: "6em" }}
    ...
  </ThreadPrimitive.Viewport>
  

Patch Changes#

• #3924 801b9a6 - fix(react): recover ComposerPrimitive.Input from dropped compositionend (@nitnizzie)

  reset compositionRef when the next change event reports isComposing: false so a dropped compositionend (chromium dead-key layouts, mid-composition focus loss) can no longer freeze the input. additionally call setText during composition so React 19's stricter controlled-input reconciliation does not reset the textarea mid-IME. fixes #3923.

• #3953 7098bab - Add cursor-based pagination to the thread list. RemoteThreadListAdapter.list() accepts an optional { after } cursor and may return nextCursor on the response. The runtime exposes loadMore(), hasMore, and isLoadingMore through both the legacy ThreadListRuntime API and the tap-only aui.threads() path; ThreadListRuntimeCore.loadMore?(), hasMore?, and isLoadingMore? are optional, so non-paginating cores (local, external-store, single-thread, in-memory) remain conformant. (@okisdev)

  @assistant-ui/react ships a matching ThreadListPrimitive.LoadMore button built on createActionButton, plus a useThreadListLoadMore primitive hook. Consumers wanting an IntersectionObserver sentinel can read s.threads.hasMore / isLoadingMore from useAuiState and call aui.threads().loadMore() directly.

  In-flight loadMore() calls dedup via a single promise. The existing _loadGeneration counter drops stale append callbacks when a reload() interleaves a loadMore(). The loadMore reducer captures the active adapter so a mid-flight adapter swap cannot leak a stale page. Empty-string nextCursor is normalised to undefined. reload() pre-clears the cursor so consumers reading hasMore directly during a reload do not observe a stale value.

  Adapter rejections are surfaced via console.error in both the initial-load and loadMore paths, matching the pattern in RemoteThreadListHookInstanceManager and useToolInvocations.

• #3954 aa6e071 - fix: keep active top-anchored messages visible to layout (@AVGVSTVS96)

• #3962 b090acb - chore: update dependencies (@Yonom)

• #3952 df7eb3e - perf: cut per-message overhead in long threads (@okisdev)

  Two MessagePrimitive.Root changes remove work that scaled with message count:

  • Defer the parseCssLength call inside the top-anchor target ref to the next animation frame. The synchronous getComputedStyle read previously forced a full-tree layout during the bulk-mount of a long thread (a 335 ms forced reflow at 100 messages in our trace). Deferring past first paint lets the browser do the layout naturally.
  • Split the root into a default and a top-anchor path. Threads using the default turnAnchor="bottom" no longer subscribe to the top-anchor useAuiState selectors per message.

  The only observable change is that top-anchor target registration is now async by one frame.

  Note: @assistant-ui/ui (private, copy-into-project) gains a content-visibility: auto default on message wrappers in the same PR. On a cold load with pre-existing history taller than the viewport, the placeholder-based scrollHeight can transiently disagree with the at-bottom check until off-screen messages are measured. useOnResizeContent resyncs within a frame, and the auto-scroll path uses an explicit "scrolling" flag rather than trusting isAtBottom alone, so run-start scrolling is unaffected.

• #3948 f4a693e - fix(core): restore adapter context flow through RemoteThreadListAdapter.unstable_Provider (@okisdev)

  PR #3891 hoisted the runtime binder out of RemoteThreadListAdapter.unstable_Provider so that user-supplied loading / Suspense wrappers no longer strand the runtime binding. as a side effect, any RuntimeAdapterProvider mounted inside unstable_Provider (history, attachments — what useCloudThreadListAdapter and LocalStorageThreadListAdapter both do) ended up below the binder in the render tree. useRuntimeAdapters() reads context from above, so the runtime hook saw null and useExternalHistory early-returned.

  for useChatRuntime({ cloud }) setups this silently disabled message persistence (POST /v1/threads/:id/messages), thread history loading, run telemetry (POST /v1/runs), and forced cloud attachments to fall back to vercelAttachmentAdapter's base64 inlining. the same regression hits useA2ARuntime, useAgUiRuntime, and useLocalRuntime whenever they are wrapped by useRemoteThreadListRuntime with a similar adapter.

  restore the pre-#3891 layering: the binder once again renders inside unstable_Provider, so the runtime hook reads any context the Provider injects. the ProviderRenderDetector warning introduced by #3891 is kept and now fires whenever Provider gates children behind suspense, loading state, or useEffect (the original #3678 case), pointing the user at the synchronous-children rule. no API surface changes; first-party adapters keep working unchanged.

• Updated dependencies [7098bab, b090acb, 5fdf17e]:

  • @assistant-ui/core@0.1.18
  • assistant-stream@0.3.13
  • @assistant-ui/store@0.2.10
  • @assistant-ui/tap@0.5.11

0.12.28#

Patch Changes#

• #3853 6a919c1 - feat: add <MessagePrimitive.GroupedParts> for hierarchical adjacent grouping of message parts (@Yonom)

  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.

• Updated dependencies [0bbf5dd, 98f165c, 62ec5bd, 6a919c1]:

  • @assistant-ui/core@0.1.17

0.12.27#

Patch Changes#

• #3909 005f83f - chore: update dependencies (@Yonom)

• Updated dependencies [549037a, 005f83f, 976aec5, 25b97d5, 2008fc9, 88fcd35]:

  • @assistant-ui/core@0.1.16
  • @assistant-ui/store@0.2.9
  • @assistant-ui/tap@0.5.10

0.12.26#

Patch Changes#

• #3876 ce865bc - chore: update dependencies (@Yonom)

• #3873 c56f98f - feat(core): add reload() method on ThreadListRuntime and aui.threads() that re-invokes the remote adapter's list() and refreshes the thread list. Use this after asynchronous auth (e.g. OIDC, better-auth) completes to recover from an initial load that ran before the authenticated user was available. A generation counter ensures a mid-flight response from a superseded load cannot overwrite a newer reload's state. (@okisdev)

• #3829 9aa5410 - fix: add render prop support to dropdown menu primitives (@AVGVSTVS96)

• #3583 a1f84ae - fix: process dropped attachments in parallel (@samdickson22)

  Align drag-and-drop attachment handling with paste so multiple files appear together instead of appearing one by one.

• #3870 b4fde97 - fix(composer): sync mouse hover with keyboard highlight in TriggerPopover. Items and categories now update highlightedIndex on mouse move, keeping data-highlighted, aria-selected, and aria-activedescendant consistent with the hovered element. A new highlightIndex(index) method is exposed on the popover scope. Closes #3868. (@okisdev)

• #3831 d53ff4f - chore: remove decorative separator comments across packages (@okisdev)

• #3834 17958c9 - refactor: unify mention/slash under behavior sub-primitives; delete Mention/SlashCommand aliases and the execute field on Unstable_TriggerItem; split TriggerPopoverResource; rename react-lexical MentionNode/MentionPlugin/MentionChipProvider/mentionChip prop to DirectiveNode/DirectivePlugin/DirectiveChipProvider/directiveChip; fix IME/Unicode/copy-paste/undo bugs. Breaking (Unstable_ APIs): replace onSelect={{type:"insertDirective",formatter}} with <Unstable_TriggerPopover.Directive formatter={...}>; replace onSelect={{type:"action",handler}} with <Unstable_TriggerPopover.Action onExecute={...}>. Rename unstable_useToolMentionAdapter → unstable_useMentionAdapter with new items/categories/includeModelContextTools options. unstable_useSlashCommandAdapter now returns { adapter, action } — execute stays in the hook closure instead of on the item. Rename CSS class aui-mention-chip → aui-directive-chip and attributes data-mention-* → data-directive-*. (@okisdev)

• #3827 477fa8a - feat: unify mention and slash command primitives under Unstable_TriggerPopover (@okisdev)

• Updated dependencies [c7a274e, ce865bc, ca8f526, c56f98f, 974d15e, 4b19d42, 055dda5, da0f598, d53ff4f, 20f8404, 17958c9]:

  • @assistant-ui/core@0.1.15
  • assistant-stream@0.3.12
  • assistant-cloud@0.1.27
  • @assistant-ui/store@0.2.8
  • @assistant-ui/tap@0.5.9

0.12.25#

Patch Changes#

• c988db8: chore: update dependencies
• Updated dependencies [f20b9ca]
• Updated dependencies [c988db8]
  • @assistant-ui/core@0.1.14
  • assistant-stream@0.3.11
  • assistant-cloud@0.1.26
  • @assistant-ui/store@0.2.7
  • @assistant-ui/tap@0.5.8

0.12.24#

Patch Changes#

• 42bc640: feat: support edit lineage and startRun in EditComposer send flow

  • 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

• e82726c: fix(react): forward viewport slack props from MessagePrimitive.Root

• 376bb00: chore: update dependencies

• 87e7761: feat: generalize mention system into trigger popover architecture with slash command support

  • 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

• Updated dependencies [42bc640]

• Updated dependencies [376bb00]

• Updated dependencies [87e7761]

  • @assistant-ui/core@0.1.13
  • assistant-cloud@0.1.25
  • @assistant-ui/tap@0.5.7

0.12.23#

Patch Changes#

• a8bf84b: feat(core): expose getLoadThreadsPromise() on ThreadListRuntime public API
• bdbd024: fix(core): set EMPTY_THREAD_CORE.isLoading to true to prevent Welcome page flash during thread switch
• 0958070: feat(core): add initialThreadId option to useRemoteThreadListRuntime
• Updated dependencies [de29641]
• Updated dependencies [a8bf84b]
• Updated dependencies [5fd5c3d]
• Updated dependencies [2c5cd97]
• Updated dependencies [ec50e8a]
  • @assistant-ui/core@0.1.11
  • assistant-stream@0.3.10

0.12.22#

Patch Changes#

• 6554892: feat: add useAssistantContext for dynamic context injection

  Register a callback-based context provider that injects computed text into the system prompt at evaluation time, ensuring the prompt always reflects current application state.

• d726499: fix: unify assistant-transport request body format with AssistantChatTransport

  callSettings and config are now sent as nested objects in the request body,
  aligned with the AI SDK transport. The old top-level spread is preserved for
  backward compatibility but deprecated and will be removed in a future version.

• 876f75d: feat: add interactable state persistence

  Add persistence API to interactables with exportState/importState, debounced setPersistenceAdapter, per-id isPending/error tracking, flush() for immediate sync, and auto-flush on component unregister.

• bdce66f: chore: update dependencies

• c362685: feat: add RealtimeVoiceAdapter with VoiceOrb UI, mode/volume support, and ElevenLabs/LiveKit examples

• 4abb898: refactor: align interactables with codebase conventions

  • 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

• 209ae81: chore: remove aui-source export condition from package.json exports

• 50b3100: feat: add render prop support to all primitives for shadcn "Base" component library compatibility

• af70d7f: feat: add useToolArgsStatus hook for per-prop streaming status

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

• Updated dependencies [dffb6b4]

• Updated dependencies [6554892]

• Updated dependencies [9103282]

• Updated dependencies [876f75d]

• Updated dependencies [bdce66f]

• Updated dependencies [4abb898]

• Updated dependencies [209ae81]

• Updated dependencies [2dd0c9f]

• Updated dependencies [af70d7f]

  • assistant-stream@0.3.9
  • @assistant-ui/core@0.1.10
  • assistant-cloud@0.1.24
  • @assistant-ui/store@0.2.6
  • @assistant-ui/tap@0.5.6

0.12.21#

Patch Changes#

• 3227e71: feat: add interactables with partial updates, multi-instance, and selection

  • 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

• 52403c3: chore: update dependencies

• Updated dependencies [781f28d]

• Updated dependencies [3227e71]

• Updated dependencies [3227e71]

• Updated dependencies [0f55ce8]

• Updated dependencies [83a15f7]

• Updated dependencies [52403c3]

• Updated dependencies [ffa3a0f]

  • @assistant-ui/core@0.1.9
  • assistant-stream@0.3.8
  • assistant-cloud@0.1.23
  • @assistant-ui/store@0.2.5
  • @assistant-ui/tap@0.5.5

0.12.20#

Patch Changes#

• 28a987a: feat: SingleThreadList resource
  refactor: attachTransformScopes should mutate the scopes instead of cloning it

• 736344c: chore: update dependencies

• ff3be2a: Add @-mention system with cursor-aware trigger detection, keyboard navigation, search, and Lexical rich editor support

• 70b19f3: feat: add queue.clear callback, route thread.append through queue

  • 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

• 70b19f3: feat: add native queue and steer support

  • 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

• c71cb58: chore: update dependencies

• Updated dependencies [1406aed]

• Updated dependencies [9480f30]

• Updated dependencies [28a987a]

• Updated dependencies [736344c]

• Updated dependencies [ff3be2a]

• Updated dependencies [70b19f3]

• Updated dependencies [c71cb58]

  • @assistant-ui/core@0.1.8
  • @assistant-ui/store@0.2.4
  • assistant-stream@0.3.7
  • @assistant-ui/tap@0.5.4

0.12.19#

Patch Changes#

• 7ecc497: feat: children API for primitives with part.toolUI, part.dataRendererUI, and MessagePrimitive.Quote
• Updated dependencies [7ecc497]
  • @assistant-ui/core@0.1.7

0.12.18#

Patch Changes#

• 1ed9867: feat: move resumeRun to stable

• 427ffaa: refactor: useRemoteThreadListRuntime no longer marked unstable

• 349f3c7: chore: update deps

• 02614aa: feat: add multi-agent support

  • 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

• 642bcda: Add quote.tsx registry components and injectQuoteContext helper

• Updated dependencies [1ed9867]

• Updated dependencies [427ffaa]

• Updated dependencies [349f3c7]

• Updated dependencies [02614aa]

• Updated dependencies [6cc4122]

• Updated dependencies [642bcda]

  • @assistant-ui/core@0.1.6
  • assistant-stream@0.3.6
  • assistant-cloud@0.1.22
  • @assistant-ui/store@0.2.3
  • @assistant-ui/tap@0.5.3

0.12.17#

Patch Changes#

• 990e41d: refactor: code sharing between the multiple platforms
• Updated dependencies [990e41d]
  • @assistant-ui/core@0.1.5

0.12.16#

Patch Changes#

• 5ae74fe: fix: prevent double-submit when ComposerPrimitive.Send child has type="submit"
• 8ed9d6f: Refactor React Native component API: move shared runtime logic (remote thread list, external store, cloud adapters, message converter, tool invocations) into @assistant-ui/core for reuse across React and React Native
• Updated dependencies [5ae74fe]
• Updated dependencies [8ed9d6f]
• Updated dependencies [01bee2b]
  • @assistant-ui/core@0.1.3

0.12.15#

Patch Changes#

• 07dcce0: fix(react): duplicate toolCallId parts when joining consecutive assistant snapshots in the external message converter.
• a845911: chore: update dependencies
• bc40eaf: fix(react): ActionBarMorePrimitive disappearing when ActionBarPrimitive.Root uses autohide="not-last" on non-last messages.
• be23d74: fix(react): make useToolInvocations args stream rewrites recover safely and avoid premature closure for non-executable client tools.
• 1eb059c: fix(react): avoid crashing when external message conversion receives orphaned tool results without a matching tool call.
• Updated dependencies [a845911]
  • assistant-cloud@0.1.21
  • @assistant-ui/store@0.2.2
  • @assistant-ui/tap@0.5.2

0.12.14#

Patch Changes#

• 03714af: fix: DataRenderers not in scope
• Updated dependencies [03714af]
  • @assistant-ui/core@0.1.2

0.12.13#

Patch Changes#

• 17cf9a8: feat(telemetry): add reasoning/cached token usage across cloud reporting paths
• Updated dependencies [17cf9a8]
  • assistant-cloud@0.1.20

0.12.12#

Patch Changes#

• 36ef3a2: chore: update dependencies

• 6692226: feat: support external source attachments in composer

  addAttachment() now accepts either a File or a CreateAttachment descriptor, allowing users to add attachments from external sources (URLs, API data, CMS references) without creating dummy File objects or requiring an AttachmentAdapter.

• c31c0fa: Extract shared React code (model-context, client, types, providers, RuntimeAdapter) into @assistant-ui/core/react sub-path so both @assistant-ui/react and @assistant-ui/react-native re-export from one source.

• 1672be8: feat: bindExternalStoreMessage

• 28f39fe: Handle unknown attachment types with fallback component and unknown message part types with console.warn instead of throwing

• 3a1cb66: feat: assistant transport prepareRequestBody support

• 14769af: refactor: move RuntimeAdapter base logic to @assistant-ui/core; re-export missing core APIs from distribution packages

• 7c360ce: Update npm README

• a638f05: refactor(react): target @assistant-ui/store for ScopeRegistry module augmentation

• 8a78cd2: fix: stabilize runtimeHook identity in useRemoteThreadListRuntime to avoid unnecessary option updates and thread state churn

• Updated dependencies [a638f05]

• Updated dependencies [28f39fe]

• Updated dependencies [36ef3a2]

• Updated dependencies [6692226]

• Updated dependencies [c31c0fa]

• Updated dependencies [fc98475]

• Updated dependencies [374f83a]

• Updated dependencies [fc98475]

• Updated dependencies [1672be8]

• Updated dependencies [14769af]

• Updated dependencies [a638f05]

  • @assistant-ui/core@0.1.1
  • assistant-stream@0.3.4
  • assistant-cloud@0.1.19
  • @assistant-ui/store@0.2.1
  • @assistant-ui/tap@0.5.1

0.12.11#

Patch Changes#

• 5bbe8a9: Fix rewritten streaming tool arguments in assistant transport by safely restarting tool-call arg streams without crashing, preserving logical tool call IDs, and preventing stale status cleanup after reset.

• 5e304ea: feat: client-side run telemetry reporting with beforeReport hook

• 546c053: feat(core): extract subscribable, utils, and model-context; add public/internal API split

• a7039e3: feat(core): extract remote-thread-list and assistant-transport utilities to @assistant-ui/core

• 16c10fd: feat(core): extract runtime and adapters to @assistant-ui/core

• 98c3d54: feat(react): support custom components for "data" message parts

• b181803: feat(core): introduce @assistant-ui/core package

  Extract framework-agnostic core from @assistant-ui/react. Replace React ComponentType references with framework-agnostic types and decouple AssistantToolProps/AssistantInstructionsConfig from React hook files.

• 7836760: fix(assistant-cloud): expand joined messages for AI SDK v6 history export and telemetry reporting

• 9276547: fix: thread deletion crash "Entry not available in the store"

• b65428e: refactor: thread().composer() now needs to be invoked

• af5b085: feat(assistant-cloud): support MCP tool observability

• 61b54e9: Add message timing metadata: AssistantMessageTiming type, automatic timing tracking in AssistantMessageAccumulator, MessageTiming type, useMessageTiming() hook, and client-side streaming timing for AI SDK runtime.

• a094c45: fix: add DataMessagePart to ThreadUserMessagePart for parity with ThreadAssistantMessagePart

• 4d7f712: feat(core): move runtime-to-client bridge to core/store for framework reuse

• ecc29ec: feat(core): move scope types and client implementations to @assistant-ui/core/store

• 6e97999: feat(core): move store tap infrastructure to @assistant-ui/core/store

• a247fc9: feat(assistant-cloud): allow save complete multi-step message

• f414af9: fix: avoid stale thread metadata overwrite while streaming generated titles

• b48912c: fix(react): smooth streaming behaviour to include first chunk

• 93910bd: Rename .tsx files to .ts where no JSX syntax is used

• 58a8472: feat: Add standalone AI SDK hooks for cloud persistence without assistant-ui

  New @assistant-ui/cloud-ai-sdk package with useCloudChat and useThreads hooks. Wraps AI SDK's useChat with automatic message persistence, thread management, and auto-title generation.

• Updated dependencies [b65428e]

• Updated dependencies [d08a488]

• Updated dependencies [b65428e]

• Updated dependencies [5e304ea]

• Updated dependencies [546c053]

• Updated dependencies [a7039e3]

• Updated dependencies [16c10fd]

• Updated dependencies [40a67b6]

• Updated dependencies [b65428e]

• Updated dependencies [b181803]

• Updated dependencies [b65428e]

• Updated dependencies [6bd6419]

• Updated dependencies [b65428e]

• Updated dependencies [b65428e]

• Updated dependencies [af5b085]

• Updated dependencies [61b54e9]

• Updated dependencies [4d7f712]

• Updated dependencies [ecc29ec]

• Updated dependencies [6e97999]

• Updated dependencies [a247fc9]

• Updated dependencies [b65428e]

• Updated dependencies [93910bd]

• Updated dependencies [60bbe53]

• Updated dependencies [58a8472]

• Updated dependencies [b65428e]

• Updated dependencies [b65428e]

  • @assistant-ui/tap@0.5.0
  • assistant-cloud@0.1.18
  • @assistant-ui/store@0.2.0
  • @assistant-ui/core@0.1.0
  • assistant-stream@0.3.3

0.12.10#

Patch Changes#

• afaaf3b: fix: use bracket notation for process.env

• afaaf3b: fix: duplicate key toolCallId error in HITL tools (#3197)

• afaaf3b: fix(react): runConfig not applied when clicking Suggestion with send=true

• afaaf3b: feat(react): Quote Selected Text primitives

  Added new primitives and hooks for quoting selected text from messages:

  • SelectionToolbarPrimitive.Root - Floating toolbar that appears on text selection within a message
  • SelectionToolbarPrimitive.Quote - Button inside the floating toolbar to capture the selection as a quote
  • ComposerPrimitive.Quote - Container for quote preview (renders only when quote is set)
  • ComposerPrimitive.QuoteText - Displays the quoted text
  • ComposerPrimitive.QuoteDismiss - Button to clear the quote
  • useMessageQuote() - Hook to read quote info from message metadata
  • QuoteInfo type - { text: string; messageId: string }
  • ComposerRuntime.setQuote() - Programmatic API to set/clear quotes
  • MessagePrimitive.Root now renders data-message-id attribute

• 51d24be: feat(react): add submitMode prop

  Add submitMode prop to ComposerInput with three options: "enter" (default), "ctrlEnter", and "none". This controls keyboard submission behavior - "ctrlEnter" mode allows plain Enter to insert newlines for easier multi-line message composition, "none" disables keyboard submission entirely.

  The existing submitOnEnter prop is now deprecated but still supported for backward compatibility.

• afaaf3b: feat(assistant-transport): support editing messages

• Updated dependencies [afaaf3b]

  • @assistant-ui/tap@0.4.6

0.12.9#

Patch Changes#

• a088518: chore: update dependencies
• d8122cc: feat: ChainOfThought Layout API
• Updated dependencies [a088518]
  • assistant-stream@0.3.2
  • assistant-cloud@0.1.17
  • @assistant-ui/store@0.1.6
  • @assistant-ui/tap@0.4.5

0.12.8#

Patch Changes#

• 38f4a32: feat: ChainOfThoughtPrimitive

0.12.7#

Patch Changes#

• 77af8c3: fix: runtime not responsive if loaded under React StrictMode (critial bug)
• 9ef966a: fix(store): memoize the aui client instance
• Updated dependencies [77af8c3]
• Updated dependencies [9ef966a]
  • @assistant-ui/tap@0.4.4
  • @assistant-ui/store@0.1.5

0.12.6#

Patch Changes#

• 39fefec: feat: importExternalState API

0.12.5#

Patch Changes#

• d45b893: chore: update dependencies
• fe71bfc: feat: use enhanced tapSubscribableResource hook
• Updated dependencies [d45b893]
• Updated dependencies [fe71bfc]
• Updated dependencies [fe71bfc]
  • assistant-stream@0.3.1
  • assistant-cloud@0.1.16
  • @assistant-ui/store@0.1.4
  • @assistant-ui/tap@0.4.3

0.12.4#

Patch Changes#

• 86baaee: fix(react): devtools not register
• 3bbe318: fix: allow destructuring proxy methods (e.g. addToolResult, resumeToolCall)
• Updated dependencies [3bbe318]
  • @assistant-ui/store@0.1.3

0.12.3#

Patch Changes#

• 07d1c65: fix: nesting assistant providers
• b591d72: feat: new tools API
• 59a338a: feat: åshowEmptyOnNonTextEnd
• acbaf07: feat: add framework-agnostic toToolsJSONSchema and toGenericMessages utilities to assistant-stream
• c665612: fix: do not capture handleSendMessage errors
• 0371d72: feat: AssistantRuntimeProvider aui prop
• e8b3f34: feat: Suggestions API and Primitives
• Updated dependencies [07d1c65]
• Updated dependencies [acbaf07]
• Updated dependencies [5ab3690]
• Updated dependencies [0371d72]
  • @assistant-ui/store@0.1.2
  • assistant-stream@0.3.0
  • @assistant-ui/tap@0.4.2
  • assistant-cloud@0.1.15

0.12.2#

Patch Changes#

• 1ea3e28: feat(react): better error handling
• 8cbf686: fix: tap should run effects after remount
• a8be364: feat: log individual errors when throwing AggregateError
• 605d825: chore: update dependencies
• Updated dependencies [8cbf686]
• Updated dependencies [2e088eb]
• Updated dependencies [a8be364]
• Updated dependencies [605d825]
• Updated dependencies [fe15232]
  • @assistant-ui/tap@0.4.1
  • @assistant-ui/store@0.1.1
  • assistant-stream@0.2.48
  • assistant-cloud@0.1.14

0.12.1#

Patch Changes#

• 8672695: fix: race condition in RemoteThreadListRuntime causing app crash on thread deletion

0.12.0#

Minor Changes#

• 9314b36: feat: use @assistant-ui/store to power state management

Patch Changes#

• 6eab31e: fix(react): handle tool argsText key reordering during streaming
• 083ed83: fix(cloud): serialize image and file parts across all formats
• 6511990: fix(react): bind this context when calling __internal_setGetInitializePromise
• a526e63: fix uncaught AbortError when cancelling streams
• Updated dependencies [11625b5]
  • @assistant-ui/store@0.0.7

0.11.59#

Patch Changes#

• fe06c7c: Revert "fix(react): accept URL-based images in sanitizeImageContent (#3069)"
• Updated dependencies
  • @assistant-ui/tap@0.4.0

0.11.58#

Patch Changes#

• 3719567: chore: update deps
• Updated dependencies [3719567]
  • assistant-stream@0.2.47
  • assistant-cloud@0.1.13
  • @assistant-ui/tap@0.3.6

0.11.57#

Patch Changes#

• 9a110ea: fix(react): prevent viewport slack feedback loop
• caee095: feat(react): allow passing threadId to backend
• 9883125: fix(react): merge reasoning parts with same parentId in ExternalStoreRuntime

0.11.56#

Patch Changes#

• 3a0b9c8: fix(react): scroll to bottom on initial history load
• b8f62e1: fix: add missing type export for ExportedMessageRespositoryItem
• 8d5c20c: fix: restore useLocalThreadRuntime export as deprecated alias to useLocalRuntime

0.11.55#

Patch Changes#

• 5ca09bc: fix(cloud): filter unsupported messages parts passed to generateTitle

0.11.54#

Patch Changes#

• ab2259d: feat(react): thread list item more primitive

• 699e585: feat(react): action bar more primitive

• 4b63488: Allow async function for body in runtime options

• aee8561: feat(react): add dictation (speech-to-text) support

  Adds dictation (speech-to-text) support via a new DictationAdapter interface. Users can now convert voice input to text in the composer using the browser's Web Speech API or custom adapters.

  • New adapter: WebSpeechDictationAdapter - uses browser's Web Speech API
  • New components: ComposerPrimitive.Dictate, ComposerPrimitive.StopDictation, ComposerPrimitive.DictationTranscript
  • New state: composer.dictation for dictation status and transcript
  • New methods: composer.startDictation(), composer.stopDictation()
  • Configuration via adapters.dictation in runtime options

• dbfdb11: fix(docs): fix broken migration links

0.11.53#

Patch Changes#

• 57bd207: chore: update dependencies
• cce009d: chore: use tsc for building packages
• Updated dependencies [57bd207]
• Updated dependencies [cce009d]
  • assistant-stream@0.2.46
  • assistant-cloud@0.1.12
  • @assistant-ui/tap@0.3.5

0.11.52#

Patch Changes#

• 4db92c9: fix(react): useIsHoveringRef on SSR issue

0.11.51#

Patch Changes#

• fix: update tap package

0.11.50#

Patch Changes#

• bae3aa2: feat: use new tap global flushSync method
• e8ea57b: chore: update deps
• Updated dependencies [bae3aa2]
• Updated dependencies [bae3aa2]
• Updated dependencies [bae3aa2]
• Updated dependencies [bae3aa2]
• Updated dependencies [bae3aa2]
• Updated dependencies [bae3aa2]
• Updated dependencies [e8ea57b]
• Updated dependencies [bae3aa2]
  • @assistant-ui/tap@0.3.3
  • assistant-stream@0.2.45
  • assistant-cloud@0.1.11

0.11.49#

Patch Changes#

• 89aec17: feat: AI SDK frontend tool execution cancellation support
  fix: AI SDK isRunning status when running frontend tools
• ee7040f: fix: always scroll to bottom when switching to a thread
• bd27465: feat: ability to disable auto scrollToBottom on message send / thread switch
• a3e9549: feat: only add turn anchor slack after the first turn
• 206616b: fix: scroll to bottom button flickers on send message
• 7aa77b5: feat: do not take viewport padding into account when calculating the slack inset
• Updated dependencies [89aec17]
  • assistant-stream@0.2.44

0.11.48#

Patch Changes#

• ba26b22: feat(react): export as anything

• d169e4f: feat: add AssistantIf

• da9f8a6: Fix ESC keydown handler to only trigger when event originates from the composer input

  The useEscapeKeydown hook was intercepting ESC key events globally, preventing other UI elements (like Radix dialogs) from responding to ESC. The handler now checks if the event target is within the composer input before calling preventDefault().

• 01c31fe: chore: update dependencies

• Updated dependencies [01c31fe]

  • assistant-stream@0.2.43
  • assistant-cloud@0.1.10
  • @assistant-ui/tap@0.3.2

0.11.47#

Patch Changes#

• 45d771f: fix(react): data-status stuck on running when smooth streaming disabled

0.11.46#

Patch Changes#

• ab8953b: feat(react): add allowNesting option to allow wrapping runtimes with custom thread list adapters

0.11.45#

Patch Changes#

• ec662cd: chore: update dependencies
• Updated dependencies [ec662cd]
  • assistant-stream@0.2.42
  • assistant-cloud@0.1.9
  • @assistant-ui/tap@0.3.1

0.11.44#

Patch Changes#

• 4f6afef: feat: unified json schema

0.11.43#

Patch Changes#

• f54c17b: feat: Viewport turnAnchor="top"

0.11.42#

Patch Changes#

• 354c5c3: feat: MessageState.index
• c3ac004: fix: export ComposerAttachmentDropzone as ComposerPrimitive.AttachmentDropzone
  fix: prevent drag state flicker in ComposerAttachmentDropzone
• 282a596: feat: ThreadPrimitive.ScrollToBottom behavior prop

0.11.41#

Patch Changes#

• 08430e8: feat(assistant-transport): support command enqueue inside onError/onCancel
  feat(assistant-transport): cancel queued commands on error

0.11.40#

Patch Changes#

• 2c33091: chore: update deps
• Updated dependencies [2c33091]
  • assistant-stream@0.2.41
  • assistant-cloud@0.1.8
  • @assistant-ui/tap@0.2.2

0.11.39#

Patch Changes#

• b408005: feat(react-ai-sdk): Integrate AI SDK v5 data parts in message content
• 7a6d9ca: fix: LocalThreadRuntime deleting branches during message reloads
• 70d5966: feat: allow storing runConfig with ThreadHistoryAdapter
• 3754bdd: refactor: rename toolUIs to tools and remove ToolUI API
• 0a4bdc1: feat: renamed ResourceElementConstructor to Resource, changed ResourceElement.type to be Resource instead of ResourceFn
• Updated dependencies [0a4bdc1]
  • @assistant-ui/tap@0.2.1

0.11.38#

Patch Changes#

• 66a13a0: fix: separate scroll-to-bottom button from autoScroll behavior (#1916)

• 4e3877e: feat: Add thread fetching capability to remote thread list adapter

  • Add fetch method to RemoteThreadListAdapter interface
  • Implement fetch in cloud adapter to retrieve individual threads
  • Enhance switchToThread to automatically fetch and load threads not present in the current list
  • Add get method to AssistantCloudThreads for individual thread retrieval

• eef682b: fix(react): update check for scroll position in autoscroll

• Updated dependencies [4e3877e]

  • assistant-cloud@0.1.7

0.11.37#

Patch Changes#

• 0ce129b: add scroll lock hook for reasoning component

0.11.36#

Patch Changes#

• 3ab9484: feat: Toolkit API
• 7a88ead: chore: mark all old context API hooks as deprecated
• 81b581f: feat: display AI SDK errors
• 2fc7e99: chore: update deps
• Updated dependencies [dbc4ec7]
• Updated dependencies [2fc7e99]
  • @assistant-ui/tap@0.1.5
  • assistant-stream@0.2.39
  • assistant-cloud@0.1.6

0.11.35#

Patch Changes#

• 2fc5c3d: feat: AssistantTransport wire format
• 04144dd: feat: useAssistantTransportState
• Updated dependencies [2fc5c3d]
  • assistant-stream@0.2.38

0.11.34#

Patch Changes#

• 953db24: chore: update deps
• fix: submittedFeedback external message converter support
• Updated dependencies [953db24]
  • assistant-stream@0.2.37
  • assistant-cloud@0.1.5
  • @assistant-ui/tap@0.1.4