Web Search Card | Zyeon UI

Preview in your theme

status='ready', search.state='done' — the whole step: three query chips (click one to filter the list to the pages it surfaced), a favicon stack of every site consulted, 12 result rows with read / cited marks, and 'Cited only (4)' to cut 12 down to the 4 the answer actually leaned on. All 12 rows are on screen here because maxVisibleResults={12}.

Yes — `use cache` is stable in Next.js 16, it is keyed automatically and invalidated through cacheTag, and it composes with Partial Prerendering rather than replacing ISR. (A stand-in answer — click a marker, or a number inside the card.)

3 queries

Results

Caching and Revalidating — App Router · Next.jsCited as
nextjs.orgJan 28, 2026read
A function marked with `use cache` is cached by the arguments it is called with and by the closed-over values it reads. Entries are keyed automatically; you never write the key you…
Next.js 16Cited as
nextjs.orgOct 21, 2025read
`use cache` graduates from experimental. Partial Prerendering is on by default for new projects: the static shell is served from the edge while the dynamic holes stream in, and a c…
RFC: `use cache` invalidation semantics · vercel/next.js · Discussion #74123Cited as
github.comFeb 9, 2026read
revalidateTag() only clears entries that were tagged during the render that produced them. Calling it for a tag that was never attached is a silent no-op today — the RFC proposes m…
Partial Prerendering is generally availableCited as
vercel.comNov 4, 2025read
ISR regenerates a whole route on a schedule; PPR splits the route once at build time and only the holes re-run per request. The two compose: a PPR shell can itself be revalidated o…
Why does revalidatePath not clear my `use cache` entry in Next.js 16?
stackoverflow.comFeb 27, 2026
Accepted answer: revalidatePath busts the route cache, not the function cache. Tag the cached function and call revalidateTag instead.
A practical guide to partial prerendering in Next.js 16
blog.logrocket.comMar 12, 2026
Walks through converting an ISR dashboard to PPR one Suspense boundary at a time.
The Next.js caching cheat sheet nobody asked for (2026 edition)
dev.toJan 6, 2026
One table per cache layer: request memoization, the data cache, the full route cache, the router cache.
PPR vs ISR — when does the shell actually get regenerated?
reddit.comFeb 14, 2026
Thread with two contradictory top answers; the maintainer reply three levels down is the correct one.
Next.js 16 ships `use cache` (nextjs.org)
news.ycombinator.comOct 21, 2025
412 comments, mostly about whether directives belong in userland code at all.
I migrated 40 routes to `use cache` — here is everything that broke
medium.comMar 2, 2026
Paywalled after the third paragraph.
Partial Prerendering explained in 12 minutes
youtube.comDec 19, 2025
Cache tags and revalidation patterns
egghead.ioJan 19, 2026
Six-minute lesson, requires an account.

search.state='reading' — two rows are being fetched right now, and the shimmer sits on those rows because result.readState says so, not because a timer fired. The queries that are still running keep their own spinner on the chip.

3 queries

Reading nextjs.org, github.com…

Results

Caching and Revalidating — App Router · Next.js
nextjs.orgJan 28, 2026read
A function marked with `use cache` is cached by the arguments it is called with and by the closed-over values it reads. Entries are keyed automatically; you never write the key you…
Next.js 16
nextjs.orgOct 21, 2025reading…
`use cache` graduates from experimental. Partial Prerendering is on by default for new projects: the static shell is served from the edge while the dynamic holes stream in, and a c…
RFC: `use cache` invalidation semantics · vercel/next.js · Discussion #74123
github.comFeb 9, 2026reading…
revalidateTag() only clears entries that were tagged during the render that produced them. Calling it for a tag that was never attached is a silent no-op today — the RFC proposes m…
Partial Prerendering is generally available
vercel.comNov 4, 2025
ISR regenerates a whole route on a schedule; PPR splits the route once at build time and only the holes re-run per request. The two compose: a PPR shell can itself be revalidated o…

search.state='searching' — the queries are already visible (they are the most useful thing on screen when an answer later goes wrong), the result list is a skeleton, and nothing on the card measures time.

3 queries

search.state='failed' — the provider quota ran out after the first query landed. The failure text is never clipped, the two dead queries say why on their chips, and the three results that did arrive are still listed: a half-failed step is not an empty one.

3 queries

partial prerendering vs ISR revalidate difference: provider returned 429 after 3 retries
revalidateTag not clearing use cache entry: provider returned 429 after 3 retries

The search provider failed

The search provider returned no reason.

Results

