Changelog

2026-02-26

Changes

New component: Geo Map — themed Leaflet shell with automatic dark tile inheritance from the document theme.
Gallery: deterministic ranking, centered layout, and masonry column breakpoint refinements.

2026-02-17

Changes

New component: CodeDiff — unified and split diff views for code.
Compound composition API shipped across Code Block, Terminal, Order Summary, Video, Progress Tracker, and Item Carousel.
Weather Widget: runtime artifacts now generate as TypeScript; generated payload shrunk with size guardrails.
Shared theme tokens introduced across code components; Code Block mirrors shared tokens locally with tightened content line-height.
Normalized action button styling and layout across components; default spacing added between ToolUI surface and actions.
Data Table: added links-tags preset; removed escalate from actions preset; removed resources preset from docs.

Migration prompt

Update Tool UI components to the compound composition API.Goals:1) Re-install only the affected components that already exist in this project.2) Migrate usage from monolithic component props to compound subcomponents (e.g., CodeBlock.Root, Terminal.Output).3) Validate UI rendering with updated component APIs.Steps:- Check which of these components exist in this project by looking for their directories under components/tool-ui/:  code-block, terminal, order-summary, video, progress-tracker, item-carousel- For each component that exists, re-install it to pull in the new compound exports:  npx shadcn@latest add @tool-ui/code-block  npx shadcn@latest add @tool-ui/terminal  npx shadcn@latest add @tool-ui/order-summary  npx shadcn@latest add @tool-ui/video  npx shadcn@latest add @tool-ui/progress-tracker  npx shadcn@latest add @tool-ui/item-carousel- Skip any component not already installed — do not add new components.- Update imports and usage to reference compound subcomponents instead of monolithic component props.- Run lint, typecheck, and tests; fix any breakages.- Validate UI rendering with updated component APIs.

2026-02-12

Breaking changes

Tool UI component entrypoints now enforce /schema boundaries; imports from non-schema entrypoints may break.
Removed the error boundary layer across Tool UI components; existing error handling may no longer apply.
Tool UI action model migrated to bound compound action surfaces. Legacy inline response-action patterns were removed in favor of LocalActions / DecisionActions, and outlier components now use dedicated action configs. See Actions.

Changes

Tool UI: repo-wide enforcement of /schema entrypoints.
Tool UI action model refactor: migrated components to bound compound action surfaces via LocalActions and DecisionActions. See Actions.
Action-model cutover shipped across core components (including Audio, Citation, Code Block, Data Table, Image, Link Preview, Order Summary, Plan, Terminal, Video, and social post renderers: X Post, Instagram Post, LinkedIn Post).
Outlier workflows were split to component-specific action configs (Option List, Parameter Slider, Preferences Panel) with contracts tightened around supported action props. See Actions.
Option List: receipt presets codegen updated to omit onConfirm; multi-receipt preset added; receipt spacing refined; related tests updated.
Progress Tracker: shipped v2 display with result-driven UI; tests updated.
Plan: compact variant steps-only mode implemented.
Image Gallery and Item Carousel: aligned tool-ui contracts.

Migration prompt

Migrate codebase to adopt explicit /schema entrypoints for Tool UI schemas.Goals:1) Move all schema helper imports to dedicated /schema entrypoints per component.2) Keep public UI imports under their component paths; import schema only from /schema modules.3) Migrate action handling to the bound compound model using LocalActions / DecisionActions.4) Replace legacy response-action usage on outlier components with their dedicated action configs.5) Update tests and docs to reflect new entrypoints and action model semantics.6) Regenerate artifacts (registry/public assets) and update docs accordingly.7) Validate UI rendering with updated imports and schema/action contracts.Steps:- Replace imports of Serializable*Schema, parseSerializable*, and safeParseSerializable* from non-schema tool-ui entrypoints with imports from the component's /schema module (e.g., @/components/tool-ui/<component>/schema).- For all affected components, update imports to reference /schema entrypoints; preserve existing UI imports.- Migrate shared action composition to ToolUI-bound LocalActions / DecisionActions surfaces.- Remove legacy inline response-action usage and adopt dedicated outlier action configs (for example selection/adjustment/form action props) where applicable.- Update relevant tests and docs to reflect new entrypoints and action model semantics.- Run lint, typecheck, and tests; fix breakages.- Regenerate artifacts (registry/public assets) and update docs accordingly.- Validate UI rendering with updated schema and action contracts.

UI Guidelines Actions