@mast-ai/react-ui 0.2.0 → 0.3.0

package/dist/components/MessageList.d.ts

@@ -49,8 +49,10 @@ export interface MessageListProps {
  * `virtualizer.measureElement`, so messages with long tool call results or
  * large markdown blocks expand the viewport correctly.
  *
- * Auto-scrolls to the bottom whenever a new entry is appended or the last
- * entry's `text` grows during streaming.
+ * Auto-scrolls to the bottom whenever the content grows (new entry, streaming
+ * text deltas, thinking/tool blocks expanding) **only if** the user is already
+ * at the bottom of the list. If the user has scrolled up to read an earlier
+ * message, their scroll position is preserved until they scroll back down.
  *
  * Reads `messages` from `useAgent()`, so this component must be rendered
  * inside an `<AgentProvider>`.

package/dist/context.d.ts

@@ -35,8 +35,13 @@ export interface AgentProviderProps {
      * {@link import('./approval.js').INLINE_APPROVAL} to defer to the inline
      * approval queue exposed via `useAgent().pendingApprovals`.
      *
-     * Not called when no tool requires approval, and not called when the prop
-     * is omitted — in which case `requiresApproval: true` tools execute silently.
+     * Defaults to a callback that returns `INLINE_APPROVAL` for every call when
+     * omitted, so tools marked `requiresApproval: true` always pause for user
+     * confirmation by default. Apps that already render `<InlineApproval>` (or
+     * read `useAgent().pendingApprovals`) get a working approval flow with no
+     * additional wiring. Provide a custom callback to plug in a different
+     * confirmation UI, auto-approve specific tools, inject canned results, or
+     * short-circuit cancellations.
      */
     onApprovalRequired?: OnApprovalRequired;
     /**
@@ -66,18 +71,28 @@ export interface AgentProviderProps {
      */
     onConversationChange?: (history: Message[], entries: ConversationEntry[]) => void;
     /**
-     * Forces a theme on the auto-rendered `[data-mast-root]` wrapper. When
-     * omitted, the panel follows the OS preference via the default stylesheet's
-     * `prefers-color-scheme` media query. Ignored when `disableRoot` is `true`.
+     * Forces a theme on the auto-rendered `[data-mast-root]` wrapper. Only
+     * meaningful when `disableRoot` is explicitly `false` (so the provider
+     * actually renders the wrapper); when omitted or `true`, this prop has no
+     * effect and consumers should set `data-mast-theme` themselves on whatever
+     * element carries `data-mast-root`. When the wrapper is rendered without a
+     * theme set, the panel follows OS preference via the default stylesheet's
+     * `prefers-color-scheme` media query.
      */
     theme?: 'light' | 'dark';
     /**
-     * Disable the auto-rendered `<div data-mast-root>` wrapper around `children`.
-     * Use this when you want to place `data-mast-root` somewhere else in the
-     * tree yourself, e.g. on a chat sidebar's outer container so additional
-     * non-library UI inside also picks up the library's CSS variables.
+     * Controls whether the provider renders an auto wrapper `<div data-mast-root>`
+     * around `children`.
      *
-     * Default: `false` (the wrapper is rendered).
+     * Default: `true` — the provider is transparent in the DOM and consumers
+     * are responsible for placing `data-mast-root` themselves (typically on the
+     * outermost container, or implicitly via `<ConversationPanel>` which carries
+     * its own `data-mast-root`). This avoids the auto wrapper's panel chrome
+     * (border, padding, `height: 100%`) leaking onto whatever subtree the
+     * provider wraps, including app-root mounts.
+     *
+     * Set to `false` to opt back into the auto wrapper for zero-config setups
+     * that compose primitives directly without their own root container.
      */
     disableRoot?: boolean;
 }