Stream Inspector | Zyeon UI

Preview in your theme

status="ready" — one healthy run of 151 frames. Merging is on, so the 32 thinking deltas and the runs of text deltas fold into single rows (the ×N badge says how many); the 940 ms hiccup mid-sentence BREAKS the fold, so the delta that arrived late starts its own row and carries the stall mark instead of disappearing into the run before it. The TTFT line is drawn where the first token landed — everything above it is connection overhead. Click any row to read its payload, and flip that row to Raw for the exact SSE frame.

TTFT668mstok/s36.5events151· 10 rowstotal4.79swire18.2 kB

TTFT 668msfirst think frame — everything above is connection overhead

status="ready", fed live. The panel pins itself to the tail while it plays; scroll up inside the feed and it breaks away, freezes the top of its window so nothing shifts under the cursor, and counts the frames you have not seen on the "Jump to latest" pill. The panel owns no clock — the interval belongs to this demo.

TTFT668mstok/s36.5events151· 10 rowstotal4.79swire18.2 kB

TTFT 668msfirst think frame — everything above is connection overhead

follow: on · frames 151/151

status="ready" with merging OFF and maxRows={120}: 1,232 frames, one row each. Only the last 120 rows are in the DOM and the banner says exactly how many are not, with a control to render them all — a budget you can see is a budget you can trust. This is the run that explains why "Merge deltas" exists.

TTFT492mstok/s93.9events1,232total13.32swire143.4 kB

1,112 earlier rows are not in the DOM

status="ready" for a degraded stream, with stallMs={500} and the payload view defaulting to Raw. TTFT lands past three seconds and every gap over half a second is marked and counted — click the stalls chip in the header to walk them one by one, it centres each stalled row and keeps score. The provider error arrived AS a frame: the transport was fine, so the panel stays ready and the failure is a destructive row, not an envelope error.

TTFT3.12stok/s4.2events17· 7 rowstotal8.65swire1.9 kB

TTFT 3.12sfirst text frame — everything above is connection overhead

status="ready" for a response that never writes a character: it opens straight into a tool call, so TTFT comes from the tool-call frame instead of a text delta. Every frame here carries a wall-clock label, so the time column offers a Clock mode; two frames arrived without their raw bytes and the raw view says it reconstructed them rather than passing a guess off as the wire truth.

TTFT457mstok/s69events9· 6 rowstotal1.14swire713 B

TTFT 457msfirst tool frame — everything above is connection overhead

status="loading" — the request is out and not one frame has arrived.

status="empty" — the connection opened and closed without a single frame. Its own bug, and it reads differently from still waiting.

The stream opened and closed without emitting a single event.

status="error" — the transport itself failed, which is a different failure from a provider error inside the feed, so it reads differently and offers a retry.

The stream broke before it could be inspected

The connection closed after 0 frames. Upstream returned text/html; charset=utf-8 instead of text/event-stream. request-id: req_01Fj4Kd9

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