@chatsystem/client 1.2.6 → 1.3.2

package/README.md

@@ -11,6 +11,26 @@ import { App } from "@chatsystem/client";
 `appToken` identifies the public customer installation; it is not a user
 credential. `displayMode` accepts `launcher` or `chatbox`.
 
+For most React integrations, keep using `App`: it owns one conversation and
+one visual presentation. When the same Agent must appear as both an inline
+chatbox and a floating launcher on one page, mount both presentations inside
+one shared runtime:
+
+```tsx
+import { WidgetRuntime, WidgetView } from "@chatsystem/client";
+
+<WidgetRuntime appToken="YOUR_TOKEN_ID" agentId={42}>
+  <WidgetView displayMode="chatbox" />
+  <WidgetView displayMode="launcher" />
+</WidgetRuntime>;
+```
+
+Both views mirror the same messages, partial response and loading state.
+Opening or closing the launcher does not stop a response. Pressing stop in
+either view cancels the one shared response and leaves its received partial
+content visible in both views. Use separate `WidgetRuntime` boundaries for
+different app tokens or Agents; their conversations and streams stay isolated.
+
 ### Delegated user identity
 
 Pass an `identityProvider` when the customer host can recognize its existing
@@ -93,6 +113,9 @@ the client itself; it must never be reimplemented in a host-specific adapter.
 
 `data-displayMode` is optional and defaults to `launcher`. Set
 `data-displayMode="chatbox"` when embedding the chat directly in the page.
+The bundled script remains a single-widget-per-page API; its data attributes
+and `window.ChatSystem.mount()` contract are unchanged by the React multi-view
+API.
 
 The declarative form remains the simplest anonymous integration. For Identity
 Delegation, load the same bundle without `data-appToken`, then use its