@heroui/agent 0.2.0-beta.7 → 0.2.0-beta.8

package/CHANGELOG.md

@@ -1,5 +1,18 @@
 # Changelog
 
+## 0.2.0-beta.8
+
+- Replace the HeroUI Agents Trigger.dev transport with a preconnected protocol-v6 Durable Object
+  WebSocket, resumable streaming, direct provider requests, and runtime-derived activity updates.
+- Move conversation presence and transcript hydration onto the edge connection; InstantDB is now
+  an asynchronous monitoring projection rather than an interactive runtime dependency.
+- Preload project configuration and the complete composer behind an immediately available launcher,
+  show a centered loading state on an early open, and expose readiness through `onReady` and the
+  reactive `useAgent().ready` status for custom entry points.
+- Stabilize startup and composer presentation so the initial prompt appears immediately, controls
+  stay compact while bootstrapping, and the disclaimer remains visible.
+- Bound live activity details and smooth status transitions during long-running turns.
+
 ## 0.2.0-beta.7
 
 - Polish the activity trail with smoother status transitions, semantic summary icons, bounded
@@ -62,8 +75,8 @@
 - Fold `renderUI` into `composeUI`, which now accepts either a single component or a layout tree as
   its root. The component union is no longer declared to the model as a tool schema: it reads a
   compact kind catalog and fetches the props it needs with `getComponentSchema`, which cut ~300 KB
-  (~76K tokens) of JSON Schema off every rendering request. `renderUI` and the `loadUIRenderers`
-  deferral it needed are gone; only `loadUIRenderers` stays reserved for stored-conversation safety.
+  (~76K tokens) of JSON Schema off every rendering request. `renderUI` and the
+  `loadUIRenderers` deferral it needed are gone.
 - Promote fourteen polished Storybook response compositions to validated Agent UI kinds, including
   current weather, forecasts, flights, events, rides, playlists, commerce, messages, player stats,
   notifications, and product-signal tabs.

package/README.md

@@ -174,16 +174,21 @@ Projects and API keys are managed in the [Agents dashboard](https://heroui.pro/d
 
 ## What runs where
 
-The browser sends every message and receives every answer stream through the HeroUI API, which
-owns the model, the durable run, the conversation store, and server-side tools. Ephemeral
-"watching now" presence remains a direct InstantDB room connection; it carries only conversation
-and pseudonymous viewer identifiers, never messages or tool data.
-
-| In the browser                              | Behind the HeroUI API                        |
+The HeroUI API authenticates the visitor once, verifies conversation ownership, and returns a
+one-use connection ticket. The browser then keeps a resumable WebSocket directly to the
+conversation's Cloudflare Durable Object. That object owns the transcript, streams from the model
+provider, and starts MCP or an offline, per-call-scoped sandbox only when a tool actually needs
+one. Before the composer clears, the SDK durably stores the submitted turn and attachment blobs in
+an identity-and-conversation-scoped IndexedDB outbox. It removes that entry only after the Durable
+Object acknowledges committed admission, and reconciles the same `turnId` after a reload. InstantDB
+is updated asynchronously for dashboard monitoring and never sits in front of a response stream.
+
+| In the browser                              | At the HeroUI edge runtime                   |
 | ------------------------------------------- | -------------------------------------------- |
-| Panel, theme, composer, generated UI        | Model orchestration and the durable run      |
-| Client tools, running as the signed-in user | Server tools, MCP servers, knowledge search  |
-| A short-lived HeroUI browser credential     | Runtime credentials and conversation storage |
+| Panel, theme, composer, generated UI        | Conversation Durable Object and model stream |
+| Client tools, running as the signed-in user | Server tools, lazy MCP and offline Python    |
+| Pre-admission IndexedDB turn outbox         | SDK transcript and resumable stream storage  |
+| A short-lived HeroUI browser credential     | Hashed tickets, credit lease, Queue outbox   |
 
 ## Compatibility
 
@@ -192,7 +197,7 @@ and pseudonymous viewer identifiers, never messages or tool data.
 - Chrome/Edge 120+, Firefox 121+, Safari 17.2+
 - ESM only
 
-This SDK speaks protocol version `5`. The hosted API returns `426 Upgrade Required` when a beta SDK is no longer compatible.
+This SDK speaks protocol version `6`. The hosted API returns `426 Upgrade Required` when a beta SDK is no longer compatible.
 
 ## Support