WebSearch
A search query and its results landing one by one as the agent reads.
Install it:
npx shadcn add @ambientui/web-searchLive
Reading three sources
assistant-ui draft persistence
Reading sources… 0s
Behavior
- ·Showing the QUERY is the part most search UIs skip: it is the assistant's interpretation of the question, and the first place an answer goes wrong.
- ·Results stagger in because they genuinely arrive that way — the animation is reporting, not decoration.
- ·The query itself shimmers while sources are still being read: the search is the thing currently happening, and it settles to plain text when the reading ends.
- ·Each source carries its own mark (a caller-supplied logo, else the domain's initial) and its domain in mono, so provenance is recognizable before it is read.
- ·A source with an href opens in a new tab; without one it stays a record of what was read.
When to use
- ·Any answer grounded in a live search.
- ·Whenever the user should be able to challenge WHAT was searched, not just what was found.
When not to
- ·As a final bibliography — that is ReferenceChips, under the answer.
- ·For internal retrieval with no user-visible sources.