@8wave/ai-elements 0.121.0-beta.57 → 0.121.0-beta.58

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -386,6 +386,20 @@ an effect around the page itself: an answer that only thinks and writes leaves t
386
386
  body:has(floating-chat-widget[controlling]) .app-frame { box-shadow: 0 0 0 2px rebeccapurple; }
387
387
  ```
388
388
 
389
+ The floating widget draws a light of its own on the second: while the agent acts on the page, an
390
+ aurora in the agent's color grows from the corner where the card sits, sways while the agent
391
+ works, glints at each of its clicks and draws back into the corner when it lets go, under the card
392
+ and letting every click through. The copilot layout draws a beam on its frame instead, see
393
+ [Copilot layout](#copilot-layout). The agent's setting **Glow while working** (backoffice: Style
394
+ tab, advanced options) switches them off.
395
+
396
+ Every layout, the embedded widget too, shows where the agent acts: a cursor in the agent's color,
397
+ with its name and the name of the element beside it, as in a shared editor, leaves the chat, glides
398
+ to the element and clicks before the action runs, and a ring settles around the element and
399
+ follows the agent to the next one, or goes when your page removes the element. It sits in a layer
400
+ of its own over your page and its modal dialogs, never over the chat, letting every click through,
401
+ and stays on with **Glow while working** off. With reduced motion it moves without gliding.
402
+
389
403
  ## Glass and your own open button
390
404
 
391
405
  Two settings of the agent (backoffice: Style tab, advanced options) change how the floating widget
@@ -1060,7 +1074,8 @@ as its last child. What to know:
1060
1074
  the modal dialog it opened, whole, or the page it led to. After a submit your page has not
1061
1075
  answered yet, the widget waits up to 2 seconds for it to announce the outcome: a save that goes
1062
1076
  to your server is announced when its answer comes back.
1063
- - The element is scrolled into view and outlined while the agent acts. Disabled controls
1077
+ - The element is scrolled into view, and the agent's cursor clicks on it before the action
1078
+ (see [Working state](#working-state)). Disabled controls
1064
1079
  (directly or through a disabled fieldset) and read-only fields refuse the action, and an
1065
1080
  element whose role or accessible name changed since the last snapshot asks the model to read
1066
1081
  the page again.