@artooi/ag-ui-web-component 0.22.0 → 0.23.0

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.
Files changed (21) hide show
  1. package/CHANGELOG.md +62 -1
  2. package/dist/ag-ui-web-component.bundle.js +76 -30
  3. package/dist/ag-ui-web-component.bundle.js.map +3 -3
  4. package/dist/constants.d.ts +16 -0
  5. package/dist/constants.d.ts.map +1 -1
  6. package/dist/core/ag_ui_chat.d.ts +8 -4
  7. package/dist/core/ag_ui_chat.d.ts.map +1 -1
  8. package/dist/index.js +70 -36
  9. package/dist/index.js.map +2 -2
  10. package/dist/ui/attachment_chips.d.ts +12 -1
  11. package/dist/ui/attachment_chips.d.ts.map +1 -1
  12. package/dist/ui/attachment_tray.d.ts.map +1 -1
  13. package/dist/ui/styles.d.ts +1 -1
  14. package/dist/ui/styles.d.ts.map +1 -1
  15. package/package.json +1 -1
  16. package/src/constants.ts +20 -0
  17. package/src/core/ag_ui_chat.ts +8 -30
  18. package/src/ui/attachment_chips.ts +18 -6
  19. package/src/ui/attachment_tray.ts +2 -1
  20. package/src/ui/styles.ts +50 -2
  21. package/src/version.ts +1 -1
package/CHANGELOG.md CHANGED
@@ -7,6 +7,66 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ## [0.23.0] — 2026-08-12
11
+
12
+ Attachment chips, which turned out to be the least finished corner of 0.22.
13
+
14
+ ### Fixed
15
+
16
+ - **A filename on a sent attachment chip was invisible on the stock light
17
+ theme.** `.attachment-chip` set the assistant surface as its background but no
18
+ colour, so on a user bubble it inherited `--ag-ui-user-fg` — white on
19
+ `#f1f1f6`, a contrast ratio of 1.13:1 where WCAG AA wants 4.5:1. Only the size
20
+ stayed legible, because it sets its own muted colour, which is exactly how the
21
+ bug read to a user: an icon, a blank gap, and a size. The chip now takes
22
+ `--ag-ui-text`, the same consumer-overridable token the rest of the body text
23
+ uses, so a page that themes its text themes the chip with it. The dark and
24
+ code themes were never affected, which is why this shipped.
25
+
26
+ - **The composer's attachment tray never collapsed.** The tray sets `hidden`
27
+ while it holds no chips, but its rule declared `display: flex` with no
28
+ `[hidden]` guard, and an author `display` beats the UA stylesheet's
29
+ `[hidden] { display: none }`. Every embed that wired uploads therefore carried
30
+ 8px of dead space above the composer at all times. With the tray genuinely
31
+ collapsing, its padding is also symmetric again (`8px 12px`), so a chip clears
32
+ the composer's top edge instead of sitting flush against it.
33
+
34
+ - **Filenames truncated far short of the space available.**
35
+ `.attachment-chip-name` capped itself at `14ch`, so
36
+ `LQ27552-7006-EXHIBIT-A.pdf` rendered as `LQ27552-7006 …` inside a chip with
37
+ room to spare. The cap is gone: the chip is already `max-width: 100%` with the
38
+ name ellipsising, so its container bounds it, and a genuinely long name now
39
+ ellipsises at the edge it actually reaches. The chip is `box-sizing:
40
+ border-box` with it, which stops that `100%` from overflowing its container by
41
+ the chip's own padding and border.
42
+
43
+ ### Changed
44
+
45
+ - **Attachment chip icons are inline SVG.** 0.22 moved the chrome's glyphs to
46
+ inline SVG and stopped at the chips, leaving emoji sitting beside SVG send,
47
+ attach and mic buttons — a different optical weight, varying by platform, and
48
+ taking neither `currentColor` nor a size from CSS. Four marks (image, PDF,
49
+ text, generic) now follow the same contract as the rest, painted from the
50
+ chip's own colour so an errored chip turns red glyph and all. Both the sent
51
+ bubble's chips and the composer tray's change together.
52
+
53
+ ### Removed
54
+
55
+ - **The client-side attachment manifest in `RunAgentInput.context`.**
56
+ `getContext()` appended a one-line summary of the message's attachments; the
57
+ server now derives that from the refs riding the messages, so the client's
58
+ copy only duplicated it on the turn a file was attached. Attachments still
59
+ reach the agent — through the message, which is where they already were. The
60
+ page-map half of `getContext()` is unchanged.
61
+
62
+ **This needs a server that derives the manifest itself.** `django-ag-ui`
63
+ does so from 0.42.0. Against an older server nothing replaces the client's
64
+ copy, so the agent stops being told which attachment ids exist and answers a
65
+ question about an attached file by asking for the file — which is the defect
66
+ the server-side derivation was written to fix. Upgrade the server first, or
67
+ together. A host that read the manifest out of the run context itself is
68
+ likewise affected.
69
+
10
70
  ## [0.22.0] — 2026-08-11
11
71
 
12
72
  Two complaints about how the widget *feels*, and both turned out to be structural
@@ -1250,7 +1310,8 @@ hosts that both arrange the page the way it expects.
1250
1310
  ### Notes
1251
1311
  - First release — exercising the automated npm OIDC publish pipeline end-to-end.
1252
1312
 
1253
- [Unreleased]: https://github.com/Artui/ag-ui-web-component/compare/v0.22.0...HEAD
1313
+ [Unreleased]: https://github.com/Artui/ag-ui-web-component/compare/v0.23.0...HEAD
1314
+ [0.23.0]: https://github.com/Artui/ag-ui-web-component/compare/v0.22.0...v0.23.0
1254
1315
  [0.22.0]: https://github.com/Artui/ag-ui-web-component/compare/v0.21.0...v0.22.0
1255
1316
  [0.21.0]: https://github.com/Artui/ag-ui-web-component/compare/v0.20.1...v0.21.0
1256
1317
  [0.20.1]: https://github.com/Artui/ag-ui-web-component/compare/v0.20.0...v0.20.1