assistant-ui--assistant-ui/packages/react-native/CHANGELOG.md

@assistant-ui/react-native

0.1.29

Patch Changes

• #4580 2220136 - fix: re-export documented context providers from platform barrels (@Kinfe123)

0.1.28

Patch Changes

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

• #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.

• #4513 ef5d628 - fix(react-native): stop IME composition from breaking the web composer input (@okisdev)

  two related IME regressions on the rn-web ComposerInput (#4506, #4510):

  • #4506: typing a CJK/IME composition was interrupted mid character. onChangeText called aui.composer().setText(value), which the tap scheduler defers to a macrotask, so the controlled value={text} stayed stale while react-dom reconciled the textarea and reset it back, killing the in flight composition buffer. now wraps setText in flushTapSync on web so the controlled value is synced synchronously before react can write the stale value back, mirroring the web ComposerPrimitive.Input.
  • #4510: pressing Enter to commit an IME candidate submitted the message instead of only confirming it. rn-web forwards the raw dom keydown to onKeyPress before its own composition guard, so the Enter branch fired while isComposing/keyCode === 229 was set. now bails out of the submit branch when the forwarded nativeEvent reports an active composition, matching rn-web's own isEventComposing.

  both only affect the web path; native iOS/Android keep the existing behavior.

• #4514 19c0b86 - test: add a vitest suite covering the react-native primitives (composer input IME and submit behavior, action buttons, conditionals, state readers, error, chain-of-thought, and message content dispatch) (@okisdev)

• #4577 fe28419 - feat: re-export unstable interactable snapshot helpers from native and ink barrels (@Kinfe123)

• #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-ui/store@0.2.19
  • @assistant-ui/tap@0.9.3

0.1.27

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.1.26

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).

• Updated dependencies [344f737, a2e21ee]:

  • @assistant-ui/core@0.2.17

0.1.25

Patch Changes

• #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-ui/tap@0.9.1
  • @assistant-ui/store@0.2.18

0.1.24

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.1.23

Patch Changes

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

• 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.1.22

Patch Changes

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

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

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

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

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

  • @assistant-ui/core@0.2.11
  • assistant-stream@0.3.21
  • @assistant-ui/store@0.2.14
  • @assistant-ui/tap@0.6.0

0.1.21

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)

• #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, 5fe118d, dcd5897, 0558db2, 69540af, d9b3119, ae54c55, 7640b31]:

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

0.1.20

Patch Changes

• #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.1.19

Patch Changes

• #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).

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

• #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": [].

• #4128 331f2f7 - chore: update dependencies (@Yonom)

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

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

0.1.18

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.1.17

Patch Changes

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

• #4095 fa62e49 - fix(react-native): support the children render-prop API on ThreadPrimitive.Messages (@okisdev)

  @assistant-ui/core/react's ThreadPrimitive.Messages was updated in #3642 to accept either components or a children render function, and the docs and examples/with-expo were switched to the children form. The React Native primitive (FlatList-backed, separate implementation) was missed in that pass and kept requiring components, so the example crashed at runtime with Cannot read property 'UserMessage' of undefined (from getComponent(undefined, role, isEditing)).

  Mirrors the core/react shape: ThreadMessagesProps is now a union of { components } or { children }, with a new ThreadMessageByChildren that wraps each row in MessageByIndexProvider + RenderChildrenWithAccessor so consumers get a lazy { message } accessor without subscribing the row to the full message state. The components path is unchanged.

  <ThreadPrimitive.Messages>{() => <MessageBubble />}</ThreadPrimitive.Messages>
  

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

  • assistant-stream@0.3.16
  • @assistant-ui/core@0.2.5
  • @assistant-ui/store@0.2.12
  • @assistant-ui/tap@0.5.12

0.1.16

Patch Changes

• #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.

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

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

0.1.15

Patch Changes

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

0.1.14

Patch Changes

• #3932 6700da5 - feat: re-export RuntimeAdapterProvider, useRuntimeAdapters, and CompleteAttachment (@AVGVSTVS96)

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

• 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.1.13

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.1.12

Patch Changes

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

• 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-ui/store@0.2.8
  • @assistant-ui/tap@0.5.9

0.1.11

Patch Changes

• 0d2d2f3: fix: export ExportedMessageRepository and ExportedMessageRepositoryItem from react-native
• c988db8: chore: update dependencies
• Updated dependencies [f20b9ca]
• Updated dependencies [c988db8]
  • @assistant-ui/core@0.1.14
  • assistant-stream@0.3.11
  • @assistant-ui/store@0.2.7
  • @assistant-ui/tap@0.5.8

0.1.10

Patch Changes

• 376bb00: chore: update dependencies
• Updated dependencies [42bc640]
• Updated dependencies [376bb00]
• Updated dependencies [87e7761]
  • @assistant-ui/core@0.1.13
  • @assistant-ui/tap@0.5.7

0.1.9

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.

• bdce66f: chore: update dependencies

• 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

• 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-ui/store@0.2.6
  • @assistant-ui/tap@0.5.6

0.1.8

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-ui/store@0.2.5
  • @assistant-ui/tap@0.5.5

0.1.7

Patch Changes

• 736344c: 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.1.6

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.1.5

Patch Changes

• 4a904de: refactor: remove useAssistantRuntime hook
• 349f3c7: chore: update deps
• 6cc4122: refactor: use primitive hooks
• 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-ui/store@0.2.3
  • @assistant-ui/tap@0.5.3

0.1.4

Patch Changes

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

0.1.3

Patch Changes

• 8ed9d6f: Add optional aui parameter to AssistantRuntimeProvider for passing an AssistantClient
• 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.1.2

Patch Changes

• a845911: chore: update dependencies
• Updated dependencies [a845911]
  • @assistant-ui/store@0.2.2
  • @assistant-ui/tap@0.5.2

0.1.1

Patch Changes

• 36ef3a2: chore: update dependencies
• 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.
• 14769af: refactor: move RuntimeAdapter base logic to @assistant-ui/core; re-export missing core APIs from distribution packages
• f8abe87: feat(react-native): add attachment primitives and useComposerAddAttachment hook
• a638f05: refactor(react-native): import generic store utilities from @assistant-ui/store, remove deprecated hooks in favor of useAuiState
• d74d309: feat(react-native): add tool system, model context hooks, and data renderers
• 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-ui/store@0.2.1
  • @assistant-ui/tap@0.5.1

0.1.0

Minor Changes

• 124ae9f: feat(react-native): setup
• ef5d622: feat(react-native): integrate store system

Patch Changes

• 9276547: fix: thread deletion crash "Entry not available in the store"
• f116f55: feat(react-native): use core's RemoteThreadList infrastructure
• Updated dependencies [b65428e]
• Updated dependencies [b65428e]
• 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 [61b54e9]
• Updated dependencies [4d7f712]
• Updated dependencies [ecc29ec]
• Updated dependencies [6e97999]
• Updated dependencies [b65428e]
• Updated dependencies [93910bd]
• Updated dependencies [60bbe53]
• Updated dependencies [b65428e]
• Updated dependencies [b65428e]
  • @assistant-ui/tap@0.5.0
  • @assistant-ui/store@0.2.0
  • @assistant-ui/core@0.1.0
  • assistant-stream@0.3.3