@artooi/ag-ui-web-component 0.41.2 → 0.41.3
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/CHANGELOG.md +30 -1
- package/README.md +4 -1
- package/dist/ag-ui-web-component.bundle.js +78 -75
- package/dist/ag-ui-web-component.bundle.js.map +4 -4
- package/dist/constants.d.ts +6 -1
- package/dist/constants.d.ts.map +1 -1
- package/dist/core/ag_ui_chat.d.ts.map +1 -1
- package/dist/index.js +1457 -1014
- package/dist/index.js.map +4 -4
- package/dist/ui/history/conversation_history.d.ts +5 -0
- package/dist/ui/history/conversation_history.d.ts.map +1 -1
- package/package.json +1 -1
- package/src/constants.ts +6 -1
- package/src/core/ag_ui_chat.ts +21 -1
- package/src/ui/history/conversation_history.ts +29 -0
- package/src/version.ts +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,34 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
## [Unreleased]
|
|
9
9
|
|
|
10
|
+
## [0.41.3] — 2026-10-07
|
|
11
|
+
|
|
12
|
+
### Fixed
|
|
13
|
+
|
|
14
|
+
- **A resumed or forked run shows the turn it was sent with.** Picking Resume
|
|
15
|
+
or Fork in the checkpoint panel sent what the composer held and streamed the
|
|
16
|
+
answer, but drew no bubble for the turn, so the answer arrived under no
|
|
17
|
+
question. The save already held the turn, so a reload showed a question the
|
|
18
|
+
live transcript never had. The continuation now draws the turn the way Send
|
|
19
|
+
does, ahead of its answer, and tests hold that the live transcript and the
|
|
20
|
+
restored one agree after both a resume and a fork.
|
|
21
|
+
- **`ag-ui-submit` fires for a continued turn.** A host listens to it as "the
|
|
22
|
+
user sent something", and a turn sent with Resume or Fork is one: only the
|
|
23
|
+
endpoint differs. The event fires once the continuation is the run in flight,
|
|
24
|
+
so a `sendMessage()` from a listener is refused rather than starting a second
|
|
25
|
+
run beside it, and a listener that stops it -- a new chat, a thread switch,
|
|
26
|
+
moving the element -- stops it before its request is made. Its
|
|
27
|
+
`detail.attachments` is empty, because a continuation sends only the
|
|
28
|
+
composer's text.
|
|
29
|
+
|
|
30
|
+
### Changed
|
|
31
|
+
|
|
32
|
+
- **Ships DOMPurify 3.4.16 and marked 18.0.14**, from the lockfile refresh
|
|
33
|
+
since 0.41.2. Both builds carry them inlined, the npm build as well as the
|
|
34
|
+
vendored bundle: only `@ag-ui/client` and `@ag-ui/core` are left to the
|
|
35
|
+
host's resolver, so a host's own lockfile does not choose which sanitiser
|
|
36
|
+
runs.
|
|
37
|
+
|
|
10
38
|
## [0.41.2] — 2026-09-23
|
|
11
39
|
|
|
12
40
|
### Changed
|
|
@@ -4222,7 +4250,8 @@ hosts that both arrange the page the way it expects.
|
|
|
4222
4250
|
### Notes
|
|
4223
4251
|
- First release — exercising the automated npm OIDC publish pipeline end-to-end.
|
|
4224
4252
|
|
|
4225
|
-
[Unreleased]: https://github.com/Artui/ag-ui-web-component/compare/v0.41.
|
|
4253
|
+
[Unreleased]: https://github.com/Artui/ag-ui-web-component/compare/v0.41.3...HEAD
|
|
4254
|
+
[0.41.3]: https://github.com/Artui/ag-ui-web-component/compare/v0.41.2...v0.41.3
|
|
4226
4255
|
[0.41.2]: https://github.com/Artui/ag-ui-web-component/compare/v0.41.1...v0.41.2
|
|
4227
4256
|
[0.41.1]: https://github.com/Artui/ag-ui-web-component/compare/v0.41.0...v0.41.1
|
|
4228
4257
|
[0.41.0]: https://github.com/Artui/ag-ui-web-component/compare/v0.40.0...v0.41.0
|
package/README.md
CHANGED
|
@@ -2409,7 +2409,10 @@ Type the next turn in the composer, then pick a row:
|
|
|
2409
2409
|
- **Resume** — continue that run.
|
|
2410
2410
|
- **Fork** — branch it, leaving the original untouched.
|
|
2411
2411
|
|
|
2412
|
-
Both send to the matching server endpoint and stream into the same transcript.
|
|
2412
|
+
Both send to the matching server endpoint and stream into the same transcript. The
|
|
2413
|
+
turn you typed is drawn there ahead of the answer and announced with `ag-ui-submit`,
|
|
2414
|
+
exactly as a send is, so a host that keeps its own record of what the user said sees
|
|
2415
|
+
continued turns too.
|
|
2413
2416
|
|
|
2414
2417
|
Picking a row with an empty composer says so above the input and puts the caret
|
|
2415
2418
|
there, rather than closing the panel over nothing: a continuation sends **only**
|