834610320088a70f0cf108671aa8f7d50ea69cfb
The transcript scrolled itself with a watcher that set `scrollTop = scrollHeight` on every new message and streamed token, reaching into ScrollArea's internals through `[data-slot="scroll-area-viewport"]` to find the element that actually scrolls. That follows the tail and nothing else. It has no notion of the reader having scrolled away, so every streamed token yanked them back, and no way down for someone who had deliberately scrolled up. shadcn-vue's MessageScroller is the component for exactly this, so the surface is composed from it instead: the provider owns autoscroll, the viewport reports its edges, the content is a `role="log"` region, and the item carries the scroll anchor. It buys the part the watcher could not express: once the reader scrolls, autoscroll stops rather than fighting them, and a "Scroll to end" button appears. Verified in the browser: at the tail the root reports `data-scrollable="start"` and the button is inert; after a wheel scroll it reports `data-scrollable="end"`, autoscroll disengages, and the button is visible at opacity 1 and reachable. A programmatic scrollTop does not count as intent, which is right: autoscroll reclaims the tail unless a person asked for something else.
fix(ui,gateway): load the served lifecycle vocabulary, and make the page registry match the routes (#890)
feat(messaging): Messaging Service operator surface, chat report rendering, and the diff-cap config fix (#899)
Description
Archie connects events from your systems to agents that can investigate, reason, and act.
Define what an event means, map its data into a workflow, and give that workflow an agent equipped for the job: its own execution environment, tools, and identity.
https://archie.catlow.cloud
133 MiB
0 Stars
1 Watchers
0 Forks
Releases
11
Archie v1.62.0
Latest
Languages
Go
76.7%
Vue
13.1%
TypeScript
7.8%
JavaScript
1.2%
Shell
0.6%
Other
0.4%