Caching and Revalidating — App Router · Next.js
nextjs.orgJan 28, 2026
A function marked with `use cache` is cached by the arguments it is called with and by the closed-over values it reads. Entries are keyed automatically; you never write the key you…
Next.js 16
nextjs.orgOct 21, 2025
`use cache` graduates from experimental. Partial Prerendering is on by default for new projects: the static shell is served from the edge while the dynamic holes stream in, and a c…
RFC: `use cache` invalidation semantics · vercel/next.js · Discussion #74123
github.comFeb 9, 2026
revalidateTag() only clears entries that were tagged during the render that produced them. Calling it for a tag that was never attached is a silent no-op today — the RFC proposes m…

search.state='done' with zero results — the search ran fine and the web had nothing. Deliberately worded and coloured differently from the failure above, because 'nothing exists' and 'we couldn't look' lead to different next moves.

2 queries

zyeon ui "web-search-card" changelog 2026: 0 results
site:zyeon.ai web search card release notes: 0 results

Every query came back with nothing. The answer below is not grounded in the web.

A 24-result step at the default budget: the stack collapses into '+N', four rows are drawn and the reveal states exactly how many are behind it — 'Show all 24 results (20 more)'. Filter by a query chip and the count re-derives from the filtered list, never from a stored total.

Layout stress: a 190-character title, a 74-character host and a query long enough to be a paragraph. wrap-anywhere + min-w-0 lower the min-content width, so everything wraps inside the card instead of widening it — at 320px too. The snippet is capped at snippetPreviewChars with an inline More.

1 query

Results

Self-hosting Next.js 16 behind a shared Redis cluster: configuring a custom incremental cache handler so that revalidateTag propagates to every container instance without a rolling restart, and what to do when it does notCited as1712
platform-engineering.internal.example-corporation-services.comApr 30, 2026read
Set cacheHandler in next.config.ts to a module that exports get / set / revalidateTag. The handler is instantiated once per server process, so any state it keeps in memory is per-c…

The same finished step at its default disclosure: a step that is over collapses to one line — headline, counts, favicon stack, duration — and gets out of the way of the answer. A step still in flight, or one that failed, opens itself instead.

status='loading' — the search record itself hasn't arrived yet.

status='empty' — the assistant answered this turn without searching at all.

The assistant answered this without searching the web.

status='error' — the transcript row failed to load. A different failure from the search provider failing, so it reads differently and offers a retry.

Couldn't load this search step

The transcript stream closed before this step arrived. request-id: 4c1a-9be2

Try again is wired to the demo: pressed 0 times

Loading preview…

This component is part of Pro

The install command, prompt and concept map are included with a Pro license — one purchase unlocks every Pro component, forever.

Unlock with Pro

3 queries

Results

Caching and Revalidating — App Router · Next.jsCited as
nextjs.orgJan 28, 2026read
A function marked with `use cache` is cached by the arguments it is called with and by the closed-over values it reads. Entries are keyed automatically; you never write the key you…
Next.js 16Cited as
nextjs.orgOct 21, 2025read
`use cache` graduates from experimental. Partial Prerendering is on by default for new projects: the static shell is served from the edge while the dynamic holes stream in, and a c…
RFC: `use cache` invalidation semantics · vercel/next.js · Discussion #74123Cited as
github.comFeb 9, 2026read
revalidateTag() only clears entries that were tagged during the render that produced them. Calling it for a tag that was never attached is a silent no-op today — the RFC proposes m…
Partial Prerendering is generally availableCited as
vercel.comNov 4, 2025read
ISR regenerates a whole route on a schedule; PPR splits the route once at build time and only the holes re-run per request. The two compose: a PPR shell can itself be revalidated o…
Why does revalidatePath not clear my `use cache` entry in Next.js 16?
stackoverflow.comFeb 27, 2026
Accepted answer: revalidatePath busts the route cache, not the function cache. Tag the cached function and call revalidateTag instead.
A practical guide to partial prerendering in Next.js 16
blog.logrocket.comMar 12, 2026
Walks through converting an ISR dashboard to PPR one Suspense boundary at a time.
The Next.js caching cheat sheet nobody asked for (2026 edition)
dev.toJan 6, 2026
One table per cache layer: request memoization, the data cache, the full route cache, the router cache.
PPR vs ISR — when does the shell actually get regenerated?
reddit.comFeb 14, 2026
Thread with two contradictory top answers; the maintainer reply three levels down is the correct one.
Next.js 16 ships `use cache` (nextjs.org)
news.ycombinator.comOct 21, 2025
412 comments, mostly about whether directives belong in userland code at all.
I migrated 40 routes to `use cache` — here is everything that broke
medium.comMar 2, 2026
Paywalled after the third paragraph.
Partial Prerendering explained in 12 minutes
youtube.comDec 19, 2025
Cache tags and revalidation patterns
egghead.ioJan 19, 2026
Six-minute lesson, requires an account.