PINNED CLIENTS · LOCAL REPLAY
Run your AG-UI capture through both SDKs.
See what reaches your subscribers, messages and state. Review a change, run it again, then take the exact SDKs and observations with you.
01 / Load one capture
JSON · JSONL · SSEDrop the run you want to understand.
8 MiB · 5,000 events · nothing uploaded · no API keysNo run loaded. Choose an example or your own capture.
| Observed path | SDK 0.0.59 | SDK 1.0.2 | Inspect |
|---|
No observed differences in this view.
The request protocol declaration is an expected version difference. Generated message IDs are normalized only for this comparison; original IDs remain in the SDK records and export.
Each selection changes captured producer data. Review the field path and loss before running it. Subscriber application code still needs its own change.
What does a resolved run actually prove?
The two pinned TypeScript clients consumed a local SSE response. This does not execute a model or tool, test your backend middleware, render your application, or certify a producer stream. A provider RUN_ERROR can coexist with a resolved SDK promise. Missing run boundaries and unterminated SSE frames are shown separately.
All data is processed in browser Workers. The page fetches only fixed same-origin code and replay assets. Captured URLs and tool arguments are never executed. The comparison keeps raw data, delivered events and reviewed branch inputs distinct.
Start with metadata and nulls, tool-result media or the capture contract. The method page records exact versions and test limits.